KoltrixOnboarding a new teammate to the team inbox in one week
A day-by-day plan for bringing a new hire into your shared inbox: reading history, drafting with review, owning one category, and a first solo shift.
On this page(9 sections)
Most new hires learn the team inbox by being handed access and told to "jump in when you can." A week later they're either too timid to reply to anything or confidently answering questions with the wrong policy.
A structured first week fixes both problems. The plan below assumes a small team (three to fifteen people) with one or more shared addresses, and a new teammate who will be answering customer or partner email as part of their job. Adjust the pace, but keep the order: context, then reading, then supervised writing, then narrow ownership, then a solo shift.
Before day one: prepare three things
New teammates lose hours on things that take you minutes to write down. Have these ready:
- An address map. Every shared address, what it's for, who monitors it, and what "done" means for a thread there.
- A label glossary. Each label, one sentence on when to use it, and which labels are applied by rules automatically.
- A buddy. One named person who reviews drafts all week and answers "is this normal?" questions without the new hire feeling like a burden.
Also set up access properly before they arrive: their own account, the shared mailboxes they need (and only those), and two-factor authentication enabled on day one rather than "later."
Day 1: The tour
Goal: understand the shape of the inbox without replying to anything.
Spend an hour together walking through:
- Each shared address and a typical email that arrives there.
- How mail gets sorted and labeled, including what automation does.
- The states a thread can be in: new, waiting on us, waiting on the customer, done.
- Who owns what, and how ownership is signaled on your team.
- Where policies live: refunds, discounts, security requests, anything that needs approval.
End the day with the new hire writing down, in their own words, the five things they think matter most. Read it together the next morning. Misunderstandings show up immediately.
Day 2: Read fifty historical threads
Goal: absorb how your team actually writes, not how the style guide says it writes.
Pick around fifty resolved threads from the last couple of months. Choose deliberately:
| Type | How many | Why |
|---|---|---|
| Common how-to questions | 15 | These will be most of their work |
| Bugs and escalations | 10 | Shows how handoffs to engineering work |
| Billing and refunds | 8 | Shows where judgment and approval come in |
| Difficult or upset customers | 7 | Shows tone under pressure |
| Sales or partnership inquiries | 5 | Shows where the boundaries are |
| Mistakes your team made | 5 | Shows how you recover |
That last row is the most valuable and the one teams leave out. Seeing how a colleague apologized for a wrong answer teaches more than ten perfect replies.
Ask the new hire to note any reply they would have written differently and why. Discuss the notes with their buddy at the end of the day.
Day 3: Draft everything, send nothing
Goal: practice writing replies with a safety net.
The new hire drafts replies to real incoming email, and the buddy reviews each one before it's sent. The buddy either sends it as-is, edits and sends (and shows the edit), or explains why it needs a different approach.
Keep a short running list of feedback themes. Typical first-day patterns:
- Replies are too long, or bury the answer below an apology.
- Promises dates or fixes the team can't guarantee.
- Doesn't ask the one clarifying question that would unblock the customer.
- Uses a tone that's either stiffer or more casual than the team's.
By the end of day three, the feedback should be getting smaller. If it isn't, slow down and spend more time on reading.
Day 4: Own one narrow category
Goal: real responsibility with limited blast radius.
Give the new hire full ownership of one well-understood category, such as how-to questions about a single feature, or password and login issues. They reply directly without review in that category, and continue drafting with review for everything else.
Choose a category that is:
- High volume, so they get lots of practice.
- Low risk, so a mistake costs an apology, not money.
- Well documented, so the answers exist somewhere.
Ask the buddy to spot-check a handful of their sent replies at the end of the day rather than reviewing every one.
Day 5: A solo shift with a buddy on call
Goal: confidence.
For a half-day block, the new hire is the first responder for the whole inbox. The buddy is available but not watching. The rules:
- Reply directly to anything they're confident about.
- Draft and ask for review on anything involving money, security, legal topics or an upset customer.
- Escalate anything they don't understand, with a one-line summary of what they think is going on.
Afterward, do a thirty-minute review: what went well, what they escalated, what they wish they'd known.
The week-one checklist
- Own account, correct mailbox access, 2FA enabled
- Address map and label glossary read and discussed
- Fifty historical threads read, notes reviewed
- At least a day of drafting with buddy review
- Owns one category directly
- Completed one solo shift
- Knows exactly what always needs approval
- Knows who to escalate to for bugs, billing and security
What week two looks like
The goal isn't full independence in five days. It's a teammate who knows the territory, writes in the team's voice, and knows exactly where their limits are. In week two, expand their owned categories one at a time, and reduce review to a weekly sample of their replies.
Watch for one thing in particular: new people often under-escalate because they don't want to look like they need help. Make it explicit that escalating early is part of the job, not a sign of weakness.
Key takeaways
- Prepare an address map, a label glossary and a named buddy before day one.
- Read real history, including mistakes, before writing anything.
- Draft with review before sending directly, and start ownership with one low-risk category.
- End the week with a supervised solo shift and an honest debrief.
- Expand ownership gradually and reward early escalation.
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.
