RegisterLogin  
  Search
 

HelpMaster Pro

The most flexible, template driven
helpdesk software on the market


desktop | web self service | email response management | sla escalation | active directory | knowledge base

 

You are here: Community » Discussion Board  
Third party/Supplier contacts
Last Post 17 Jun 2008 10:02 AM by Justin Annand. 7 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
muserUser is Online
Helpdesker
Helpdesker
Posts:25
Points:43
Avatar

--
20 Feb 2008 08:22 PM  

Hi all,

 

May I ask the other users how you treat your Third party contact info within HMP? That is, do you have SITE records for each vendor/external escalation point/service provider, or do you have these details as a knowledgebase article?

 

cheers,

aprill

Rod WeirUser is Offline
HelpMaster Pro development team
Helpdesk whiz
Helpdesk whiz
Posts:170
Points:344
Avatar

--
27 Feb 2008 12:00 AM  
Hi Aprill,

From my experience in consulting and understanding the setup of many of our clients, I believe that most implement 3rd part vendors as sites. Some also have corresponding client records that are then linked to the site. This makes it convenient if you ever need to log a job for that client / site.

I would be interested to know further details about what your operating environment. Perhaps we could come up with the best solution?

Best regards,
Rod
HelpMaster Pro development team.
Have you seen what's new in v9 yet?
muserUser is Online
Helpdesker
Helpdesker
Posts:25
Points:43
Avatar

--
27 Feb 2008 01:03 AM  

I think we will end up doing a bit of a mix of the two. Obviously the contacts pertaining to assets and operating environments should be Sites. We have a few other random things like security guards/camera security that are more about building management. Currently it's a record in the KB. Perhaps it should be moved to the extra info in the Site record for the building/site concerned, now that I think more about it.

muserUser is Online
Helpdesker
Helpdesker
Posts:25
Points:43
Avatar

--
06 Mar 2008 01:59 AM  
OK so getting back to this. If I wanted to show a job had been escalated to a vendor, I would have the job created by the client which would ideally be linked to a site and asset within our business.. then I would link it to another clientID which is our main contact at the vendor? (which is also linked to a site for the vendor?)
Rod WeirUser is Offline
HelpMaster Pro development team
Helpdesk whiz
Helpdesk whiz
Posts:170
Points:344
Avatar

--
06 Mar 2008 03:22 AM  

Yes, this is one way of achieving this. Basically you'd be linking multiple clients to the same job, and then changing the primary client to reflect where the job is.

Here's another way that might work.

1. Create a new staff member, or even skillgroup (or both) that represents the vendor
2. When the job is escalated, assign the job to that staff member, or skillgroup. At this stage it may also be helpful to change the status of the job to something like "Awaiting vendor reply", or "Vendor action" etc.
3. When the job is finished with the vendor, re-assign it back to your internal staff member for further action.

Another way might be to create a unique job status that relates to each unique vendor and change the status of the job to reflect this.

Personally, I like the Staff member/Skillgroup option for the following reasons.

1. It physically moves the job into another job queue which makes it easier to see what each staff member has, and what each vendor has
2. It allows you to create Priority Manager profiles that target that staff member / skillgroup to perform additional escation work such as email reminders, or "Hey, what's happinging to that job - you've had it now for x weeks!"
3. It allows a finer level of reporting.
4. it also allows your vendors to start using the HelpMaster Pro web interface to receive work, update their job and re-assign it back once finished.

This method does have drawback if you have lots of vendors. You can end up having a lot of "Staff members".

Anyway, that's just a few ideas off the top of my head. I hope it's useful.

Best regards,

Rod

HelpMaster Pro development team.
Have you seen what's new in v9 yet?
muserUser is Online
Helpdesker
Helpdesker
Posts:25
Points:43
Avatar

--
11 Mar 2008 09:04 PM  

We don't have many vendors that we regularly escalate to so I like your idea with the Staff Member representation. Thanks  for the input.

Rod WeirUser is Offline
HelpMaster Pro development team
Helpdesk whiz
Helpdesk whiz
Posts:170
Points:344
Avatar

--
11 Mar 2008 09:28 PM  
Hi Aprill, let us know how it all turns out.
Rod
HelpMaster Pro development team.
Have you seen what's new in v9 yet?
Justin AnnandUser is Offline
New Member
New Member
Posts:6
Points:8
Avatar

--
17 Jun 2008 10:02 AM  

This is how we have it setup. -Vendors

- Vendors are staff members. This is so its easier to assign requests. Job status is set to waiting for vendor.

- External requests are set as job type repair/service, normally jobs are classified as incidents. This is do we don't get emails bugging us that the job is not completed within client chosen SLA. We advise internal clients that once it goes outside our organisation its an SLA exception.

- We have a priority manager schedule that runs every few minutes and assign's vendor tickets back to service desk. This prevents clients replying to the job and going "Whinge, this is taking too long" than having that message sent to the vendor.

- We than add the vendor name in a custom field description

- Add the vendor reference to a custom field "VendorRef"

- Create a saved search "Random Vendor" - all jobs open that looks for the vendor name in the custom field description.

 

