Ticketing
Part of Live chat and messaging support
Choosing when a chat should become a support ticket
Use the remaining customer action to decide when a chat needs tracked ticket work and avoid duplicate records where messaging already creates tickets.
Treat a chat as tracked follow-up work when an answer or action is still owed after the exchange ends. Tell the customer what happens next. First check whether the platform has already created a ticket: in some systems, manage that existing record rather than create another.
Use the remaining action as the threshold
An exchange can be completed when the question has been answered and no follow-up remains. Keep the work visible when an agent must check another system, seek a specialist decision, investigate a fault or send a promised update after the customer leaves. Before ending the session, establish:
- What result is still owed?
- Who will obtain it, and who will update the customer?
- What context and reply route will that person need?
A new label or ticket object will not repair an unclear handoff. Record the open question and any commitment already made. Mark unverified information as unverified.
Check what the product already records
Intercom distinguishes quick conversations from longer work that needs investigation or collaboration. With a suitable ticket type configured, an agent can convert a conversation to a Customer ticket. The ticket appears beside the replies and internal notes.
Intercom also offers a linked Back-office ticket for a separate internal task. Choose according to whether the customer needs tracked updates, another team needs its own task, or both.
Zendesk says requests received through its messaging channels generate tickets. A team using that workflow should check the existing ticket’s owner and next action before creating another record.
Help Scout creates an Inbox conversation with the transcript and internal notes when a live chat ends. Its end-chat screen defaults to Closed and unassigned, although the agent can change the status and assignment. If a follow-up is owed, check those choices before ending the chat.
Carry the customer through the change
Tell the customer what is being checked, where the next reply will arrive and when to expect an update if the team can commit to a time. Confirm that the contact route is usable. An anonymous visitor who leaves without an email address may not be reachable for an email follow-up.
Keep the original question, relevant details, actions taken and unresolved decision in the working record. Separate private staff discussion from the public update. If a specialist has a linked task, identify who remains responsible for the customer reply.
Compare an answered chat, a record check, a specialist request and a customer departure. In each resulting record, an agent should be able to find the next owner, action and reply route.
