WhatsApp Customer Support: Tickets, SLAs & KB
Customers don't open a portal to file a ticket anymore. They message you on WhatsApp — the same number they'd use to text a friend — and they expect a person, not a form. That's great for them. It's a nightmare for a support team, because a WhatsApp chat has no status, no owner, no deadline and no record of whether the issue was actually resolved. A question comes in, someone half-answers it, the thread scrolls away, and three days later the customer messages again, angrier, and nobody knows what happened the first time.
The fix isn't to drag customers off WhatsApp into a ticketing portal they'll ignore. It's to make the chat itself accountable — to turn every conversation into a ticket with an owner and a deadline (an SLA), backed by a knowledge base so answers are consistent and correct. That's what good WhatsApp customer support software does: it keeps the channel customers love and adds the structure your team needs to never drop one.
This is the hub guide for support on WhatsApp. We'll cover why chat-only support fails at scale, what a real support desk looks like (tickets, SLAs, a KB), the metrics that tell you if it's working, and how to set it up on the number you already use.
TL;DR
- A chat is not a ticket. Without status, owner and a due time, support requests silently fall through the cracks — and you can't measure what you can't track.
- Three pillars turn WhatsApp into a real helpdesk: tickets (accountability), SLAs (deadlines), and a knowledge base (consistent, correct answers).
- The official WhatsApp Business API can't access groups — so community and broker-group support is invisible to API tools. A workspace on your own number can.
- Measure first response, resolution time and SLA-met rate — not vanity volume. Most support teams we talk to are flying blind on all three.
- Tenashi adds tickets, SLAs and AI-assisted answers on your existing number via a QR scan — no new SIM, no template approvals, no per-message fees.
Why chat-only WhatsApp support breaks down
The free WhatsApp Business app, or one shared phone passed between agents, works for the first dozen customers. Past that, the cracks aren't subtle.
A conversation has no state
In a ticketing tool, every request is open, pending, or resolved. In WhatsApp, it's just a thread that's either at the top of the list (recent) or buried (old). There's no way to glance at your inbox and answer the only question that matters: what still needs a reply, and by when? An issue that's been "waiting on the customer" for a week looks identical to one your team forgot about.
Nobody owns it
When five agents can see the same chat, the predictable thing happens: everyone assumes someone else has it, so no one does. Or two people reply at once and contradict each other. Without explicit assignment, "shared" really means "nobody's." We cover the fix in our guide to assigning WhatsApp chats to agents.
There's no deadline, so there's no urgency
"We'll get back to you" has no teeth without a clock. A support promise of "within 2 hours" only means something if the system knows the clock started, warns you before it runs out, and flags the ones that breached. Chat has none of that.
Answers are inconsistent
Three agents answer the same refund question three different ways — one correct, one outdated, one that promises something you don't offer. Every wrong answer is a future complaint. Without a shared source of truth, quality is a coin flip that depends on who happened to pick up the chat.
You can't measure any of it
How fast do you respond? What's your resolution time? How many requests breached their promised window last month? In a chat-only setup, the honest answer is we have no idea. And support you can't measure is support you can't improve. More on this in WhatsApp support metrics that actually matter.
The instinct is to bolt on the WhatsApp Business API (WATI, AiSensy, Interakt and similar). That adds some structure — but it also adds template approvals, per-message fees, and a hard limit: the API structurally cannot access WhatsApp groups. If any of your support happens in groups — community support, a wholesale buyers' group, a society or broker group — it's completely invisible to those tools. We'll come back to that.
The three pillars of WhatsApp support software
Turning WhatsApp from a chat app into a support desk comes down to three things working together. Skip any one and the other two leak.
| Pillar | What it does | What breaks without it |
|---|---|---|
| Tickets | Gives every request a status and an owner | Issues get half-answered and lost |
| SLAs | Puts a deadline on each ticket | "We'll get back to you" never happens |
| Knowledge base | One correct, consistent answer | Three agents, three different answers |
The rest of this guide takes each in turn, then shows how to measure the whole thing.
Pillar 1: Tickets — turning chats into accountable work
A ticket is a chat with a job to do. It has a status (open, pending, resolved), an owner (the agent responsible), and a history (what's been tried). That's the whole idea — but it changes everything, because now your inbox is a queue of work, not a wall of messages.
What a WhatsApp ticket should carry
- Status — so you can filter to "open and unassigned" and clear the real backlog, not scroll.
- An owner — one agent on the hook, visible to the team, so nothing is everyone-and-no-one.
- A priority — an outage complaint and a "do you ship to Pune?" are not the same urgency.
- Internal notes — context the customer never sees: "refund approved by finance, processing." Use internal notes and @mentions so the next agent isn't starting cold.
- The full conversation — the chat is the ticket. No copy-pasting between WhatsApp and a separate portal; the customer keeps texting the same number.
Why this beats a portal-based helpdesk
Traditional helpdesks make the customer come to you — open a portal, create a login, fill a form. Most won't; they'll just message you on WhatsApp anyway, and now you're running two systems. Putting the ticket inside the WhatsApp chat removes that friction entirely. The customer does nothing different; your team gets all the structure. We go deeper in WhatsApp helpdesk and ticketing: how it works.
Routing tickets to the right agent
A ticket is only as good as who it lands on. Auto-assignment by team, topic or round-robin gets each request to the right person without a manager triaging by hand. Pair that with auto-assign and auto-tag rules so a chat that mentions "invoice" lands with billing and gets tagged before anyone touches it. For the human side of routing — roles, who sees what — see roles and permissions for a WhatsApp inbox.
Pillar 2: SLAs — putting a clock on every promise
An SLA (service-level agreement) is the deadline your support runs against. "First response within 2 hours, resolution within 24" — but as a rule the system enforces, not a line in a help doc nobody reads. Without SLAs, tickets have owners but no urgency. With them, your queue sorts itself by what's about to breach.
The two SLAs that matter most
- First-response time — how long until a human acknowledges the customer. This is the one customers feel most. A fast "we're on it" buys enormous goodwill even before the fix lands.
- Resolution time — how long until the issue is actually closed. Slower, but it's the number that determines whether they stay a customer.
Set different targets by priority — an outage gets a tighter clock than a feature question — and by plan tier if you offer premium support. Our dedicated guide, setting SLAs for WhatsApp support, walks through choosing targets you can actually hit.
Make the clock visible
An SLA only works if the team sees it ticking. The queue should surface what's due soon and what's already breached, so agents work the most urgent ticket next instead of the most recent message. A deadline nobody can see is a deadline nobody meets.
Don't set SLAs you can't keep
A 15-minute first-response SLA looks great on a sales page and humiliates you in practice. Set targets against your real staffing and hours. Pair SLAs with honest WhatsApp business hours and an away message, so the clock reflects when you're actually open — not a promise that quietly breaches every night at 9pm.
Pillar 3: A knowledge base — consistent, grounded answers
The third pillar is the one teams skip, and it's the one that quietly determines quality. A knowledge base (KB) is your single source of truth: the canonical answer to every common question, written once and reused everywhere. It does two jobs — it makes agents faster and more consistent, and it can power self-service so customers solve simple things without waiting.
Start with your repeat questions
You already know your top 20 support questions — they're the ones you answer every single day: shipping times, refund policy, how to reset something, what's included in a plan. Write the correct, current answer to each, once. That list is your starter KB. The full method is in building a knowledge base for WhatsApp support.
Canned replies are the KB's front line
The fastest way a KB pays off: turn each canonical answer into a canned reply an agent can drop into a chat in one tap. Same correct wording every time, in a fraction of the keystrokes. Set these up properly with canned replies for WhatsApp — it's the single highest -leverage thing most support teams can do this week.
Grounded answers beat improvised ones
"Grounded" means the answer traces back to your KB, not to whatever the agent half-remembers. That's how you kill the three-agents-three-answers problem. When the source of truth is shared, a new hire on day one answers the refund question as accurately as your most senior agent — because they're both reading from the same page, not improvising.
Keep it alive
A KB rots the moment your policy changes and the article doesn't. Assign an owner, review it on a cadence, and update the canned reply the same day a policy changes. A stale KB is worse than none — it confidently hands out wrong answers at scale.
What about support that happens in groups?
Here's the gap most "WhatsApp support" tools won't mention: a lot of support doesn't happen in DMs. It happens in groups — a customer community, a wholesale buyers' group, a society or broker group, a class cohort. Someone posts "anyone else's order delayed?" and a dozen people pile on.
The official WhatsApp Business API cannot access groups at all — it's a structural limit, not a setting. So every API-based support tool (WATI, AiSensy, Interakt, DoubleTick) is blind to group support entirely. If your customers ask for help in groups, those questions never reach your ticket queue. We unpack the why in can the WhatsApp Business API access groups?.
A workspace that runs on your own number sees groups as first-class conversations: you can read, reply, assign and take notes on group threads, and even summarize a long, noisy group chat into the actual support items buried in it (AI summaries are a Growth & Scale feature). For support teams running communities, this is often the deciding factor.
The metrics that tell you it's working
Tickets, SLAs and a KB only matter if they move numbers you can see. Track these — and ignore vanity volume, which tells you nothing about quality.
| Metric | What it tells you | Healthy direction |
|---|---|---|
| First-response time | How fast a human acknowledges | Down |
| Resolution time | How fast issues actually close | Down |
| SLA-met rate | % of tickets answered within the promise | Up |
| Reopen rate | How often "resolved" wasn't | Down |
| Backlog age | How old your oldest open ticket is | Down |
The point isn't to obsess over dashboards. It's that a chat-only setup can't produce any of these numbers, so you genuinely can't tell whether support is improving or quietly getting worse. The moment chats become tickets with deadlines, every one of these becomes measurable. Our guide to WhatsApp support metrics that actually matter covers what to watch and what to ignore.
Where Tenashi fits
Most WhatsApp support tools force a trade you shouldn't have to make: get structure (tickets, SLAs) or keep the channel customers love — but not both, and never in groups.
Tenashi is the WhatsApp workspace for teams, and it's built to give you both. You link your existing WhatsApp number with a QR scan — no new SIM, no porting, no waiting on the API — and your whole team works one shared inbox that covers DMs and groups. On top of that inbox sits a real support desk: every chat can become a ticket with an owner and status, with SLAs putting a deadline on each one so nothing quietly breaches. Because it's your own number rather than the API, there are no template approvals and no per-message fees — you pay a flat price, not per support reply.
For consistency, canned replies turn your knowledge base into one-tap answers, and on Growth & Scale, AI can suggest replies, summarize a long group thread into the real issues, run OCR on a screenshot a customer sends, and translate messages inline (all four are Growth & Scale only). Under every conversation is a real CRM — contacts, custom fields and history — so an agent picking up a ticket sees the whole relationship, not just the latest message.
Because support volume means a lot of sending, Tenashi paces messages like a human — jitter, typing presence, warm-up, and duplicate/burst guards — to reduce the risk to the number that runs your support (risk reduction, not a guarantee; WhatsApp's policies can always change). You can read how that works in our guide to avoiding a WhatsApp ban.
Pricing is flat: Starter $18/mo, Growth $27/mo, Scale $56/mo, with a 3-day Growth trial, no card.
Start your free trial → · See every feature
How to set up WhatsApp support, step by step
A practical sequence you can run this week:
- Connect your number. Link your existing WhatsApp number to a shared workspace by QR scan — no new SIM, no porting. See connect your existing WhatsApp number.
- Turn chats into tickets. Decide your statuses (open / pending / resolved) and start assigning an owner to every incoming request, so nothing is everyone's-and-no-one's.
- Set two SLAs. A first-response target and a resolution target, sized to your real hours and staffing — not aspirational numbers you'll breach nightly.
- Write your top 20 answers. Capture the questions you answer daily as canned replies. That's your starter KB and your single biggest consistency win.
- Add routing. Auto-assign and auto-tag so each ticket lands on the right agent, tagged, before a human triages.
- Measure. Watch first-response time, resolution time and SLA-met rate. Fix the one that's worst.
For teams moving off an API tool or a single shared phone, our migration guide to a WhatsApp workspace covers doing this without losing history or downtime.
Related guides
- WhatsApp helpdesk and ticketing: how it works
- Setting SLAs for WhatsApp support
- Building a knowledge base for WhatsApp support
- WhatsApp support metrics that actually matter
- How to use WhatsApp for customer service
- WhatsApp shared inbox for teams
FAQ
What is WhatsApp customer support software?
It's software that turns WhatsApp conversations into structured support: every chat becomes a ticket with an owner and status, SLAs put a deadline on each one, and a knowledge base keeps answers consistent. A workspace like Tenashi adds all of this on your existing WhatsApp number, so customers keep texting the same number while your team gains accountability and metrics.
What's the difference between a WhatsApp ticket and a normal chat?
A normal WhatsApp chat has no status, owner or deadline — it's just a thread that scrolls. A ticket adds those three things: a status (open, pending, resolved), one accountable agent, and a clock. That's the difference between requests that get tracked to completion and requests that get half-answered and lost in the inbox.
Can I set SLAs for WhatsApp support?
Yes. With a support desk on top of WhatsApp, you set targets like "first response within 2 hours, resolution within 24" and the system tracks each ticket against them — surfacing what's due soon and what's breached. Set targets against your real hours and staffing so the clock reflects when you're actually open, not an aspirational promise.
Does WhatsApp support software work with groups?
It depends on the tool. The official WhatsApp Business API can't access groups at all, so API-based tools (WATI, AiSensy, Interakt, DoubleTick) are blind to any support that happens in groups. A workspace like Tenashi runs on your own number and treats groups as first-class chats, so community and group support reaches the same ticket queue as your DMs.
Will running support through a tool get my WhatsApp number banned?
It can if the tool blasts messages without pacing. Tenashi paces every send like a human — with jitter, typing presence, warm-up and duplicate/burst guards — which reduces the risk to your number. No tool can guarantee against a ban, since WhatsApp's policies can change, but human-paced sending on your own number is far safer than bulk blasting.
Do I need a new number or the WhatsApp API for this?
No. Tenashi links your existing WhatsApp number with a QR scan — no new SIM, no porting, and no API approval process. There are also no template approvals and no per-message fees: you pay a flat plan price and your customers keep messaging the same number they always have.
Stop losing support requests in the chat scroll. Start your free trial and turn every WhatsApp conversation into an accountable ticket — with deadlines, consistent answers, and the metrics to prove it's working.