KoltrixHow founders hand off the inbox to their first hire
A staged playbook for founders handing customer email to their first hire: shadowing, reviewed replies, owning a category, then owning the whole inbox.
On this page(10 sections)
For the first year or two, the founder usually is the support team. Every customer email passes through one person who knows the product, the history, and the customer by name, and that is exactly what makes handing it off so hard.
The handoff fails in two common ways. Either the founder dumps the inbox on the new hire on day one with "just use your judgment," or the founder never really lets go and reviews every reply forever. This playbook lays out a staged handoff that gets the new person to full ownership in a few weeks, with the founder's knowledge written down along the way.
Before day one: write down what's in your head
You can't hand off judgment you've never articulated. Spend an hour or two before your hire starts writing short answers to these questions. Bullet points are fine.
- Tone. How do you sign emails? First name or full name? How formal are you with enterprise customers versus indie developers?
- Refunds and credits. What do you actually do when someone asks for money back? What's your informal limit?
- Who gets escalated to you. Which customers, topics or situations should always come to you? (Common answers: largest accounts, legal or security questions, press, anything involving a public complaint.)
- What you never say. Roadmap dates, discounts, comparisons with competitors, whatever you've learned to avoid.
- Known recurring questions. The ten things people ask every month, with your usual answer.
This document doesn't need to be polished. Its job is to make your defaults visible so the new hire can copy them before developing their own.
Set up access properly
Before the handoff starts, the new hire needs their own account and access to the shared addresses, not your password. Give them access to the mailboxes they'll work (support@, hello@) and keep sensitive ones (billing details, investor mail, security@) restricted until there's a reason to share. Tools with per-mailbox permissions, like Koltrix's shared mailboxes, make this a settings change rather than a workaround.
Also decide which address the new hire replies from. Replies should come from the shared address with their name in the signature, so customers stay attached to the team rather than to whichever person answered first.
Stage 1: Shadow (first few days)
The new hire reads, you reply.
- Have them read a few weeks of historical threads, especially long or difficult ones.
- As new mail comes in, they read it first and tell you what they'd do: reply, escalate, ignore, label. You compare it with what you actually do.
- Talk through disagreements. These conversations transfer more judgment than any document.
The goal is not speed. It's calibration: the new hire starts predicting your decisions.
Stage 2: Draft with review (about a week)
They write, you approve.
- The new hire drafts replies to everything except your escalation list.
- You review before sending. Keep feedback specific: "Answer the question in the first line," "We don't promise dates," "This one should come to me."
- Track the kind of feedback you give. If the same note comes up three times, add it to the document from day zero.
Set a time limit on reviews. If drafts wait half a day for your approval, customers wait too, and the hire learns that their work is blocked on you.
Stage 3: Own a category (one to two weeks)
They send without review in one area.
Pick a category that is frequent, low-risk, and well documented. How-to questions are a common first choice. Billing questions often come later because they involve money and judgment.
| Category | Typical risk | Suggested stage to hand off |
|---|---|---|
| How-to and setup questions | Low | Early in stage 3 |
| Bug reports | Low to medium | Stage 3 |
| Feature requests | Low | Stage 3 |
| Billing and refunds | Medium | Late stage 3, with a clear limit |
| Cancellations | Medium | Stage 4 |
| Large accounts, legal, security | High | Stays with founder until explicitly moved |
You still spot-check a few sent replies each day, but after sending, not before. Expand the categories as confidence grows.
Stage 4: Own the inbox
The new hire owns the inbox; you are an escalation path.
- They triage everything and decide what comes to you.
- You stop reading the inbox daily. This is the hard part. If you keep reading, you'll keep replying, and the hire will never fully own it.
- Hold a short weekly review: interesting threads, recurring problems, anything they weren't sure about.
At this stage, the escalation list should be short and explicit. "Anything from our three largest accounts" is a clear rule. "Anything important" is not.
Letting go of perfection
The new hire will not write exactly like you. Some replies will be more formal, some less. A few will contain answers you'd have phrased differently. That's fine, and it's the price of having support that doesn't depend on one person.
What matters is whether customers get correct, timely, kind answers. If they do, resist the urge to rewrite. Save your feedback for errors of fact, policy, or judgment, not style.
It helps to remember what the alternative costs. Every hour you spend in the inbox is an hour you're not spending on the things only a founder can do.
Signs the handoff is working
- The new hire escalates fewer things over time, and the escalations they do send are the right ones.
- You learn about customer problems from the weekly review, not from reading the inbox.
- Customers reply to the new hire by name.
- The day-zero document has grown, and the new hire is the one editing it.
Signs it isn't
- You're still reviewing most replies weeks in.
- The new hire waits for you before answering anything unusual.
- Customers keep emailing you directly because that's how they get answers.
If customers bypass the shared address, reply from the shared address, introduce your colleague, and copy them in. After a few rounds, customers learn where to write.
Bottom line
Hand off the inbox in stages: shadow, draft with review, own a category, own the inbox. Write down your defaults before the hire starts, give them proper access instead of shared passwords, keep a short explicit escalation list, and then genuinely step back. The new hire's replies won't sound exactly like yours, and that's how you know the inbox no longer depends on you.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
