Take the free IT Readiness Test and see where you stand, 10 quick questions.
A Microsoft Teams call queue is an automated routing system that directs incoming calls to a group of agents based on rules you define. Instead of calls ringing everyone at once or being missed entirely, a queue manages the flow, plays hold music, estimated wait times, and even redirects calls if no one picks up within a set timeframe.
For UK organisations running customer-facing teams, it's a game-changer. You avoid dropped calls, reduce time spent managing ad-hoc routing, and give callers a professional experience rather than chaos. If you're using Teams for business already (and most UK companies are), call queues are built in. You don't need expensive third-party PBX systems.
The catch? Setup requires the right admin permissions, a clear understanding of your organisation's calling architecture, and attention to a few easy-to-miss configuration steps.
Before you touch call queues, confirm three things:
Licensing: Users who'll answer calls from the queue need a Microsoft 365 business licence that includes calling (Teams Phone). This includes Business Standard, Business Premium, or Enterprise licences (E1 and above). If you're unsure what your team has, ask your IT administrator or check the Microsoft 365 admin centre under Licenses.
Admin Access: You'll need to be a Teams admin or Global admin in your Microsoft 365 tenant to create call queues. If you're a regular user trying to set this up, you won't see the options.
Resource Account: Call queues require a dedicated "resource account" (a no-cost tenant account with no licence) to act as the routing hub. Think of it as the virtual receptionist. You'll create this before building the queue itself.
If your organisation doesn't currently have Teams Phone enabled, that's the actual first step. It's separate from Teams chat and requires a Teams Phone licence. If you're unsure whether you need this or how to budget for it, a free consultation with your IT partner will clarify the licensing cost for your team size.
Log into the Microsoft 365 admin centre (admin.microsoft.com) with your Global or Teams admin account.
1. Go to Users > Active users.
2. Click Add a user and fill in the details as you would for any employee.
3. For the username, use something descriptive like "queue-reception" or "queue-sales".
4. Assign a password (you won't log in with this account, so make it complex and store it securely).
5. Leave the licence blank (resource accounts don't need one).
6. Click Create.
Once created, the resource account exists but won't do anything yet. It's inert until you assign it to a call queue and give it a phone number.
Go to the Teams admin centre (teams.microsoft.com/admin).
1. Navigate to Voice > Phone numbers.
2. Click Add and select a new number (or port an existing one if you're moving an old business line).
3. Assign that number to your resource account.
4. Confirm the assignment.
This number is what callers will dial. Internally, Teams associates the queue with this number.
Still in the Teams admin centre:
1. Go to Voice > Call queues.
2. Click Add to create a new queue.
3. Name it something clear (e.g. "Support Queue" or "Sales Queue").
4. Select your resource account from the dropdown (this is the hub the queue routes through).
5. Set the language (English UK is the default; select it).
At this point you're defining the queue itself. Don't save yet; there are more steps below.
Call Answering Agents: Add the users who should receive calls from this queue.
1. Under Add agents, add team members one by one or paste a distribution group if you have one.
2. Set a routing method: "Round robin" spreads calls evenly; "Longest idle" sends the next call to whoever's been free longest; "Serial" rings agents in order.
3. For most UK teams, round robin is best because it's fair and spreads load evenly.
Conference Mode: Tick the box for "Conference mode". This means the resource account joins the call behind the scenes, ensuring better call quality and recording compliance.
Call Overflow Handling: Set a maximum queue size (e.g. 50 calls) and decide what happens when it's full (redirect to voicemail, disconnect, or transfer to another number).
Call Timeout: Set how long a call rings before moving to the next agent (typically 30 to 45 seconds for UK customer service teams).
This is where your queue sounds professional:
Hold Music: Choose from Teams' built-in options (classical, jazz, etc.) or upload a custom audio file. Most UK organisations use a simple hold tone with periodic updates.
Hold Announcements: Enable periodic messages to inform callers of their queue position and estimated wait time. This dramatically reduces abandoned calls.
Voicemail: If calls timeout or queue is full, direct them to a shared voicemail box or a specific person.
Save these settings.
Create a test group of three or four colleagues. Have them answer calls from the queue for a morning. Call the queue number from a mobile and confirm:
Document any issues and adjust routing or timeout settings if needed.
Not enabling Teams Phone licensing: If your team doesn't have the calling licence, the queue will exist but calls won't work.
Assigning regular users as the resource account: Resource accounts must be created as resource accounts, not repurposed user accounts. A regular user account will cause licensing conflicts.
Timeouts set too short: 15-second timeouts frustrate agents and callers. Aim for 30 to 45 seconds in most cases.
Ignoring call analytics: Once the queue is live, check the Teams admin centre weekly for call volume, average wait time, and abandonment rates. This data tells you if you need more agents or better routing.
If you're building call queues now or thinking about moving into Microsoft 365 administration formally, the Microsoft 365 Administrator Course covers this exact skill in depth, including Teams calling, resource accounts, and call centre automation. The course is currently on a waitlist (demand is high), but you can join the list here. Even better: if you're early in your IT career and unsure whether administration is the right fit, grab a free AI career pathway assessment to see how Teams admin skills fit into your broader IT journey.
Yes. Set up the queue with a small test group and use an internal number to test it before publishing the number externally. Once you're confident it works, add it to your contact directory or post it on your website.
The call enters the queue and waits. If the timeout is set to 45 seconds and no one becomes available, it routes to voicemail or redirects to another number, depending on your overflow settings.
Absolutely. Each queue needs its own resource account and phone number. You can have a sales queue, support queue, HR queue, and so on, all routing independently within the same Teams tenant.
Not much. They need to know how to use Teams, accept calls, put callers on hold, and transfer calls. Most teams pick it up within a day or two, especially if you run a short walkthrough session first.
Yes, if you enable call recording in your queue settings. Recordings are stored in Microsoft Stream and comply with UK GDPR requirements, though you should inform callers that calls may be recorded.
SmoothOps 365 runs live instructor-led training every Saturday and Sunday. 3 months. 50 contact hours. Keep your job while you train.