Use Case: A service rep needs help researching or resolving a ticket. They need the ability to notify/reassign(?) the ticket, but continue to track and have the ticker passed back with updates.
The first level is to use the ‘Owner’ field, but when it is changed, the person who initiated the ticket can no longer track it.
I have seen a suggestion on using a custom field - Owner2, for example, but that can impact workflows and passing the contact back can be problemmatic - There is not a way to pass the contact back to the person who originally owned it.
We have considered setting up users as contacts and associating them to the ticket. I have not seen any information on this scenario and whether it is a ‘good’ practice or if there are downsides.
Any feedback/alternatives would be appreciated.
Thanks.
Hi @PCarlson9,
A notification can be achieved by simply mentioning (type @ followed by the user name) in a note on the record.
Users can also choose to follow records: Follow a record
Does one of these help?
Hi @karstenkoehler ,
These are two great options. I will test them and run them by the team.
Either or both should work.
Thanks for the quick response.
Paul Carlson
@karstenkoehler if you just put a note with the @employee name in the ticket - will this continue to update that user for all future activity on the ticket or just the one note? Our current ticketing system (I’m working to migrate to Hubspot’s) instead of “follow” a ticket you “subscribe” and you can subscribe others to the ticket, so you can see in the ticket, the ticket owner as the drop down field and then you can view who else has been subscribed to it. This feature is incredibly helpful, is what you’re suggesting by adding a note with the employees tagged a way to replicate the subscribing others I described? Thanks for helping to clarify for me!