What it is
The Chat Agent Onboarding Checklist is a structured ramp plan that takes a new live-chat agent from access-provisioned to a fully certified, multi-chat-handling team member. It standardizes onboarding so nothing — from tooling access to compliance sign-off — gets missed before an agent owns live conversations alone. The plan is organized as a timeline: pre-start (before day one), Week 1 foundations and tooling, Week 2 skills and simulation, and Weeks 3-4 nesting on supported live chats. The defining principle is that concurrency is built deliberately, not assumed: a new agent starts at a limit of one chat so they aren't overwhelmed, then ramps toward two and three as quality holds.
Each phase carries concrete actions. Pre-start provisions SSO, the chat console, and CRM/help-desk access with the correct role and skill tags, grants the macro library and knowledge base, and sends compliance acknowledgements. Week 1 covers product, policy, and brand voice — walking the Greeting & Tone Guide and macro library — plus hands-on console work and compliance training on identity verification, consent, data handling, and PII redaction. Week 2 is role-play and shadowing against the QA scorecard as the rubric. Weeks 3-4 are nesting: live chats with a coach nearby, daily QA, and a gradual ramp toward team handle time, FCR, and CSAT, certifying on each chat type before folding into the main queue.
The checklist includes a systems-and-access setup list (chat console login tested with a sandbox chat, CRM access and disposition sync verified, macro and knowledge-base access, skill tags and routing, concurrency set for the ramp stage, schedule published in the WFM tool) and a 30-60-90 ramp-targets table. By Day 30 the agent handles up to 2 concurrent chats at an 80+ QA score with zero compliance misses; by Day 60, 2-3 concurrent at 85+; by Day 90, team-standard concurrency (3-4) at 90+ with CSAT and FCR at or above team average. Manager sign-off questions close the loop before the agent runs solo.
What it's used for
An onboarding checklist exists to make agent ramp repeatable and safe, so quality and compliance don't depend on whoever happened to train the new hire. Teams use it to:
- ✓ Provision everything before day one — SSO, chat console, CRM with the right role and skill tags, macro library, and compliance acknowledgements — so the agent starts ready, not waiting.
- ✓ Ramp concurrency deliberately, starting at one chat and raising the limit only as quality holds, since ramping concurrency too fast tanks CSAT across every simultaneous conversation.
- ✓ Train the foundations in a fixed order: product and brand voice, the Greeting & Tone Guide and macro library, the chat console mechanics, and compliance on verification, consent, and PII handling.
- ✓ Build skills through role-play and side-by-side shadowing, using the QA scorecard as the rubric so practice is measured against the real standard.
- ✓ Nest new agents on supported live chats with a coach nearby and daily QA, ramping targets toward team handle time, FCR, and CSAT against a defined curve.
- ✓ Track progress against a 30-60-90 table with explicit concurrency, QA-score, and CSAT milestones at each checkpoint.
- ✓ Gate solo work behind manager sign-off questions covering compliance certification, concurrency-at-quality, trend toward targets, and knowing when to escalate.
Who uses it
Onboarding is a shared responsibility across the people who provision, train, certify, and eventually manage the new agent:
Context & good to know
Concurrency is the lever unique to chat onboarding, and it's the one that ramps most easily wrong. Unlike phone, where an agent handles one call at a time, a chat agent eventually runs three or four conversations simultaneously — and pushing a newcomer there too fast tanks CSAT across every chat at once, because their attention is split before they've built the muscle memory. The checklist therefore starts every agent at one chat and raises the limit deliberately as quality holds, treating concurrency as something earned milestone by milestone rather than granted on day one.
Compliance can't be an afterthought folded in later, which is why it's woven through the timeline and gated at sign-off. Chat agents handle identity verification, consent, data handling, and PII redaction in real time, often while juggling multiple conversations, so the Week 1 compliance training and the explicit manager sign-off question ('Has the agent passed compliance certification?') exist to ensure no agent owns live chats before they can handle data correctly. The QA scorecard reinforces this with its compliance auto-fail, so the standard the agent trains toward already treats a breach as disqualifying.
The checklist deliberately ties onboarding to the rest of the chat operation rather than treating it as a standalone HR task. Trainees walk the Greeting & Tone Guide and the macro library so they inherit the team's voice and approved language; they practice against the QA scorecard so they learn the exact rubric they'll be measured by; and they ramp toward the same handle-time, FCR, and CSAT targets the team already runs. This alignment is what makes a newly certified agent indistinguishable from a tenured one in the queue.
The 30-60-90 framework turns ramp from a vague feeling into a measurable curve. Each cohort's days-to-target-concurrency can be tracked alongside QA-at-day-30, so the program itself can be tuned — ramping too fast tanks quality, ramping too slow wastes capacity, and the goal is full concurrency without a CSAT dip. Tools like Intercom, LiveChat, and Olark all let admins set per-agent concurrency caps and skill-based routing, which is what makes a deliberate, staged ramp practical to enforce rather than just aspirational.