When a customer service agent handles a conversation from email, message or chat it would be nice to assign an issue category, so an agent can flag the conversation as: shipping issue, or missing account information.
So within dashboards directors can see the types of issues popping up.
**SHORT-TERM SOLUTION EDIT - DEC, 15 2020**
👋Hi all, here's my short term solution:
Create New Property on Contact Object: i.e. Latest Reason for Contacting
Add Property to Right Sidebar. For easy access:
Train Customer Service Team, and Optimize Property Values
Create Report of Latest Reason for Contacting:
Distribute to Teams for Continual Improvement, or Automate Responses 😎
Would really love this feature! We don't use ticketing as the vast majority of our customer queries are resolved within the live chat in 5 minutes so categories is not an option. To be able to tag conversations so we can see they type of queries that are coming in would be invaluable.
This had to be a priority since DAY 1, I really dont know how they have so many reports about how many conversations you have but we can not chet what are them about!!! We cannot organize with tags or any other method.
This is absolutely necessary for support teams that actually want to add value to their organization. we can't keep going without visibility and not have the organization not know what conversations are happening.
Just wanted to post about the solution we found here. We have implemented a ticketing system with HubSpot, and a chatflow. In the chatflow, the person has to answer what this question is in reference to, which autopopulates a field on the ticket level. Every email and chat then automatically creates a ticket. For all tickets, we have added the product / issue property as a mandatory closing property, meaning that every support rep has to fill this out, if not already filled in, which mostly applies to emails.
This also allowed us to write an automated "we received your support request" message to people using the ticket workflows, whenever a new ticket comes in, and generally gives us a lot more and more accurate reporting capabilities than the conversations inbox.
This is still an issue – tagging for reporting needs to be added to the conversations. Creating a ticket from every chat conversation is way too cumbersome and unnecessary.