Quick answer
A helpdesk ticketing system is software that records each customer request as a ticket with a category, priority, owner and status, then tracks it until it is resolved. It stops requests from getting lost in chats and emails, shows who is working on what, warns when deadlines are close, and lets managers measure how quickly problems are fixed.
Key takeaways
- A ticket is a single customer request with a category, priority, owner, status and timestamps.
- Ticketing exists to make sure requests that take longer than one reply are not forgotten.
- Core parts: intake from channels, categories and priorities, assignment and routing, SLA targets, internal notes, customer updates and reports.
- Modern helpdesks open tickets from WhatsApp and email conversations, so customers do not have to fill in forms.
- Small businesses benefit as soon as they handle refunds, repairs, complaints or multi-step requests.
A helpdesk ticketing system is software that turns each customer request into a trackable record, called a ticket, and follows it from the moment it arrives until the problem is solved. If you have ever been given a reference number after reporting a fault to your internet provider, you have been on the customer side of one.
This explainer is for Kenyan business owners and managers who keep hearing the term and want to know what it means in practice, whether they need one, and how it fits with WhatsApp, where most of their customers actually write.
How does a helpdesk ticketing system work?
A ticketing system works by giving every request a record with the same fields, then moving that record through a set of statuses until it is closed. Everyone on the team sees the same list, so nothing depends on one person's memory.
A typical ticket contains:
- Customer: who raised it and how to reach them.
- Subject and description: what the problem is, ideally with the original conversation attached.
- Category: the kind of request, such as refund, fault or billing.
- Priority: how urgent it is.
- Owner: the one person responsible for it.
- Status: for example open, in progress, waiting or resolved.
- Timestamps: when it was opened, first answered and resolved.
- Internal notes: updates from colleagues the customer does not see.
What are the main features of a ticketing system?
Most helpdesks share the same building blocks. The table below explains each one and why it matters to a small business.
| Feature | What it does | Why it matters |
|---|---|---|
| Multi-channel intake | Creates tickets from WhatsApp, email, web forms or calls | Customers use their preferred channel |
| Categories | Groups tickets by type | Routing and reports by problem type |
| Priorities | Ranks urgency | Urgent issues are handled first |
| Assignment and routing rules | Sends tickets to the right person or team | No manager has to sort every ticket |
| SLA targets and alerts | Tracks response and resolution deadlines | Promises are kept, breaches are visible |
| Internal notes and mentions | Private team discussion on the ticket | Context stays with the ticket, not in private chats |
| Customer updates | Status messages or a progress page | Fewer "any update?" messages |
| Reports | Volumes, response and resolution times | Shows where the team is struggling |
| Knowledge base (optional) | Self-service articles | Customers solve simple issues themselves |
What does a ticket look like from start to finish? (worked example)
Here is how one request moves through a ticketing system at a beach hotel in Mombasa.
Monday, 19:40. A guest who checked out on Sunday messages the hotel on WhatsApp: she was charged twice for a dinner, once on her card and once on M-Pesa. The reception agent replies within a few minutes, apologises and asks for the M-Pesa confirmation message.
19:52. The guest sends the M-Pesa message. This cannot be fixed in the chat: accounts must check both payments. The agent opens a ticket from the conversation:
- Category: Billing and refunds
- Priority: High
- Owner: the agent herself (she stays responsible for the guest)
- Status: In progress
She adds an internal note asking the accounts team to check both payments. The agent shares the ticket's progress link with the guest and tells her accounts will confirm by Tuesday afternoon.
Tuesday, 10:15. Accounts adds an internal note: the duplicate card charge is confirmed and a refund to M-Pesa is approved. Status changes to Waiting while the refund is processed.
Tuesday, 14:30. The refund is sent. The agent messages the guest on WhatsApp with the M-Pesa reference and sets the ticket to Resolved. The guest's progress link shows Resolved too.
What the system recorded: first response in about 10 minutes, resolution in under 19 hours, two people involved, every step visible. Without a ticket, the request would have depended on the receptionist remembering to chase accounts after her shift. That is the core value of ticketing.
Do small businesses need a helpdesk ticketing system?
Small businesses need ticketing when requests outlive the conversation, not when they reach a certain size. A two-person phone repair shop handling ten repairs a week needs tickets more than a 15-person boutique that mostly answers stock questions.
Signs you are ready:
- Customers chase you for updates.
- Requests involve someone who does not talk to customers, such as a technician, store or accounts.
- You make promises about timeframes.
- You cannot say how many complaints you had last month.
If most questions are answered in one or two messages, a shared inbox may be all you need for now. Our comparison of a helpdesk vs a shared inbox helps you decide.
How does ticketing work with WhatsApp?
Traditional helpdesks were built around email: every new email became a ticket. That model does not fit WhatsApp, where customers send many short messages and most conversations need no ticket at all.
The better model, and the one chat.or.ke uses, is conversation first, ticket when needed. Customers chat in the shared WhatsApp inbox. When a chat turns into a job, an agent opens a ticket from it in one click, with the customer and history attached. In the chat.or.ke helpdesk, tickets have priorities and categories, rules route them by category, agents get notifications for new assignments and for tickets close to breaching their SLA, and customers can follow a private progress link without logging in.
How is a helpdesk different from a CRM?
A helpdesk tracks problems to resolution; a CRM tracks relationships and sales opportunities. A CRM answers "which leads are we about to close?" while a helpdesk answers "which customer issues are still open?"
Both use the same customer records, which is why it helps when they live in one system. In chat.or.ke, a customer's chats, leads and tickets appear on one profile, so a sales agent can see an open complaint before calling about a new order. To understand the CRM side, see what a CRM is for small business.
How do you measure a helpdesk's performance?
The core measures are first response time, resolution time, SLA compliance (the share of tickets that met their targets) and customer satisfaction. Volume by category tells you where problems come from.
Our guide to customer service metrics explains each one with formulas, and setting up customer support SLAs shows how to choose realistic targets.
Published 20 October 2026 Updated 20 October 2026 Plain-text version
