Adding a new agent to a 24/7 support roster is not the same as adding a new employee to a regular 9-to-5 team — and the mistakes made during onboarding show up fast, usually in the form of coverage gaps, missed handovers, or an agent who logs in on day one and has no idea what they’re supposed to do.
When your operation runs around the clock, every agent is a load-bearing piece of the schedule. Getting them fully set up before their first shift — not during it — is the difference between a smooth addition and a week of scrambling.
This guide walks through every step of onboarding a new agent onto a 24/7 schedule using Manage Roster as the example. The same logic applies regardless of what tool you use — but the steps are specific enough to follow directly.
A lot of teams treat onboarding as: “I told them their shift, they have Slack access, they’re good.”
They’re not good. For a 24/7 support agent to be fully operational, they need:
Miss any of these and you’ll find out about it at the worst possible moment — mid-shift, when they’re asking questions that should have been answered on day one.
The first thing to do is create the agent’s profile in your scheduling tool. In Manage Roster, this is done under Agents → Add Agent.
The fields that matter most at this stage:
Full name and display name. The name that will appear on the schedule grid and in reports. Use whatever name the agent goes by — not their legal name if they go by a nickname.
Contact information. Phone number and email. These are used for shift notifications and emergency contact. Make sure these are verified with the agent directly — don’t assume HR’s records are current.
Location / timezone. This is critical. A scheduling tool uses timezone to display shift times correctly for both the manager and the agent. If Maria is in Manila and you’re based in London, her 22:00–06:00 UTC shift needs to show as 06:00–14:00 on her end. Get this wrong and agents show up an hour late on their first day.
Role or tier. If your team has agent tiers (L1, L2, L3) or specializations (billing, technical, onboarding), tag the agent correctly now. This affects which shifts they’re eligible for and which OT events they appear in.
Notes field. Use this for anything that doesn’t fit a standard field — “primary language Tagalog, secondary English,” “authorized for L2 escalations from day 30,” “part-time, max 4 shifts per week.” You’ll thank yourself later.
Working hours tell the system when this agent is available to be scheduled. Without this, the system treats them as available 24/7, which will create scheduling errors.
Working hours have two components:
Days of the week. Which days is this agent contracted to work? Most 24/7 agents work 4–5 days per week with 2–3 days off. Be specific. If their days off rotate (common in 24/7 operations), set a rotation pattern rather than fixed days.
Shift window. What hours within a working day are they available? For a fixed-shift agent, this might be 22:00–06:00 UTC every night they work. For a flexible agent, it might be a wider window within which shifts can be assigned.
In Manage Roster, working hours are set per agent in their profile. The system uses this to:
A common mistake: Setting working hours as a flat “40 hours per week” without specifying which days or what time window. This gives the system no useful information and defaults to treating the agent as fully available. Be specific about days and times.
If you’re running a global team, every agent needs to be assigned to the holiday group that matches their country. This determines which public holidays they observe — and therefore which days need coverage from other agents.
For a Philippines-based agent joining your team:
From that moment on, every Philippine public holiday is reflected in their schedule. When you publish a schedule that includes Rizal Day or Independence Day, the system already knows this agent is off — and flags any resulting coverage gap before you publish.
If you don’t have holiday groups set up yet, this is the moment to do it. Onboarding a new agent is a natural forcing function to get your holiday infrastructure right. The guide How to Handle Public Holidays for a Global Support Team covers the full setup process.
The agent profile is the manager-side record. The user account is what the agent themselves logs in with.
These are two separate things in most scheduling tools, and skipping the user account is a common oversight. You end up with an agent who’s on the schedule but has no way to see their shifts except by asking you.
In Manage Roster:
Once they have an account, they can:
This matters for 24/7 operations specifically because agents often need to check their schedule at odd hours — midnight before a shift, weekend morning before a rotation change. Having their own login means they’re not dependent on you being available to answer “what time do I start tomorrow?”
Set their account permissions carefully. A new agent should see their own schedule and the team schedule for their region. They probably shouldn’t have access to edit other agents’ profiles or modify the master schedule. Configure read-only access for the first month and expand as they settle in.
The agent profile is complete. Now you actually put them on the schedule — and this is where you need to have a direct conversation, not just a Slack message with their shift times.
For a 24/7 team, the shift handover is the most important operational ritual. Every time one agent logs off and another logs on, context needs to transfer. What’s open, what’s urgent, what the customer was told, what’s waiting on engineering. If this information doesn’t pass cleanly, issues fall through the cracks.
Walk your new agent through:
What a handover note looks like. Show them a real example from a recent shift. Point out what information it includes and why. An APAC → EMEA handover note might look like:
HANDOVER: [Name] → [Incoming Agent]
Date: [DATE] | Shift: 22:00–06:00 UTC
OPEN TICKETS:
- #4421: Billing dispute, customer awaiting refund. Escalated to finance 3h ago. Follow up at 02:00 UTC if no response.
- #4438: Technical issue, logs submitted to engineering. No ETA yet. Chase at 04:00 UTC.
WAITING ON CUSTOMER:
- #4409: Asked for screen recording 2h ago. Chase if no reply by 00:30 UTC.
HEADS UP:
- Volume spike expected around 01:00 UTC — marketing email going out to US customers at 20:00 EST.
STATUS: Handover complete. Incoming agent briefed.Where handover notes are stored. Whether it’s a dedicated Slack channel, a shared doc, or a field in your ticketing system — they need to know where to find the outgoing team’s notes and where to post their own.
What to do at the start of their shift. Read the handover note. Acknowledge any open escalations. Check the ticket queue. Don’t start fresh — pick up where the last agent left off.
What to do at the end of their shift. Write the handover note at least 15 minutes before shift end (not after). Include everything the incoming agent needs to know. Don’t go quiet — the incoming agent should receive the note before they start.
This process sounds simple, but new agents consistently underestimate its importance. The handover is the backbone of 24/7 quality. Treat it accordingly.
If your team uses regular work reports — weekly or monthly summaries of hours worked, OT logged, shifts completed — your new agent needs to be included from their first week.
Leaving someone out of work reports is a common oversight that creates problems later: you can’t account for their hours, OT isn’t tracked properly, and when you need to audit coverage for a period they worked, they’re invisible.
In Manage Roster, work reports are template-based. You define which agents are included in each report, and the system generates the report from actual schedule data. To add your new agent:
Do this on day one, not a month later when you realize their hours aren’t showing up.
Also check: Are they included in your weekly schedule summary emails? Your team communication channels? Any shift-notification automations? New agents have a way of existing in your scheduling system but not being connected to the communication flows that experienced agents take for granted.
A well-onboarded agent logs in on their first shift and immediately knows where they are and what to do. Here’s what that looks like in practice:
They log into their Manage Roster account. They can see the schedule for their region — who’s on now, who they’re handing off to, when their next shift is.
They can see their upcoming shifts. Not just today’s — the next two weeks. They know when they’re working, when they’re off, and when any OT events have been published that they might want to pick up.
They receive their shift reminder. Manage Roster sends automated shift reminders before shifts start. If this is configured, they get a notification before their first shift — a simple “Your shift starts in 1 hour” that serves as a failsafe.
They have the handover note from the outgoing agent. If the incoming shift reads the handover note before starting, context is transferred. No surprises.
They know who to contact for questions. Before day one, give them: their regional team lead’s contact, the escalation path for P1 issues, and the channel where shift-related questions go (not the same channel as customer issues).
The test of a good onboarding: Can the agent get through their first full shift without asking “where do I find X” or “what should I do about Y”? If yes, you did it right.
Use this as your standard process for every new agent:
Before their first shift:
On or before day one:
After their first week:
The pattern that breaks onboarding is doing these steps during or after the first shift. The agent is trying to learn the product, handle real tickets, and figure out the handover protocol — they cannot also be chasing you for login credentials and asking why they’re not in the work report.
Do the setup work before their start date. In Manage Roster, the full onboarding setup — profile, working hours, holiday group, user account — takes about 10 minutes per agent. The checklist above takes another 10 minutes to work through. Twenty minutes of prep prevents hours of confusion.
Manage Roster is free for teams up to 10 agents — with agent profiles, holiday groups, user accounts, work report templates, and shift notifications built in.
Use code BETA2026 for 20% off your first 3 months on any paid plan.
👉 Get started free at app.manageroster.com
Related guides: