Teamabout 20 min

    How do I onboard a new team member into the system?

    Short answer

    Run the same sequence every time: create the login with the right role, connect their calendar and phone routing, walk them through the three screens they will actually use, and check their work at the end of week one.

    Before you start

    • Defined roles and permissions.
    • A written onboarding checklist.
    • The screens each role uses daily.
    • Someone assigned to check week one.

    Step by step

    1. 1

      Create the login before day one

      Correct role, calendar connected, notifications configured, ready to use.

      Day one spent waiting on access sets the tone badly.

    2. 2

      Teach three screens, not thirty

      Their schedule, the customer record, and the inbox. Everything else comes later.

      Full-system tours produce zero retention.

    3. 3

      Use a real job as the lesson

      Walk a live customer from booking to completion together.

      Context makes the training stick.

    4. 4

      Set the response expectations

      How fast to reply, when to escalate, and what never to promise.

      Standards you did not state are standards nobody meets.

    5. 5

      Check the work in week one

      Review their notes, messages, and task completion, then correct early.

      Bad habits set in the first fortnight last for years.

    6. 6

      Reuse the checklist

      Improve it after each hire instead of improvising again.

      Repeatable onboarding is what makes hiring less painful.

    What good looks like

    • New hires are productive in days.
    • Access is correct from day one.
    • Standards are explicit, not assumed.
    • Onboarding gets better every time.

    Common mistakes

    The ways this goes wrong in team, and what to do instead.

    Training on everything at once

    The new person remembers none of it and guesses for a month.

    Do this instead: Teach the three daily screens first and layer in the rest over weeks.

    No first-week review

    Small mistakes become entrenched habits.

    Do this instead: Schedule a week-one review of notes, messages, and tasks.

    Copying another user's permissions

    The new hire inherits access they should not have.

    Do this instead: Assign a defined role rather than duplicating an existing account.

    Frequently asked

    5 questions about onboard a new team member

    Basic competence in a few days for field roles, a couple of weeks for office roles handling customers end to end.

    Pick the next thing to set up, or back up a step if something here assumed work you have not done yet.

    Was this guide helpful?

    Tell us what worked and what didn't. It shapes what we rewrite next.

    You didn't get into business to be in the tech business.

    Managed Tech clients hand this to us. We build it, test it, maintain it, and add to it as the business changes, so nobody on your team has to become the person who knows how the system works.

    Schedule a fit callCallCalls are answered by Troy, our AI assistant. Troy answers questions about the system and services and can schedule, reschedule, or cancel appointments. He never sells or makes offers. Any communication with TactStack is stored in our systems and referenced by Troy during certain interactions. AI can make mistakes.Full documentation