To onboard a support agent in 30 days, split the month into four phases. Days 1 to 3: tools, product and the ten most common questions. Days 4 to 10: shadowing and answering simple tickets with a buddy who reviews every reply. Days 11 to 20: practicing the hard conversations and taking a first ticket type solo. Days 21 to 30: working independently on every ticket type the agent has passed, with a review at the end.
The plan fits a support team of 3 to 30 people answering email, chat or phone. It works for a SaaS company, an online store, an agency with client accounts, a call center or BPO onboarding a new client, a booking desk at a salon, clinic or fitness studio, the dispatch desk of a cleaning or plumbing company, and the front desk at a hotel or care provider. Swap the topics. Keep the rhythm.
Before day one: what to have ready
The first morning goes well when the work happens the week before:
- Accounts for the helpdesk, phone or chat tool, order or booking system, knowledge base and training tool. Test the logins.
- A buddy, an experienced agent with time blocked to answer questions and review replies.
- The first training assigned with a due date, so the agent can start on day one.
- A written list of the ten most common questions, each linked to an article.
- A calendar for week one that mixes learning time, shadowing and short check-ins.
Days 1 to 3: tools, product and the top ten questions
Goal: the agent can find their way in every tool and knows the answers to the questions that make up most of your volume.
| Day | Focus | Activity |
|---|---|---|
| 1 | Welcome and tools | Meet the team and buddy, log into every tool, follow one ticket from start to finish |
| 2 | Product or service | Short lessons, then use the product as a customer would: place an order, book an appointment, change a setting |
| 3 | Top ten questions | Read the articles, take a short quiz per topic, write three practice replies for the buddy to review |
End of day 3: a quiz across the ten topics. Repeat any lesson where the score is low.
Days 4 to 10: shadowing and simple tickets
Goal: the agent answers low-risk tickets with a buddy reviewing before anything is sent.
- Pick two or three low-risk ticket types: order status, password reset, rescheduling, a question about opening hours.
- The agent drafts every reply. The buddy reviews it and gives one specific tip per reply.
- On the phone: listen in first, then take calls with the buddy next to them.
- Read the procedures for refunds, complaints and escalations, and confirm them.
Review rule: start by reviewing every reply. Switch to a daily sample once the buddy has a full day with no changes.
Days 11 to 20: hard conversations and the first solo ticket type
Goal: the agent handles a complaint, a refund request and an upset customer the way your procedure says, and takes the first ticket type alone.
This phase is where practice pays off most. Pick three situations that are common and costly in your business and let the agent rehearse them before they happen live. Some examples by type of business:
- Online store: a customer wants to return an item after the return window.
- SaaS: a customer can't log in the day before an important deadline.
- Agency: a client is unhappy that a deliverable is late.
- Booking business: a regular client shows up 20 minutes late and still wants the full appointment.
- Field services: a technician missed the morning slot and the customer took time off work.
- Call center or BPO: a caller demands to speak to a manager on the second sentence.
Example practice conversation: return after the window
Customer: I bought this jacket five weeks ago and the zipper is already broken. Your site says 30 days for returns. That's not fair.
Agent: A broken zipper after five weeks shouldn't happen, I get why you're annoyed. Let me check what I can do. Do you have your order number?
Customer: 77104.
Agent: Thanks. The return window has passed, but a broken zipper counts as a defect, and defects are covered for a year. I can send you a prepaid label today. Once the jacket arrives, we replace it or refund you, whichever you prefer.
Customer: Replace it, same size.
Agent: Done. The label is in your inbox within the hour. The new jacket ships the day yours arrives, and you'll get a tracking email.
Score it on three points: acknowledging the problem, applying the right procedure (the defect policy, since the return window has passed), and a clear next step with timing. Have the agent run each scenario at least twice. The second attempt is where most of the learning shows.
At the end of this phase, the agent works the ticket types from days 4 to 10 solo, plus one new type.
Days 21 to 30: working independently
Goal: the agent works on their own for every ticket type they've passed and knows who to ask for the rest.
- Drop full review. Keep a sample of a few tickets a day.
- Add one ticket type at a time, each after its quiz and practice conversation.
- Close the month with a 30-minute review: what's going well, what's still hard, which answers were missing or unclear in the knowledge base.
That last question is worth a lot. New agents see the gaps your experienced people have stopped noticing. Write those answers down, and the next hire starts with a better knowledge base.
How do you know a new agent is ready for a ticket type?
Agree on the bar before the agent starts, and use the same one for everyone:
| Check | Bar |
|---|---|
| Quiz on the topic | Passed, for example 80% correct |
| Procedure for the topic | Read and confirmed, latest version |
| Practice conversation | Passed at the score you set in advance |
| Real replies | A handful reviewed, with only small fixes needed |
If you handle several kinds of tickets, such as billing, technical issues and complaints, build a short training per kind. You'll see at a glance which agent is ready for which queue.
Onboarding checklist for support agents
- Accounts, buddy and week-one calendar ready before day one
- First training assigned with a due date
- Top ten questions written as articles, with a quiz
- Refund, complaint and escalation procedures read and confirmed
- Three practice conversations, each done at least twice
- A readiness bar per ticket type, agreed in advance
- Review reduced from every reply to a daily sample
- 30-day review, with a list of missing articles
For a general version you can adapt, see the employee onboarding checklist template.
How Helpable runs this onboarding plan for you
With Helpable you set up this plan once. Every new agent gets the same good start, and you see in one place how each person is doing.
- An onboarding program in a set order. Lessons, quizzes, procedures and practice conversations per phase, with due dates and reminders when something stalls. On Business Plus and up, a new agent is enrolled automatically when you add them to the team. See employee onboarding software.
- Answers with the source. A new agent asks "how do I refund a damaged item?" in plain words and gets a short answer from your own procedure, with a link to it. The buddy gets interrupted less.
- Read confirmations. You see who has read the refund and complaint procedures and who still has to confirm the latest version. See read and acknowledge.
- AI roleplay for days 11 to 20. Build the practice conversations from this plan as scenarios: who the customer is, how they behave, the goal and the scoring points. New agents practice by typing or out loud, whenever it suits them, and get a score with a quote for each point right away. The AI takes its facts from the procedures you attach, and a manager can review any conversation. Included in Business Plus and Business Max. See AI roleplay.
- Results per person. Quiz scores, confirmed procedures and roleplay results per agent in one view, so you know who is ready for which queue.
Helpable is training software for teams of 5 to 50 people. Business Plus costs $89 a month for 5 team members, plus $8 for each extra person, so a support team of 8 comes to $113 a month. Smaller teams start on Business at $29. Try it free for 14 days, no credit card needed. See pricing, or how online stores and SaaS teams use it.
FAQ
How long does it take to onboard a support agent?
Plan for about 30 days before an agent handles most common tickets alone. Complex products take longer for technical questions; give those their own training after the first month.
What should a support agent learn in the first week?
The tools, the product and the answers to your ten most common questions, followed by shadowing and simple tickets with a buddy reviewing every reply.
When can a new agent handle tickets on their own?
Once they've passed the quiz and practice conversation for that ticket type and a buddy has reviewed a handful of real replies with only small fixes. Keep a daily sample after that.
Should new support agents practice with roleplay?
Yes. A complaint or a refund request is stressful the first time it happens live. Two or three practice rounds give agents the steps and the words before a real customer is waiting.
How do you onboard support agents at a BPO or outsourcing partner?
Use the same plan and the same source of answers as your own team. Shorter stays make a fixed program even more useful. Give external agents access only to the knowledge they need.
What's the difference between onboarding and training support agents?
Onboarding is the first month: tools, basics and getting to solo work. Training continues after that, with refreshers when policies change and practice on the topics that cause the most trouble. More in our customer service training guide.
Set up your 30-day plan once and use it for every new hire. Start your free trial.
