When WhatsApp becomes your main service channel, chat is no longer enough: messages get lost between conversations, nobody knows who answered what, and the customer asks the same thing three times. The way out is to treat every WhatsApp request as a ticket.
Signs that chat is no longer enough
- Several agents reply from different phones or from one shared number.
- There is no way to know how long the first reply took.
- When an agent goes on vacation, their conversations freeze.
- The manager cannot say how many requests came in this week or how many were solved.
How WhatsApp service with tickets works
- The customer writes to the company's WhatsApp number, as always.
- A ticket is created with a number, category and priority, and the customer receives an acknowledgment with that number.
- An agent picks it up from the ticket inbox and replies from there; the customer receives the reply on WhatsApp.
- Follow-up messages from the same customer are added to the open ticket instead of creating a new one.
- Once solved, the ticket is closed and the customer can rate the service.
Response times: what to measure
On WhatsApp customers expect fast replies, but "fast" has to be a number. Measure two targets separately:
- First response: how long until someone replies for the first time.
- Resolution: how long until the case is solved.
Each with a target by priority, and a traffic light that warns before it expires. A target that is always missed stops being watched, so start with realistic goals.
The 24-hour window
WhatsApp Business lets you reply freely within 24 hours of the customer's last message. After that, writing to them again requires an approved template. In practice this means two things:
- Replying inside the window is cheaper and simpler: another reason to measure the first response.
- For later notices (the case was solved, the appointment is tomorrow) keep templates ready.
Templates and canned replies
Half of the questions repeat: hours, order status, how to pay. Canned replies with customer data save time and make everyone answer consistently. A knowledge base helps new agents and lets an AI suggest replies that the agent reviews before sending.
Measuring satisfaction
Speed does not tell you whether the answer helped. When the ticket is solved, a one-question survey on the same WhatsApp ("How would you rate our service?", with buttons) gives the share of satisfied customers by agent and by category. It is the number most operations are missing.
Best practices
- A company number, not personal phones. The history belongs to the company.
- Visible hours. If nobody answers at night, the bot should say so and still create the ticket.
- Consent. Only write to people who gave permission, and respect it when they ask to stop.
- All channels in the same inbox. The customer who wrote on WhatsApp and then called is the same case.
The TelHarbor Help Desk turns WhatsApp, SMS, email and phone requests into tickets, replies on the same channel and measures response times and satisfaction. See plans and pricing.
Frequently asked questions
Do I need the WhatsApp Business API for this?
Yes. The WhatsApp Business mobile app does not support multiple agents or a connection to a ticketing system; the API does.
Can I use my current number?
In most cases yes, although that number stops working in the mobile app once it is registered on the API.
What if the customer writes after the ticket is closed?
A new ticket is opened or the previous one is reopened, depending on the setup; the customer history keeps both.
Do agents need WhatsApp on their phones?
No. They reply from the Help Desk on their computer and the customer receives it on WhatsApp.