Help Desk Software Guide: A Free-First Approach

A support inbox spread across five different apps isn't a system, it's a leak. Tickets fall through when a WhatsApp message and an email about the same order never talk to each other — and by the time your agent replies, the customer has already sent two more messages asking "did you see this?"

Help desk software exists to fix exactly that: one place where every conversation becomes a ticket, gets assigned, has a deadline, and gets closed properly. The part most guides leave out is that you don't need to pay per agent, per seat, or per month to get a real one. WaSMS gives you full help desk software — tickets, SLAs, routing, and AI-drafted replies — free, because it already sits on top of every WhatsApp, SMS, and email conversation your business has.

What help desk software actually gives you

At the core, help desk software turns messages into trackable units of work instead of a chat thread that scrolls away and gets forgotten. That means:

• A ticket with a status (open, pending, closed) and a named owner
• A full history of every message tied to that customer, regardless of channel
• Metrics: first response time, resolution time, open backlog
• A clean way to say "this one's George's, not mine" without losing the thread

A shared inbox works fine until you cross roughly two agents or twenty conversations a day. After that point, someone always assumes someone else already replied, and customers start chasing you instead of the other way around.

If your support today runs out of a personal WhatsApp number or a shared Gmail login, adding a proper ticket layer is the single highest-leverage change you can make this month.

When you probably don't need one yet

If you're a single person answering a handful of messages a day, a full ticket system is likely overkill — a well-organized inbox is fine until volume or headcount grows. The signal to switch isn't a specific number of messages, it's the first time you catch yourself asking "wait, did anyone reply to this customer yet?"

Tickets, SLAs, and routing

Every incoming message in WaSMS — a WhatsApp reply, an SMS, an inbound email — automatically becomes a ticket if the customer doesn't already have one open. From there you set:

• SLA targets — for example, first response inside 15 minutes on WhatsApp, 4 hours on email
• Routing rules — new customers go to Tier 1; anything containing "refund" or "cancel" goes straight to a senior agent
• Escalation — no reply after X minutes automatically pings a supervisor

Consider what routing looks like without any rules at all: an incoming message sits in a shared inbox, visible to everyone, owned by no one, until someone happens to notice it and decides to reply. That works for a handful of messages a day. It falls apart the moment two agents are online at once, because both assume the other saw it first — and the customer, who has no visibility into any of this, just sees silence.

Take Mara, who runs a small online home-goods store. Her three-person support team used to argue about who owned which email thread. After switching to routing by rule, refund requests go straight to her most experienced agent, and everything else round-robins between the other two. Her average first response time dropped from around six hours to under twenty minutes — not because anyone got faster at typing, but because nothing sits unclaimed anymore.


When an SLA is about to breach, WaSMS flags the ticket in the queue and, if you've set it up, notifies a supervisor rather than letting it quietly slip. That single change usually does more for customer satisfaction scores than any script an agent could memorize.

Setting up your first routing rules

You don't need a complex rule set on day one. Most teams start with three rules and add more as patterns emerge:

1. Route anything mentioning "refund," "cancel," or "complaint" to your most senior agent
2. Route first-time customers (no prior ticket history) to whichever agent is least loaded
3. Escalate anything unanswered after your slowest acceptable wait time (start conservative — 30 minutes is reasonable for most small teams)

Watch your ticket reports for two weeks, then adjust. If one agent is consistently overloaded, the rule needs tightening, not the agent needing to work faster.

AI-assisted responses

This is where free help desk software starts to beat a paid one. Every ticket in WaSMS can carry an AI-drafted reply, generated by the same AI Actions layer that reads your actual business data — product catalog, FAQ, and the resolutions from your own past tickets. The agent reads the draft, edits if it needs a human touch, and sends. For routine questions (hours, pricing, order status), you can let AI reply automatically and only queue the harder ones for a human.

This isn't a generic chatbot bolted onto a widget. Because the AI is trained on your real business data, its drafts sound like your business rather than a template pulled from nowhere. For the fuller picture of what this layer can and can't do, see our guide on AI for customer service.


Teaching it your macros

If your team already has canned responses for common questions — return policy, shipping windows, business hours — feed those into WaSMS as source material rather than starting from scratch. The AI uses them as its baseline phrasing, then adapts the details (order number, product name, customer's own words) per ticket, so replies feel personal instead of copy-pasted, even though the underlying policy text is standardized.

Across-channel unification

The reason "help desk" and "inbox" are the same product in WaSMS is that customers don't think in channels. Sarah messages your WhatsApp Business number about a delayed order, then emails a screenshot of her receipt later when she can't find the chat again. If those live in two separate systems, your agent has no way of knowing they're the same complaint.

WaSMS keeps one customer timeline no matter which channel they used. A ticket opened on WhatsApp can get a reply sent by email, and the customer just sees a normal message land in whichever app they check. Here's a simplified look at replying through the API without tracking the original channel yourself:

curl -X POST https://api.wasms.net/v1/tickets/8842/reply \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "auto",
    "message": "Hi Sarah, your order shipped this morning — tracking below.",
    "attachments": []
  }'

"channel": "auto" tells WaSMS to reply on whichever channel the customer last used. For the full walkthrough of what a merged, cross-channel view looks like day to day, read unified inbox for WhatsApp, SMS, and email.


Cost vs value

Most help desk vendors charge per agent, per month — typically $15 to well over $100 depending on tier, often with AI features locked behind an even higher plan. A five-person team on a mid-tier plan can land at $300–$500 a month before anything else is added.

WaSMS's ticketing, SLAs, routing, and AI drafts are free because they're part of the same conversation layer as your messaging channels — the more your real conversations run through WaSMS, the better its AI gets, which is the actual business model. There's no seat count and no "starter plan caps you at 3 agents" wall to hit later.

If you're weighing this against a free CRM for conversations, the two overlap on purpose — a help desk is built for "handle today's messages," a CRM leans toward "track this customer over months." Most small teams end up using both, from the same account, at no extra cost.

What to read next

• Unified inbox: WhatsApp, SMS, and email in one place
• AI for customer service: what it can and can't do
• WhatsApp customer service: the full guide