Skip to content

7 Reasons Help Desk Software Is Better Than Email for Support

Ben PuzzuoliFirst published 4 min read

People crossing in front of a red streetcar in downtown Toronto

Email is a fine support tool for a team of one. Requests come in, you answer them, done. It starts to fail the day a second person joins, and it fails in the same seven ways every time. Here they are, with the moment each one starts to hurt.

1. Every request has one owner

In a shared mailbox, nobody owns anything. Two people answer the same email, or each assumes the other has it and nobody does. The customer gets two replies, or none.

In a help desk, every request becomes a ticket with a name on it. Rules assign it on arrival, round robin hands tickets out in turn, and a collision banner warns when a colleague is already replying. "Whose is this?" stops being a question.

When it starts to matter: the second agent.

2. The whole history is in one place

An email thread lives in whoever's inbox it landed in. When that person is away, the context goes with them. When the customer writes back six months later, nobody remembers.

A ticket keeps every message, every reply and every private note between colleagues in one thread, forever. Click the customer and you see every ticket they've ever sent. Internal notes hold what was tried and why it was closed, so the next agent reads instead of asks.

When it starts to matter: the first time someone goes on holiday.

3. Urgent goes first

An inbox sorts by time. The server outage sits under a newsletter and a "thanks!" reply, and the agent works top to bottom.

A help desk sorts by priority. A rule can mark anything with "down" or "urgent" in the subject as high priority, an SLA puts a clock on it, and the queue shows the oldest, most urgent ticket first. The newsletter waits.

When it starts to matter: the first outage that waited behind a thank-you note.

4. The sorting is done before you log in

Sorting an inbox is a human job: read, label, forward, flag. It takes the first hour of every day and it's the job nobody wants.

Rules do it in a help desk. By subject, sender, mailbox or form answer, a ticket is assigned, prioritised, tagged and sometimes answered before an agent sees it. A ticket waiting on a customer who's gone quiet closes itself after the days you choose. The morning queue is already sorted.

When it starts to matter: the day sorting takes longer than answering.

5. Customers can help themselves

An inbox is open only when someone's reading it. A question at 11pm waits until 9am, and the answer is the same one you typed last week.

A help desk comes with a knowledge base customers search before they write, and a portal where they send a ticket and check on it without emailing to ask. The repeat questions stop arriving, and the ones that do arrive come with the details the form asked for.

When it starts to matter: the tenth time you've answered the same question.

6. The team works the same list

Email makes teamwork awkward: forward to a colleague, copy the manager, hope nobody replies to the wrong thread. Shared logins mean nobody's actions are their own.

In a help desk, everyone has their own login and works the same queue. Groups split the work by team, quick responses share the best answers across everyone, and every action has a name and a time on it.

When it starts to matter: the first "I thought you were on that."

7. You get numbers

Ask an inbox how many requests came in last month, how long people waited, or who's behind, and it has nothing to say. You're running support on a feeling.

A help desk counts. Reports show volume by day and hour, response and resolution times, load per agent and tickets per customer. You staff for the busy hours, you spot the agent who's drowning, and you find the product area generating the tickets.

When it starts to matter: the first time the boss asks.

What the switch involves

Less than people expect, because your email address doesn't change. You forward support@ to the help desk and every message that arrives becomes a ticket; replies go back out from support@ as normal email. Customers see nothing different.

On your side, three steps fill an afternoon. Add your agents, so each has a login and every action has a name. Write two or three assignment rules for the tickets you already sort by hand, and turn on the auto-reply with the ticket number. Then put your ten most-answered questions in the knowledge base, because those are the emails that will stop arriving first.

The old inbox stays where it is for reference. Nothing needs migrating; the queue starts with the next email in.

When email is still the right tool

If you're one person with a handful of requests a week, stay in your inbox. The help desk is for the day there are two of you, or a few dozen requests a day, or a customer who asks "did anyone get my email?"

The same goes for using Gmail as a help desk, or an Outlook shared mailbox. It costs nothing extra, everyone already knows how it works, and for an internal desk with one IT person and a few requests a week, labels or flags do the job. It stops working the day two people answer the same email, or someone asks how long people waited and nobody can say.

That day usually arrives before anyone plans for it. If it's close, here's what switching from a shared inbox looks like, and the first 15 days of Cayzu are free with every feature. Your address stays the same; only your side changes.

More on Internal help desk

Running a help desk?

Cayzu is the simple, affordable one. Every feature free for 15 days.