Support leaders are judged on two things: how happy customers are and how much each resolution costs. Cost per ticket cuts through everything else, and WhatsApp can lower it substantially when used well. Here is how the number works and how to bring it down.
How to calculate cost per ticket
Take total support cost over a period and divide by tickets resolved in that period.
- Include agent salaries and tooling costs.
- Include messaging conversation charges.
- Divide by resolved tickets, not tickets received.
Why WhatsApp lowers the number
Phone support is expensive because a call occupies one agent completely. Chat is different.
- Agents handle several conversations at once.
- Context stays in the thread, so no repeated explanations.
- Media and links resolve issues faster than describing steps.
The levers that actually move it
Three things reduce cost per ticket meaningfully.
- Automate repetitive queries with a chatbot so humans handle only the complex ones.
- Prevent tickets with proactive updates, the cheapest ticket is the one never raised.
- Route efficiently through a team inbox so no one re-triages the same chat.
Do not optimise into bad service
Cost per ticket can be gamed by making help hard to reach, which costs you customers instead. Track it alongside resolution quality and satisfaction, as covered in our helpdesk guide, so efficiency never comes at the expense of the experience.
Frequently asked questions
How do I calculate support cost per ticket?
Add your total support costs for a period, agent salaries, tooling and messaging conversation charges, then divide by the number of tickets actually resolved in that period. Using resolved rather than received tickets gives a truer figure.
Why is WhatsApp support cheaper than phone support?
A phone call occupies an agent completely, while on chat one agent handles several conversations at once. Context also stays in the thread, so customers do not re-explain, and sharing media or links resolves issues faster.
What reduces cost per ticket the most?
Automating repetitive queries so humans handle only complex cases, preventing tickets entirely with proactive updates, and routing efficiently through a shared inbox so no one re-triages the same conversation. Prevention usually has the biggest impact.
Can cutting cost per ticket hurt customers?
Yes, if you reduce it by making support hard to reach. That shifts cost onto customers and drives churn. Always track cost per ticket alongside resolution quality and satisfaction so efficiency does not degrade the experience.
Support more for less. Explore WapBlaster team inbox or start free.