Turn a customer chat into a ticket and keep replying in the same chat
A refund review, a supplier check or a repair outlasts the chat it started in. Hand the work to a ticket with the right messages and a clear summary, and keep answering the customer in the chat they already use.
Deskwoot Team
9 min read
Contents
- Where the handoff goes wrong
- Which chats need a ticket
- Step 1: pass on the messages that matter
- Step 2: a title, a summary and one owner
- Tell the customer who, what and when
- Reply from the ticket, land in the customer's chat
- Wait for the customer, or close the job
- The handoff checklist
- Doing this in Deskwoot
A customer on WhatsApp says the coffee grinder she bought 3 weeks ago has stopped working. You have her photo and order number, but you can't fix it yourself: someone has to confirm the warranty, and the supplier takes 2 days to answer.
This guide covers which chats need a ticket, a summary template and checklist to copy, and how to keep answering her in the chat she already uses.
Where the handoff goes wrong
Small teams often get this moment wrong in one of two ways:
- The chat stays open in one person's inbox with a mental note attached, and nobody else knows it exists.
- The customer is told to email the warranty address and explain everything again to someone new.
In Salesforce's State of the Connected Customer research (6th edition, 14,300 consumers and business buyers), 56% said they often have to repeat or explain information again to different representatives. Salesforce sells service software, so treat that as vendor research.
A good handoff does 2 jobs. The person who does the work gets everything they need, and the customer keeps talking to you in the chat they already use. The template and checklist below work in any help desk.
Which chats need a ticket
Most chats should never become tickets. If you can finish the job while the customer is still there, answer and resolve.
A ticket is for work that outlasts the chat:
- Someone outside the conversation has to act.
- You are waiting on a supplier or a technician.
- You will need a record of what happened.
| The chat | Ticket? | Who works on it |
|---|---|---|
| "Where is my parcel?" and the tracking link is in the order | No | You, in the chat |
| New delivery address before the order ships | No | You, in the chat |
| Grinder broke after 3 weeks, warranty replacement | Yes | Owner decides, warehouse ships |
| Part out of stock, the supplier has to confirm a date | Yes | Purchasing |
| A heating engineer has to see photos before a visit | Yes | Field team |
| Refund above what the person in the chat may approve | Yes | Billing or the owner |
| The app crashes when the customer uploads a file | Yes | Developer |
| A wrong invoice and a broken part in the same chat | 2 tickets | Billing and warehouse |
Keep to one problem per ticket, so each one closes when its own work is done.
Step 1: pass on the messages that matter
The person who picks up the ticket was not in the conversation. They need:
- the customer's description of the problem
- every number: order, serial, invoice, error code
- the photos
- anything you already promised
They do not need the greeting or the 4 messages it took to find the order. Write down what you checked yourself as a private note, such as "checked the serial, warranty runs until March", and pass that on too.
In Deskwoot, Create ticket preselects the messages since the chat was last resolved or handed off, so you mostly untick the noise. Nothing goes to the customer in this step.
Step 2: a title, a summary and one owner
A title that names the job
Write the title as the job, with the number that identifies it. "Replace grinder under warranty, order 4417" tells the warehouse what to do before anyone opens the ticket.
"Customer issue" or "WhatsApp from Anna" tells them nothing. One line is plenty.
A summary in 6 lines
The summary decides whether the handoff works. Copy this template:
Customer wants: one sentence, in their words.
Facts: order number, product or model, dates, amounts, error text.
Already done: what you checked or tried, and what happened.
Promised to the customer: what, and by when.
Open question: what the ticket owner has to decide or find out.
Done when: the outcome that lets someone resolve the ticket.
Filled in for the grinder:
Customer wants: a working grinder; hers stopped after 3 weeks.
Facts: order 4417, delivered 2 October, red light blinks 3 times (photo picked).
Already done: order is inside the warranty period. The reset from the manual did not help.
Promised to the customer: an answer in this chat by Thursday.
Open question: replace from stock now, or wait for the supplier's part?
Done when: replacement shipped and the tracking link sent to her.
The promise line matters most. A ticket owner who doesn't know you said Thursday will plan for next week.
The "done when" line keeps tickets from staying open for months because nobody agreed what finished looks like.
Category and priority
A category such as Warranty, Refunds or Bug shows you next month which kind of work piles up. Deskwoot can require one on every new ticket.
Leave priority at your default unless there is a real deadline.
One owner
Give the ticket one owner: a person, or a team folder that somebody reads every day.
In Deskwoot, round robin never assigns tickets. A ticket for "Anyone in" a team waits in that team's folder until someone takes it.
Tell the customer who, what and when
Set the expectation in the chat: who is on it, what they will do, and when the customer hears back. 3 examples to adapt:
- Supplier check: "I've asked our supplier when the 40 mm burr set is back in stock. They usually answer within 2 working days, so you'll hear from me here by Thursday, whatever the answer is."
- Repair: "Thanks for the photos. Our technician will look at them tomorrow morning and reply in this chat with a fix you can try yourself or 2 possible dates for a visit."
- Refund review: "I've passed your refund request for order 4417 to the colleague who approves refunds. You'll have the decision here by Friday at the latest."
Leave out the ticket number. In their own chat you already know who they are.
In Deskwoot the customer never sees the ticket, its number or a new email thread. Your team sees a private card in the chat with the ticket's status, team and assignee.
Reply from the ticket, land in the customer's chat
The way back is where many setups break. A reply sent from a separate ticket tool can carry a new subject, such as one with "[Ticket #1043]" added, and headers that point nowhere.
Email threads
Gmail's help page says a conversation "breaks off into a new conversation when the subject line changes". The email standard, RFC 5322, ties a reply to its thread through the In-Reply-To and References headers.
When those don't match, the customer can find your answer in a fresh thread without the history.
The WhatsApp window
When a customer writes to a business on WhatsApp, a 24 hour customer service window starts. Once it closes, Meta's documentation says you can only send approved template messages.
A reply written in a ticket 3 days later is still bound by that window.
One person answers
Only one person answers the customer: whoever holds the ticket. A colleague who wants to reply takes the ticket over first, so the customer never gets 2 different answers.
Internal comments have no such rule. Anyone who can open the ticket can add one and @mention a teammate, so the warehouse can note "shipped today" without writing to the customer.
How Deskwoot sends the reply
In Deskwoot, Reply to customer goes out through the chat the ticket came from: email in the same thread, WhatsApp in WhatsApp, live chat in the widget. A resolved chat stays resolved.
After the 24 hours on a WhatsApp Cloud API inbox, you send an approved template from the ticket (see WhatsApp templates after the 24 hour window).
Wait for the customer, or close the job
Every reply from a ticket either asks the customer for something or finishes the work, and each needs a different status. In Deskwoot that is the difference between Send and wait and Send and resolve ticket.
When you ask for something
Your reply says "Could you send a photo of the type plate?" Set the ticket to pending. The customer's answer in the chat should put it back to open and unread for whoever holds it.
If the chat was already resolved, it should stay resolved while only the ticket wakes up. That way the answer never drops into the general queue.
When the job is done
Your last message says "Your replacement left today, here is the tracking link." Resolve the ticket and leave the chat as it is.
Don't snooze to wait for the customer
Snooze is for dates you know, such as the day the supplier promised the part. In Deskwoot a message from the customer does not wake a snoozed ticket, except on tickets opened from an email.
The handoff checklist
Before you create the ticket:
- The chat needs a ticket: someone else has to act, you wait on someone, or you need a record.
- One problem per ticket. A second problem gets its own.
- The picked messages include the customer's description, every number and the photos.
- The title names the job and the order or serial number.
- The summary says what you promised and by when.
- "Done when" is written down.
- The ticket has an owner: a person, or a team folder somebody reads every day.
- The customer has been told in the chat who is on it and when they will hear back.
- No duplicate. If the customer already has a ticket for this problem, add to it.
Whatever tool you use, try the checklist on your next 5 handoffs. Note which line your team skips most often, and add that line to your ticket template.
Doing this in Deskwoot
Deskwoot is our help desk. With its tickets, the customer keeps one chat and every reply from the ticket lands where they wrote.
Draft with Copilot writes the title and a summary of 2 to 5 points from the messages you pick, and you can change both before you create the ticket.
Tickets are part of Enterprise, at $12 per agent a month or $9.60 billed annually (pricing). A Copilot draft counts as an AI conversation, once per conversation per calendar month, and Enterprise includes 300 of those a month.
You can check every step in the help center before you sign up: creating a ticket, replying from a ticket, tickets and tickets in the app. The tickets launch post gives the overview.
To run your next 5 handoffs in Deskwoot, start the 7 day trial. It runs on Enterprise with tickets switched on, for up to 30 seats including yours, and you need no card.
When the trial ends, you choose a paid plan or keep working on the free Hacker plan. If you leave Enterprise, existing tickets keep working and only new tickets stop.
Also available in:DeutschEspañolFrançaisPortuguês (Brasil)
