For your first 50 customers, email works great. support@company.com goes to your inbox (or a shared Gmail account), you answer it, done. Simple.

For your first 200 customers, email mostly works. You start CC-ing a coworker on tricky ones. Sometimes you both reply to the same message. Occasionally a message gets buried. But it's manageable.

Around 300 to 500 customers (or 20+ tickets per day), email breaks. And it breaks quietly. You don't notice immediately. You just start dropping balls.

The Signs You've Outgrown Email

You're answering the same ticket twice. Two people see the email, both reply. The customer gets two different answers. This is embarrassing and confusing. Shared inboxes have no collision detection. You can't see that someone else is already typing a response.

You can't find old conversations. A customer references something from two months ago. You search Gmail for 10 minutes and can't find the thread. Was it under their old email? A different subject line? Forwarded by someone else?

You have no idea what's pending. How many unanswered emails are in the inbox right now? Which ones have been waiting the longest? Which ones are urgent? In email, you scroll through and hope you don't miss anything. There's no queue, no priority, no assignment.

You can't track metrics. How many tickets did you get this week? What's the average response time? What topics come up most? Email gives you none of this. You're flying blind.

You're hiring a second support person. If two people are handling tickets, you need some way to assign, track, and not collide. Email wasn't designed for this.

But Don't Move Too Early

Here's the counterpoint: a solo founder with 10 tickets per day doesn't need Zendesk. The overhead of configuring a help desk, managing queues, setting up routing rules, and learning a new tool exceeds the benefit.

If you can answer every email within a few hours and nothing is falling through the cracks, email is fine. Don't add complexity for complexity's sake.

The tipping point is usually around 15 to 25 tickets per day, or when you add a second person to handle support. Below that, email (or a simple shared inbox like Google Collaborative Inbox or Fastmail shared mailboxes) is sufficient.

What to Look for in Your First Help Desk

Your first help desk should be simple, affordable, fast to set up, and easy to drop if it doesn't work out. You don't need enterprise features. You need four things:

A shared queue with assignment. Multiple agents can see all tickets. Each ticket gets assigned to one person. No collisions. No duplication.

Ticket status tracking. Open, pending, waiting on customer, resolved. At a glance, you see what needs attention. Old tickets surface automatically.

Basic metrics. Tickets per day, response time, resolution time, tickets by category. Enough to know if things are getting better or worse.

Search. Find any customer's history in seconds.

That's it for version one. Don't worry about automation rules, SLA management, custom workflows, or AI features until you actually need them.

The Budget Options

Help Scout: $50/month, contact-based pricing, unlimited users. Good for small teams because you don't pay per agent. Clean interface, easy to learn.

Freshdesk: Free program for up to 2 agents for 6 months. $15/agent/month for the Growth plan (billed annually). Solid for budget-conscious teams.

Zoho Desk: Free tier for up to 3 agents. $7/agent/month for basic paid. Good if you're already in the Zoho ecosystem.

Supp: $0.20/classification, no base fee. Not a traditional help desk, but if you want AI classification and routing without a per-seat subscription, it handles the triage layer. Pair it with a simple shared inbox for human responses.

Don't start with Zendesk or Intercom. They're powerful but expensive and complex. A 5-person startup doesn't need enterprise workflow automation. You need a shared queue that doesn't lose emails.

The Migration

Moving from email to a help desk takes about a day.

Set up email forwarding: route support@company.com to your new help desk's intake address. Old emails stay in your email archive. New emails go to the help desk.

Set up your team: add agents, define basic roles (who handles what), and agree on status conventions (what "pending" means vs "on hold").

Create 5 to 10 saved replies (also called macros or canned responses) for your most common ticket types. You'll add more over time.

That's the migration. Don't try to import your entire email history. Don't spend a week configuring automation rules. Get the basic flow working and iterate.

What Changes

The immediate difference: visibility. You can see every open ticket, who's assigned to it, and how long it's been waiting. No more scrolling through email and hoping.

Within a week, you'll notice: consistent response times (because the queue surfaces old tickets), fewer dropped conversations, less confusion about who's handling what, and the relief of knowing nothing is slipping through unnoticed.

Within a month, you'll have enough data to answer basic questions. "What's our average response time?" "What are customers asking about most?" "Are we getting more tickets this month than last?" "Which agent is carrying the heaviest load?" These answers inform everything from hiring decisions to product priorities.

The help desk doesn't make support better by itself. It makes support visible. And visibility is the prerequisite for improvement.