Why we still answer our own support tickets in 2026

When we started in 2012, answering your own support tickets was just how things worked. You built the site, you knew the client, and when something broke at 11pm you fixed it because nobody else knew the codebase.

Then the industry changed. Agencies our size started outsourcing "tier-1" support to overseas call centers. The math seemed obvious: pay a low hourly rate to answer the first email, escalate only what's complicated. More margin, less friction, scale.

Why we didn't

Three reasons, in order of importance:

1. The person answering the email needs to know the code. Most hosting issues aren't "my site is down" — they're "my form stopped sending email after I installed that new plugin." The fix takes five minutes if you know the stack. It takes two days of back-and-forth if you don't.

2. Tickets are a leading indicator. Every ticket is a signal. If five people ask the same question this month, the product needs a fix — a docs update, a better error message, a default changed. Outsourced support filters those signals into a dashboard nobody reads.

3. The clients who stay are the ones who feel heard. Our churn rate is under 3% annually. I'd bet a meaningful chunk of that comes from the fact that when you email us, you get a reply from someone who can actually fix the thing.

What this costs us

Honestly? Not as much as you'd think. We've built the habit of writing good docs (so fewer tickets show up in the first place), and we set aside the first hour of every day for inbox triage. Most things resolve in one exchange.

We're not saying this is the only way. Plenty of companies do great work with outsourced support. But for a small, opinionated team that wants to keep clients for a decade, answering your own tickets is still the right call.