Forum Discussion
8 Replies
Sort By
- troglotech8 years agoActive ContributorCustomer ID and associated attributes should be associated with each Remote Support end point/unattended computer, not just with specific Service Desk incidents. Regardless of whether I am a COL Remote Support or Service Desk customer, I still need access to some basic information to perform my job effectively, including what is my end user's contact name and how I can communicate with them by phone, email and text. Other less generic but also needed information can be handled with comment boxes and/or user defined fields. Any implementation which does not integrate customer contact information with remote support endpoints will DRIVE ME INTO A SNARLING FRENZY!!!
Please do not let a misguided product differentiation/crippling strategy trump a primary goal of design excellence in every product.Our patience is not limitless. You will thrive by making Remote Support the top competitor in it's class, not by trying to shoehorn your customers into an overpriced, overkill "higher end solution". - tobyw78 years agoNew MemberI've just been looking for this feature but looks like it's not there yet. Would be great to have this.
- William Kerns9 years agoNew MemberThis feature would be a swing factor in purchasing Service Desk. Has this been implemented?
- Herman Feeler9 years agoNew MemberHas this been addressed or updated?
Thanks. - gcaparulo10 years agoNew ContributorLinking an unattended Remote Support agent to a ticket and/or CI would be hugely beneficial.
- jason111110 years agoActive ContributorMany thanks. Would be a great inclusion.
- GlennD10 years agoGoTo ManagerHi Jason,
This isn't quite possible yet so I'm turning this into an Idea for the teams to review. We're definitely working towards bringing Remote Support and Service Desk integration closer together. - troglotech10 years agoActive ContributorThat would require a customer ID, something the design team has been reluctant to implement from inception on this GoToAssist.