A customer calls your main business number at 4:55 p.m. They need billing, not sales. The right answer is not simply whether can Teams route external calls. It can. The real question is whether your setup can recognize the call, apply the right business rules, and get the caller to someone who can help without manual transfers or missed calls.
For many small and midsize businesses, Microsoft Teams is already where employees chat and meet. Adding business calling is a practical next step, but external call routing requires more than assigning users a Teams license. You need a connection to the public phone network, a plan for inbound call handling, and call-flow tools that match how your organization actually operates.
Can Teams Route External Calls?
Yes. Teams can make and receive calls to regular phone numbers when it is configured for Public Switched Telephone Network, or PSTN, calling. Once your business numbers are connected, Teams can route incoming calls through features such as auto attendants, call queues, forwarding rules, and user settings.
For example, an inbound call can reach an auto attendant that plays a greeting: “Press 1 for sales, 2 for support, or 3 for accounts.” Each option can send callers to a Teams user, a call queue, a voicemail box, an external number, or another menu. A queue can distribute support calls among available agents rather than sending every caller to one receptionist.
That is the basic capability. The limits appear when call routing needs to reflect opening hours, holiday schedules, skills, language selection, overflow policies, on-call rotations, or multiple sites. Native Teams features may be sufficient for a straightforward setup. Organizations with more detailed requirements often connect Teams to a PBX platform that provides greater control over the complete call flow.
First, Define What “External Calls” Means
The term can mean two different things in a Teams conversation. The distinction matters because the configuration is different.
An external Teams user is someone outside your Microsoft 365 organization who calls or chats through Teams federation or is invited as a guest. This is collaboration traffic. It does not use a business telephone number and does not require a PSTN calling setup.
An external phone call is a call between Teams and a standard landline or mobile number. A customer dialing your published number, an employee calling a supplier’s cell phone, or a forwarded after-hours call all fall into this category. These calls require PSTN connectivity.
If the goal is to receive customer calls on Teams, route them to departments, and maintain a professional main number, focus on PSTN calling and PBX call flows – not just Teams external access settings.
What Teams Needs Before It Can Handle Business Calls
Teams does not become a full telephone system merely because users have the Teams app. Your organization needs Teams Phone licensing for the people or shared services that will use telephony features, plus a way to connect phone numbers to the PSTN.
There are three common connectivity models. Microsoft Calling Plans provide calling service through Microsoft and can be convenient where they are available and suited to your calling needs. Operator Connect lets you select a participating carrier while managing the connection through Teams. Direct Routing connects Teams to a third-party carrier or session border controller and is often chosen when a business needs more carrier flexibility, existing contracts, or a broader telephony design.
The best choice depends on your geography, current numbers, international calling needs, carrier preferences, and IT resources. A single-office company with predictable domestic calling has different requirements from a company that maintains local numbers across several countries or needs to preserve a long-standing carrier relationship.
Route Calls With Native Teams Features
Once PSTN connectivity is in place, Teams can handle common routing scenarios well. An auto attendant provides the first layer of call handling. It can play greetings, announce office hours, present menu choices, and direct callers based on their selection.
A call queue handles the next layer: distributing calls to a group. You might create separate queues for sales, support, and accounts receivable. Agents can answer calls in Teams, while queue settings determine who receives calls, how long they ring, and what happens when no one is available.
For a simple business, that may be enough. A main number can route calls to one menu, then to a few department queues. Employees can use Teams on their computers, mobile devices, or supported desk phones, which gives distributed teams a consistent business number wherever they work.
The operational detail matters. Decide what should happen if every agent is busy, a caller waits too long, or the office is closed. Without explicit rules, callers can encounter unanswered ringing or reach a generic voicemail at the wrong time.
When a PBX Adds Needed Control
Teams is an excellent user interface for calls, but it is not always the easiest place to build and maintain detailed telephone logic. A PBX layer can make complex routing more manageable by centralizing the rules behind your Teams users, desk phones, mobile endpoints, and business numbers.
This is useful when a call needs to follow conditions rather than a fixed menu. A caller might be routed by time of day, department availability, location, language, caller ID, or an emergency overflow rule. A service business may direct calls to an on-call technician after 6 p.m. A clinic might route a holiday call to a recorded message and an urgent-care line. A retailer may send calls from each local number to the corresponding store while allowing the central team to monitor every queue.
An integrated PBX also helps when Teams is only one part of the environment. Many businesses need a mix of Teams users, desk phones in common areas, mobile workers, conference rooms, and analog devices. Managing these through a single call-flow interface reduces the chance that each device type becomes its own configuration project.
Ayrix, for example, connects Microsoft Teams with PBX functions such as IVR menus, queues, ring groups, calendar-based availability, forwarding, supervision, and dashboards. The practical benefit is not another tool for its own sake. It is the ability to build business call handling once and apply it consistently across endpoints.
Design the Call Flow Before You Configure It
The fastest way to create a confusing phone system is to start clicking through settings before mapping the customer journey. Begin with the numbers people dial and the outcomes they should reach.
For each primary number, identify the greeting, menu choices, destination groups, business hours, holiday behavior, queue timeout, overflow destination, and voicemail ownership. Keep menus short. Most callers should reach their destination in one or two selections, not navigate five options to speak with a person.
Then consider the exceptions. If the sales team is in a meeting, should calls wait, ring the receptionist, go to a backup group, or offer a callback? If the support queue exceeds a certain wait time, should new callers hear an expected wait message or be routed to a service partner? If one office closes earlier than another, should the same main number use location-specific rules?
These decisions are operational policies, not just technical settings. When they are documented, IT can configure routing with confidence and managers can verify that the system supports the customer experience they expect.
Avoid the Common Cost and Configuration Traps
Teams calling costs are not limited to a user license. Review number rental, calling usage, carrier charges, licensing for call handling, hardware where needed, and the administrative effort involved in ongoing changes. The lowest advertised per-user price may not be the lowest total cost once queues, multiple locations, and advanced routing are added.
It also helps to separate what must be standardized from what can remain flexible. Standardize greetings, naming conventions, emergency routing, and access permissions. Keep department schedules, queue membership, and temporary forwarding easy for authorized managers to update. A web-based administration interface and automated provisioning can make a meaningful difference when users, devices, or on-call schedules change frequently.
Security should be part of the design as well. Limit who can alter routing rules, protect administrator accounts with strong authentication, and review permissions when staff leave or change roles. Test emergency calling behavior for every location and endpoint. Emergency services requirements vary by location, and a remote worker’s address can matter as much as the assigned business number.
Test the Calls Your Customers Actually Make
A call flow that looks correct on a diagram can still fail in practice. Test from an external mobile phone and a landline if possible. Call during business hours, after hours, during a simulated queue overflow, and on a holiday schedule. Confirm that transfers work, voicemail reaches the right mailbox, and caller ID appears as intended.
Ask a person outside the configuration team to try the menu. They will often find unclear wording, unexpected delays, or paths that seemed obvious only to the person who built them. Review call reports after launch to identify abandoned calls, long queue times, and departments that need staffing changes.
Teams can route external calls effectively, but the customer experience depends on the routing design behind it. Start with a clear business call flow, choose PSTN connectivity that fits your organization, and use a PBX layer when your rules outgrow a simple menu and queue. That approach keeps every call moving while giving your team control without turning phone administration into a full-time job.
English 
Deutsch (Schweiz) 