For other jobs send to suppliers IE. purchase requests

- The clients are staff members only

- Requests are assigned to a supplier and left there

- If after 14 days the job is open and we haven't been advised of a stock shortage it will send an email to the supplier asking for delivery ETA. If they have advised us of a delay we place the job status as on hold and no furthur emails will be received by the vendor.

- Once the equipment arrives we add a note to the request saying the equipment was received and change the status to waiting for invoice. A priority Manager schedule with than run saying equipment arrived please send invoice. And it will keep asking for the invoice every 7 days until we receive it and close the request indicating the bill has been paid.

You are not authorized to post a reply.

Active Forums 4.1
Latest posts
System tag for current amount of jobs in queue? by Adam Faorlin in Using HelpMaster Pro with 1 replies
Hi All, I am hoping to find a system tag for use with email templates that can show the current amount of jobs in a queue or even better, how many j...

HelpMaster Pro v9 now available by Rod Weir in Announcements with 1 replies
  PRD Software is very pleased to announce the offical release of HelpMaster Pro Version 9. Version 9 of HelpMaster Pro is a major versi...

Incident Management tips from the coal face by Beth S in ITIL Best practice - getting it to work for you with 0 replies
I have just released the December 08 PRD Insider Newsletter which starts a dicussion on some 'real life' Incident Management methods. The bulk of thes...

Auto knowledge base population / creation from an action by Rod in Wishlist with 0 replies
Just received via email... Suggested improvement from our staff.... When adding an action to a job, have option to add this action to the knowle...

Please fix these long time bugs by ZGeek in HelpMaster Pro bug? with 2 replies
Everytime I close a job in helpmaster the job browser window shrinks and I have to maximize it again. Everytime I open a new job, the details fields ...

Matching Active Directory users to HelpMaster Pro clients by Rod Weir in Active Directory with 0 replies
A while ago we received this request from a client regarding the v8 Active Directory module Hi guys, I have noticed that with the Active Directo...

Web site automatic refresh to prevent timeouts + Active Directory for Web by Rod Weir in Wishlist with 0 replies
A couple of suggestions sent in via email. Normal 0 false false false EN-AU X-NONE X-NONE ...

Priority Manager & Email Error (Error Location: clsEmail.SendEmail_Redemption at code location: 25) by helpdesk@ntsolutions.com.au in HelpMaster Pro bug? with 0 replies
We recently upgraded from Exchange 2003 to 2007 and also from Helpmaster Pro 8.0.16 to 8.0.18 and we are experiencing issues with priority manager. Th...

Editing multiple records by muser in Using HelpMaster Pro with 1 replies
I'm trying to tidy up inconsistences with our records in both the assets and clients dbs. Is tricky SQl the on the db itself the best way to handle th...

Action Template timers and auto Client ID generation ideas by Rod Weir in Wishlist with 0 replies
2 Suggestions just received via email I would like to request a user/administrator setting to ensure that the timer for action logs is switched off...

  

Latest posts including replies
RE: System tag for current amount of jobs in queue? by Rod Weir in Using HelpMaster Pro
Hi Adam, Thanks for the post and welcome to the HelpMaster Pro forum. This is a great idea. The system tag for a job queue should be a relative...

RE: Deleting system codes, issues, problems etc that are linked to jobs, clients or other entities. by Rod Weir in Using HelpMaster Pro
Still further to this issue... "Deleted" system codes can be re-activated by changing the database field "IsDeleted" from a 1 to a 0. System codes...

RE: HelpMaster Pro v9 now available by Rod Weir in Announcements
Please note that HelpMaster Pro v9 requires a new registration code. All previous registration codes (v7, 7.5, 8 etc) will not work with version 9. ...

Incident Management tips from the coal face by Beth S in ITIL Best practice - getting it to work for you
I have just released the December 08 PRD Insider Newsletter which starts a dicussion on some 'real life' Incident Management methods. The bulk of thes...

Auto knowledge base population / creation from an action by Rod in Wishlist
Just received via email... Suggested improvement from our staff.... When adding an action to a job, have option to add this action to the knowle...

RE: Please fix these long time bugs by ZGeek in HelpMaster Pro bug?
Joy!...

Matching Active Directory users to HelpMaster Pro clients by Rod Weir in Active Directory
A while ago we received this request from a client regarding the v8 Active Directory module Hi guys, I have noticed that with the Active Directo...

RE: Setting reminders for other people by Scott Ward in Wishlist
This is already possible. If you go to the links tab of a new reminder you can add other clients and\or staff. The clients are just there as a ...

RE: Active Directory module > Mappings for HMP Site by Rod Weir in Wishlist
Done. Check out the screen shot of v9.   Thanks for the great suggestion.  We're ready for the next one! ;-)   Best regards, &#...

Web site automatic refresh to prevent timeouts + Active Directory for Web by Rod Weir in Wishlist
A couple of suggestions sent in via email. Normal 0 false false false EN-AU X-NONE X-NONE ...

  

 Copyright 2008 by PRD Software Terms Of Use  |  Privacy Statement