Support tickets and escalations on WhatsApp: how to triage, collect what an engineer needs, set expectations, escalate, and close the loop, with an AI agent doing the first tier
Support on WhatsApp without a process is a single thread of panic: everything is urgent, nothing is logged, and the customer who asked three days ago is buried under today's. A light process, three tiers, one intake, clear escalation, fixes that without a help desk tool.
Quick answer
Tier support in three: tier one is how-to, account and policy questions answered from your help content; tier two is problems that need a person to look (bugs, order issues, billing); tier three is urgent or sensitive (outages, safety, data, legal). An AI agent answers tier one, runs a fixed intake for tier two (what, when, where, screenshots, account identifier), and escalates tier three instantly with an alert. Set a response-time expectation in the first reply, update the customer when status changes, and close every ticket with a message. ReplyKit handles the first tier and the intake; your inbox's "Needs you" column is the ticket queue.
Three tiers
| Tier | Examples | Who | Target |
|---|---|---|---|
| 1 | How do I, where is, what is your policy, account basics | AI agent from help content | Seconds |
| 2 | Bug, wrong order, billing error, damaged item | Person, after agent intake | Same business day |
| 3 | Outage, safety, data breach, legal threat, abuse | Owner, immediately | Minutes |
Write the tier-three list for your business into the agent's instructions; the agent cannot guess what is critical to you. Escalation setup is in escalation rules for your agent.
The tier-two intake
- What happened, in the customer's words.
- When it started and whether it has happened before.
- Where: which product, order number, page or screen, device or browser.
- Evidence: a screenshot, a photo, an error message.
- Account identifier: email or order number.
- The agent asks for all of it in one or two messages, confirms what it has, sets the expectation ("A person will look at this today and reply here") and hands over. The resolver opens a complete report instead of starting an interrogation.
Expectations and updates
- State the response-time target in the first reply, and keep it. "Today" beats "as soon as possible".
- Update when status changes, not when the customer asks; a status note in the knowledge base lets the agent answer "any update" for known issues without a person.
- If a fix slips, say so before the deadline passes, with a new one.
- For outages, one status line in the knowledge base replaces fifty identical replies; see communicating during an outage.
Closing the loop
Every ticket ends with a message: what was done, and an invitation to reply if it is not right. Then mark the conversation back to the agent so the next question is answered instantly. A week later, the follow-up is where reviews come from; the wording is in after-sales support. Log tickets by type in the CRM; the monthly count by type is your product roadmap.
The queue without a help desk
The inbox's "Needs you" column is the queue: oldest first, each with the intake already done. Two people can work it by taking over different chats. When volume outgrows that, a help desk tool is the next step and the agent still does tier one; the comparison with a multichannel inbox is in ReplyKit vs Trengo.
Frequently asked questions
Can an AI agent handle support?
Tier one completely, from your help content, and the intake for tier two. Fixes, refunds and judgement stay with people.
How do I stop everything being urgent?
Define tier three explicitly for your business and let the agent escalate only those instantly; everything else gets a same-day target.
What should the intake collect?
What, when, where, evidence and an account identifier, in one or two messages, before a person is involved.
Do I need a help desk tool?
Not until two people cannot work the inbox's queue. Until then the "Needs you" column is the ticket list.
How do I handle an outage?
A status line in the knowledge base that the agent quotes, updated as things change, plus a hand-over for anyone with a specific loss.
Tier one answered, tier two reported, tier three alerted
Help content on WhatsApp, a fixed intake, and a queue with everything attached. 7-day free trial, no card.
Sources and further reading
- Harvard Business Review, The Short Life of Online Sales Leads (Oldroyd, McElheran, Elkington, 2011) · firms that responded within an hour were about seven times more likely to qualify the lead
- WhatsApp Business Messaging Policy · opt-in, opt-out and prohibited-use rules every business must follow
ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.