A first-week checklist for new joiners in BPO, KPO and contact centres

On Thursday a trainee on a billing-support process sits with a crackling headset, a CRM login that expired overnight and a shuttle that left her at the gate at one in the morning. Nobody has played her a model call. By Friday she has gone silent on the batch group, and the trainer has not noticed.

Build the week around three questions. Can she log in and use the tools? Does she know what the floor expects of her and when? Does she know whom to ask? Everything on the checklist answers one of these.

BEFORE DAY 1   system IDs raised, headset tested, cab or shuttle stop confirmed, seat and locker allotted
DAY 1          welcome by the trainer and team leader, facilities tour, break rooms, cafeteria timings, safety exits
DAY 1          shift roster, weekly off, break pattern and the rule for swapping a shift
DAY 2          process overview: who the customer is, what the product does, what a call or ticket looks like
DAY 2          tool login test: CRM, dialler or ticketing screen, knowledge base, chat window
DAY 3          call listening or sample ticket review, with the QA scorecard explained line by line
DAY 3          adherence, AHT and quality in plain words, with what the process targets mean
DAY 4          mock calls or mock tickets with the trainer, with feedback written down
DAY 4          escalation path: who to call when the customer asks for a supervisor, when the system fails, when a call turns abusive
DAY 5          first product knowledge test, review and the nesting plan for the next two weeks
DAY 5          conversation with the team leader: what felt hard, what felt unclear, what is needed

• System IDs before day one: a trainee without a working ID spends day one at the IT desk and forms an opinion of the firm.
• Cab and shift details: for night and rotational shifts, the ride home decides whether the person returns on Monday.
• QA scorecard explained: calls are scored on greeting, probing, accuracy and closing. If this is never explained, the first review feels like an ambush.
• Escalation path: a shouting caller on call three, with no idea whom to raise a hand to, is how walk-outs begin.
• Nesting plan: a planned step from the training room to live queues, with a team leader a desk away, ends the feeling of being dropped into the deep end.

Joiners hear a stream of terms in week one. AHT is the average time a call takes, from greeting to wrap-up. After-call work is the typing and tagging that follow. Adherence is how closely she keeps to her logged-in time, breaks and meetings. Shrinkage is the time the roster loses to leave, training and coaching. Dead air is silence on a call. A disposition code is the tag that says how the call ended. Barging and whisper are what a team leader does when listening in. Print them on a pocket card for day two and walk through one call from greeting to tagging.

1. 1

   Trainer

   Runs the classroom days, owns the mock calls and records feedback in a shared sheet.

2. 2

   Team leader

   Meets the batch on day one and on day five, sits with each person during nesting and checks adherence daily.

3. 3

   Workforce management

   Confirms the roster, break pattern and weekly offs, and answers shift swap questions in writing.

4. 4

   IT desk

   Delivers working IDs, headset and tool access before day one and fixes problems on the spot.

5. 5

   HR or admin

   Collects joining papers, explains the pay date and leave rules, and phones each joiner on Saturday.

A customer support centre needs calm handling of angry callers early. Add a day-three session on tone, apology scripts and hold etiquette.

A telecalling company and a sales call centre depend on scripts, objection handling and disposition codes. Add dialler practice and a listen-in on day two.

A technical support desk needs a troubleshooting tree, remote tool access and ticket notes. A data processing or finance outsourcing unit needs accuracy drills, a style guide, a document handling and confidentiality briefing and a first sample batch with error checks.

Tally three counts per batch: joiners with a working login by ten on day one, joiners present all five days, and joiners who wrote a question on the Friday sheet. If attendance slips, look first at the shuttle, then at the roster, then at the classroom. The employee onboarding process page covers a longer plan, and the BPO, KPO and contact centres hub lists related problems.

Weeks two to four still need eyes on them. Book two short sit-downs, around day fifteen and day thirty, with the team leader and trainer in the room. The attendance, shift and leave page offers a rule set for swaps and offs.