When should a customer chat become a ticket?
A chat should become a ticket when it cannot be finished in the same conversation: it needs someone else, an outside party, a part or a payment check, or a follow-up on a later day. Anything answered in one sitting stays a chat. The ticket gives the problem a priority, an owner and a due time, so it does not depend on someone remembering it. Below is a simple rule set for a small team, a priority table and the mistakes that make tickets pile up.
Chats and tickets are different jobs
A chat is a conversation: a question, an answer, done, usually in minutes. A ticket is a piece of work with a deadline: a warranty claim, a booking change that needs a manager, a delivery that went to the wrong address. Mixing the two causes trouble both ways. If every chat becomes a ticket, your team drowns in paperwork. If nothing becomes a ticket, follow-ups live in people's heads, and heads go home at 6 pm.
The four-question test
Turn the chat into a ticket if the answer to any of these is yes:
- Does someone outside this conversation need to act? A technician, a doctor, the warehouse, a courier, a supplier.
- Will it take longer than this shift? If the answer comes tomorrow, it needs to survive the hand-over.
- Is money involved that must be checked? A refund, a deposit, a payment the customer says they made.
- Did we promise a follow-up? "We'll call you Thursday" is a ticket waiting to be written.
If all four are no, answer and close the chat.
A priority table a small team can use
| Priority | Examples | Due time to agree |
|---|---|---|
| Urgent | A customer stranded with a broken rental car; a clinic appointment today that was double-booked | Same hour |
| High | Wrong order delivered; refund request; booking change for tomorrow | Same working day |
| Normal | Warranty question; invoice correction; a stock request | Within two working days |
| Low | A feature or product suggestion; a general enquiry with no deadline | Within a week |
Agree the due times as a team and write them down. The exact numbers matter less than everyone using the same ones.
How to write a ticket that someone else can finish
- Title in the customer's terms: "Wrong size delivered, order 4821", not "Issue".
- What was promised and by when, in an internal note on the conversation.
- Who owns it: one person, even if others help.
- What "done" means: "Correct size delivered and the customer confirms", not "looked into".
Then tell the customer in the chat what happens next: "I've logged this for our warehouse team; you'll hear from us here by 2 pm tomorrow." If the ticket started as a complaint, the five complaint steps still apply.
How this works in StayReplied
In the StayReplied unified inbox a conversation can become a ticket with a priority, an assignee, due times and merge history, so duplicate reports of the same problem can be combined. Tickets with status, priority and SLA policies are on every plan, as listed on the pricing page, alongside notifications when a person is needed. The conversation and its internal notes stay attached, so whoever picks up the ticket sees the full story without asking the customer again.
Roles (owner, admin, supervisor, agent, read-only and billing only) decide who can do what, as the docs describe, so a manager can review urgent and high tickets while agents keep answering chats.
Mistakes that make tickets pile up
- No owner. A ticket assigned to "the team" belongs to nobody.
- Due times nobody looks at. Pick one moment a day, such as 10 am, to review open tickets by due time.
- Tickets that never close. When the customer confirms, close it the same day. An open list full of finished work hides the real problems.
- Every chat ticketed "just in case". That doubles the work and buries the urgent ones.
- Closing without telling the customer. The last message in the chat should say what was done.
A daily ten-minute routine
- Sort open tickets by due time.
- Anything overdue: the owner sends the customer an update now. If the customer is the one who went quiet, see how to follow up.
- Anything due today: confirm the owner knows.
- Anything finished: close it, with a one-line note on the cause.
When this is not for you
If your team answers everything in one sitting, such as a café confirming hours or a salon booking a slot, you may never need tickets; a clear owner per chat is enough. And if most of your support is long e-mail threads with attachments, a general help desk built around e-mail may fit better; when a general help desk is enough helps you decide. E-mail in StayReplied is coming soon.
Questions and answers
When should I create a support ticket from a chat?
When the chat cannot be finished in one conversation: someone else must act, it will take longer than the shift, money must be checked, or you promised a follow-up.
What priority levels does a small team need?
Four are enough: urgent, high, normal and low, each with a due time your team agrees and writes down.
Can StayReplied turn a chat into a ticket?
Yes. A conversation can become a ticket with a priority, an assignee, due times and merge history, and the chat history stays attached.
Should every chat become a ticket?
No. Most chats are answered in one sitting and should simply be closed. Ticketing everything buries the problems that matter.
Keep follow-ups from slipping.
start your free trial, 14 days, no card needed.