The customer support onboarding SOP: ramp a new agent in 30 days

A new support agent's first month sets their ceiling. Onboard them well and they handle refunds, escalations, and edge cases like a veteran by week five. Wing it, and six months later they're still pinging the team lead on every unusual ticket, and your CSAT shows it.

The difference is rarely talent. It's whether there's an onboarding SOP or just a shadow-and-hope routine. New hires with documented procedures to learn from reach full competency around 40 percent faster, and teams that run on SOPs resolve tickets 35 to 50 percent quicker. That gap compounds with every hire.

This is the support onboarding SOP we use with DTC brands: what to set up before day one, the 30-day ramp week by week, the macros and tone that keep every reply on-brand, and the escalation tiers that tell a new agent exactly when to stop and ask.

Why document support onboarding

Most support onboarding is a senior agent saying 'sit with me for a few days, you'll pick it up.' It works until that senior agent is slammed, or the new hire is too polite to keep interrupting, or three different mentors teach three different ways to handle a refund.

A documented onboarding fixes three things at once: speed, because the new hire learns from a source that's always available; consistency, because everyone learns the same refund flow, the same tone, the same escalation rule; and resilience, because your onboarding doesn't walk out the door when your best agent does.

Set up before day one

The fastest ramps start before the new agent logs in. Have these ready so they spend day one on real tickets, not waiting on access:

• Access: a helpdesk seat (Gorgias or your tool), Shopify admin at the right permission level, and your SOP library. Provision it the day the offer is signed, not the morning they start.
• A reading list: the 5 to 8 SOPs that cover 80 percent of tickets. Refund flow, order status, address change, returns, and your top product questions. Not all 60 SOPs, the ones they'll use in hour one.
• Macros: the canned responses for those same common issues, so they edit a tested template instead of writing from scratch under pressure.
• A buddy: one named senior agent who owns their questions for the first two weeks. A single point of contact beats a vague 'ask anyone'.

Define what ready looks like before they start. Write down the 30, 60, and 90 day marks: what a new agent should handle alone at each. You cannot ramp someone toward a target nobody wrote down.

The 30-day ramp, week by week

Thirty days is enough to take a new agent from shadowing to full volume if the weeks are structured. Here's the ramp:

1. Week 1, learn and shadow: they read the core SOPs and watch a senior agent work live, and answer nothing solo. By Friday they should be able to explain your refund and returns flows back to you.
2. Week 2, supervised tickets: they handle real tickets from the easy queue (order status, simple questions) with their buddy reviewing every reply before it sends. Volume is low on purpose. The goal is accurate, on-tone replies on common issues.
3. Week 3, solo with review: they work the full common queue unsupervised, but a senior agent reviews a sample of their closed tickets each day and gives feedback. Escalations still go to the buddy. The goal is 20 to 30 tickets a day on standard issues.
4. Week 4, full volume: they own their queue, escalate by the tiers instead of by instinct, and a weekly QA review replaces the daily check. The goal is hitting the team's first-response and CSAT targets on standard tickets.
5. Day 30, the ready review: sit down with the definition of ready you wrote in advance. What can they handle alone, what still needs a buddy, what's the plan for days 31 to 60. The ramp continues, but now it's measured.

Macros and brand voice

Macros are how a new agent sounds like a veteran by week two. A good macro library gives them a tested starting point for every common issue, so they edit instead of compose, and every reply lands in the same brand voice.

Document the voice explicitly, because 'sound friendly' is not a standard. Write down the rules: the greeting, whether you use the customer's first name, how you apologize without admitting fault, the sign-off. New agents copy what they see, so give them the right thing to copy.

• Tie each macro to a trigger: which issue, which queue, when to use it.
• Teach them to edit, not paste. A macro is a skeleton; the order number and the customer's actual problem make it human.
• Audit the macros quarterly. Stale macros teach new agents to send outdated information with confidence.

When to escalate: give them the tiers

The biggest source of new-agent anxiety is not knowing when to stop and ask. Give them tiers, not judgment. A clear escalation matrix turns 'should I handle this myself?' from a guess into a lookup. A workable model for DTC support:

• Tier 1, the agent handles it: order status, standard returns, simple policy questions, refunds up to your set limit. Give new agents real authority here; a refund cap they can use without asking is what makes them fast.
• Tier 2, loop in a senior agent or manager: repeated complaints, carrier claims, partial refunds, anything outside policy.
• Tier 3, escalate to the Head of CX or Ops: fraud, chargeback threats, legal language, VIP customers, public social escalations.

Document the triggers, not the rare cases. You cannot list every odd ticket, but you can group them by risk. A new agent who knows the three tiers handles the vast majority of edge cases correctly in week one.

The signals a new agent is ramped

Ready is a number, not a feeling. By day 30 a new agent on standard tickets should be hitting the same targets as the team, or close to it. Track:

• First-response time: are they replying within your SLA? It comes up to speed first and is the easiest to measure.
• Tickets per day: ramping toward the team baseline. 20 to 30 a day on standard issues by week four is a reasonable bar.
• CSAT: on their resolved tickets, tracking near the team average. A new agent dragging CSAT down points to tone or accuracy, both fixable with feedback.
• QA score: a sample of their tickets reviewed against your rubric. This catches the quiet problems CSAT misses, like a correct answer delivered in the wrong tone.

Review these weekly during the ramp. An agent who is fast but tanking CSAT needs different coaching than one who is accurate but slow. The numbers tell you which.

Keep the onboarding SOP from going stale

Support onboarding SOPs rot fast because support changes fast. You switch helpdesks, you add a subscription product, you change the refund policy, and the onboarding doc still trains new hires on last quarter's process. A new agent who learns from a stale SOP is confidently wrong from day one.

Review the onboarding SOP every quarter, and immediately after any change to your helpdesk, policies, or product line. This is the same drift that quietly breaks every operational doc, and onboarding is where it does the most damage, because it teaches the error to every new person.

Where to start this week

Don't build the whole program at once. Do one thing: write the day-one access checklist and the reading list of the 5 to 8 SOPs that cover most tickets. That alone turns a wasted first morning into a productive one, for every future hire.

Then write the 30-day definition of ready. A new agent and their manager knowing exactly what ramped means is worth more than any training course, because it makes every other week of onboarding measurable.

ReccordSOP turns the procedures a new agent needs to learn into documented SOPs with timestamped screenshots, and flags drift when your tools or policies change underneath them. Generate your first SOP free at reccordsop.com.