How does onboarding work?
- Set up access before day one: named accounts at the permission level the role needs, nothing shared.
- Give context before tasks: what the business does, who the customers are, what a good day looks like.
- Start with two or three tasks under supervision, writing the procedure while learning them.
- Agree a ramp that names which tasks move across in week two, week four and week eight.
- Check in daily for the first fortnight, because the habits formed now are the ones that stick.
A worked example
An HVAC contractor in Nevada brought a scheduling assistant up over four weeks. Week one: dispatch software access, listening to recorded calls, learning the service area and the pricing rules. Week two: booking maintenance visits with every booking checked. Week three: same-day dispatch decisions with a rule for when to call the owner. Week four: running the board alone, with the procedure she had written pinned beside it. The owner's phone stopped ringing at 7am.
Where does onboarding show up in your tools?
Access usually starts in Google Workspace or Microsoft 365 admin and then reaches the tools that matter: the CRM in HubSpot, the help desk in Zendesk, the phone system in RingCentral or Dialpad. The plan itself, with weekly milestones, tends to live in Notion or as a template project in Asana or ClickUp.
Common mistakes
- Waiting until day one to request logins, which burns the first week on access rather than work.
- Handing over twelve tasks at once, so nothing is learned properly and most of it needs redoing.
- Skipping the business context, which leaves a capable assistant unable to judge what is urgent.
Why does onboarding matter?
Nearly every assistant engagement that fails did so in the first month, usually because access came late, context never came at all and too much work arrived at once. A written ramp fixes all three and gives both sides something to measure against. It is also when your procedures get written, which is the asset you keep.
How does AssistBPO handle onboarding?
AssistBPO onboarding starts the moment you approve a named assistant. We collect your tools, scripts and access requirements, set the assistant up under your own accounts at the permissions you choose, and agree in writing which tasks move across in which week. The team lead sits in for the first two weeks, and the trained backup shadows the same material so they are ready long before they are needed.