What Gmail genuinely gets right
Worth saying before the criticism, because a lot of comparison writing skips it and reads as sales copy for the thing being sold.
- Delivery and deliverability, which is a much harder problem than it looks.
- Search that actually finds a conversation from eight months ago.
- Spam filtering you would not want to reimplement.
- It costs nothing extra and everybody already knows how to use it.
If you are pre-launch or answering three emails a week, buying a support tool is premature optimisation. Come back when the failure below has actually happened to you.
The three ways it breaks, in the order they happen
1. The fixed bug nobody was told about
Someone reports a crash. You reply asking for a log, they send it, you reproduce it, and you archive the thread to get it out of the way while you work. Two days later you ship the fix. The customer hears nothing. They did not get a broken product, they got silence, and silence is what they will remember and repeat. In Gmail this conversation is in exactly the same place as one you finished properly.
2. The refund you issued and never mentioned
A refund goes out through Stripe. Stripe emails a receipt, which is a transaction record and not an answer. The person who wrote in asking whether they could get their money back never receives a reply from a human, and the last thing they remember about your product is an unanswered email.
3. The feature request that shipped six weeks later
The single highest-value email you can send is “you asked for this in June, it is in today’s release”. Almost nobody sends it, because by then the thread is buried under six weeks of other mail and there is nothing tying the shipped feature back to the person who wanted it.
Why the usual advice does not hold
Every article about this recommends the same three things, and each has the same defect.
- Star it and use the starred view. Works until the day you are debugging at 2am and archive without starring. The system fails exactly when you are busiest, which is the only time it matters.
- Snooze the thread until Friday. Snoozing guesses a date. If the fix takes an hour you sit on it for four days; if it takes two weeks the thread comes back before there is anything to say and you snooze it again.
- Keep a separate list in a task app. Now there are two systems and neither is authoritative, so the real state is in your head, which is where it was to begin with.
The common flaw is that all three require an act of memory at the moment of distraction. Any fix that depends on remembering is not a fix for a problem that is caused by forgetting.
The smallest change that actually works
Stop treating a conversation as one thing with one status, and track two facts about it: is the work done, and does the customer know. Four states fall out of that, and only one of them is finished.
- Needs you. You owe them work, a reply, or both.
- Waiting on them. The ball is in their court, and it comes back if they go quiet.
- Reply owed. You fixed it. They still do not know. This is the one that slips.
- Closed. Handled and told. Only now do they leave your list.
You can run this on paper. The reason to use software for it is that software can put a conversation into “reply owed” without you having to remember to, and can refuse to let it look finished until you have actually written back.
Questions people actually ask
Is Gmail good enough for customer support?
For a while, yes, and longer than most tool vendors admit. Gmail handles the delivery, the search and the spam filtering, and for the first months of a product it is genuinely the right answer. It breaks on one specific thing: it has no idea a customer is still owed a reply once you archive the thread and go and do the work.
What about Gmail labels and stars? Do those solve it?
They help, and they fail the same way every manual system fails: they depend on you remembering to apply them at the exact moment you are distracted by the actual work. A star you forget to add is indistinguishable from a conversation that is finished, which is precisely the state that costs you the customer.
Do I have to leave Gmail to use Moorline?
No. Moorline reads the same Gmail mailbox over IMAP and sends replies back into the same threads over SMTP. Gmail keeps working exactly as it does today, on the web and on your phone. Nothing changes about your MX records and there is no forwarding address.
When should I move off Gmail alone?
When you can name a customer who did not hear back about something you actually fixed. Before that, the tooling is premature. After that, it has already cost you more than any support tool charges.