2026-09-26 · MailPilot team
When support volume grows, you have three realistic options. Each buys speed with a different currency: money, control, or customer risk.
| Full-auto responder | Helpdesk seat | Drafting layer (MailPilot) | |
|---|---|---|---|
| Speed | Instant, 24/7 | Human-hours only | Instant drafts, human send |
| Cost model | Cheapest | ~$89/agent/mo | From $0; $19/mo at 300 drafts |
| Control | None — it talks to customers alone | Total | Total — nothing sends without approval |
| Failure mode | Public: wrong answers at scale | Slow: queue backlog | Low: bad drafts get edited or escalated |
Auto-responders answer everything, including the emails that must never get an automated reply: legal threats, chargeback disputes, angry VIPs. One wrong public answer costs more than a year of tooling. The failure isn't the model — it's removing the human from the loop.
Helpdesks are excellent systems of record: macros, SLAs, assignment, analytics. But at 200+ emails/day, most of an agent's keystrokes are re-typing the same five answers. You are paying agent rates for triage work a rules engine does in milliseconds.
A drafting layer keeps the helpdesk (or plain inbox) as the system of record and automates only the first pass: classify into five types, score sentiment and urgency, draft from pre-approved templates, escalate the risky ones. Your team reviews and sends. Volume capacity rises without adding seats or customer risk.
If your volume is low and every email is bespoke — hire people. If your volume is high and 80% is repetitive — automate the first pass, keep the last pass human. That is the design point of MailPilot: free to try, drafts never auto-send.