Teams Phone
A Microsoft Teams Phone system that replaces your PBX, ready for voice AI
Calling moved to Microsoft Teams Phone: number porting, auto attendants, call queues and desk phones, on the platform resident and customer voice agents run on.
Discover · design · deploy · optimize
Cisco, Avaya, Mitel and Skype for Business to Teams.
On this page
Short answer
Communication Square moves organizations from on-premises and legacy phone systems to Microsoft Teams Phone: calling architecture, number porting, auto attendants and call queues, desk and conference phones, and user training. Teams Phone is also the platform AI voice agents run on, so the same project prepares you for resident or customer voice AI.
Starting points
Where Teams Phone projects start
What it really is
A Microsoft Teams Phone system is call flows, numbers and people, not just licenses
Assigning Teams Phone licenses is easy. The work is the calling design, porting and the hand-off to staff.
Your options
Keep the PBX, a hosted phone vendor, or Teams Phone
Most Microsoft 365 customers already have Teams on every desktop.
| Keep the PBX | Hosted phone vendor | Teams Phone (us) | |
|---|---|---|---|
| Where staff take calls | Desk phone | Separate app | Teams on desktop, mobile and desk phone |
| Support and upgrades | Hardware and maintenance | Vendor contract | Microsoft cloud, managed by us |
| Voice AI | Not available | Vendor add-on | Voice agents on the same lines |
| Licensing | Separate | Separate | Part of Microsoft 365, one invoice |
| Government cloud | n/a | Varies | Teams Phone for GCC available |
What is included
What the work covers
Calling architecture
Auto attendants, call queues, routing, holidays and after-hours.
Number porting
Porting plan, testing and cutover for every number.
PSTN connectivity
Microsoft calling plans or direct routing through a carrier.
Devices
Poly and other certified desk, conference and headset devices.
Emergency calling
Emergency locations and policies configured.
Training and handover
User and admin training, then optimization.
Our approach
Discover, design, deploy, optimize
- DiscoverCurrent system, numbers and call flows.
- DesignTeams calling design and porting plan.
- DeployPilot, port and cut over in stages.
- OptimizeTune queues and train staff.
Our promise: numbers are ported in planned windows with the old system ready to take calls until each cutover is tested.
AI on this foundation
The phone system voice agents run on
Resident and customer voice agents answer on Teams Phone lines and transfer to Teams users. Moving to Teams Phone is step one.
Proof
Where we have done this
The offer
Start with a free Microsoft 365 assessment
A read-only look at your tenant: licenses, accounts, security hygiene and what this project would involve, with a fixed-price plan you keep.
Current-state map
Licenses, accounts and configuration as they are today.
Risk and gap list
What to fix first, ranked by risk and effort.
Plan and fixed price
Scope, timeline and a fixed price for the work.
- Free for customers and non-customers
- About one week
- Read-only: nothing changes
- The plan is yours to keep
Why free? It is how we scope a fixed price we can stand behind, and it shows you what to fix whether or not you hire us.
How it runs
Day 0Scoping call with the engineer who would run the work.
Days 1–2You grant temporary read-only access.
Days 2–4We review the environment.
Day 5Findings and a fixed-price plan. Access is removed.
We reply within one business day.
Read-only access you grant and remove. Nothing in your environment changes, and no content leaves your tenant.
Why us
A Microsoft partner that builds, licenses and runs it
Transparent investment
What the work typically costs
Published, fixed prices for the common cases. The free assessment confirms scope before you commit.
| Engagement | Typical timeline | Typical investment |
|---|---|---|
| Teams Phone assessment and calling design | About 1 week | $2,500 |
| Teams Phone implementation, up to 100 users | About 4 weeks | $9,997 |
| Multi-site rollout, 100–500 users | 4–8 weeks | $14,900–$29,900 |
| Devices and calling plans | As needed | At list price |
Want a figure for your organization? Get an estimate in 2 minutes with our pricing calculator.
Implementation includes porting, auto attendants, call queues, emergency calling and training. Phones and calling licenses are itemized separately.
| Engagement | Typical timeline | Typical investment |
|---|---|---|
| Teams Phone assessment and calling design | About 1 week | $5,000 |
| Teams Phone implementation, up to 100 users | About 4 weeks | $17,900 |
| Multi-site rollout, 100–500 users | 4–8 weeks | $17,900 + $65 per user above 100 |
| Devices and calling plans | As needed | At list price |
Government prices include procurement documentation, accessibility and records requirements, and delivery in Microsoft’s Government Community Cloud where required.
Common questions
Microsoft Teams Phone system: questions people ask
Can Microsoft Teams replace a phone system?
Yes. Teams Phone is a cloud PBX: it gives each user a phone number, voicemail, transfers, auto attendants and call queues, and works on desk phones as well as computers and mobiles. It needs a Teams Phone license plus a way to reach the phone network. Orange County Transportation Authority moved about 600 employees to it with us.
Operator Connect or Direct Routing?
Both connect a Microsoft Teams PBX to the phone network. With Microsoft Calling Plans, Microsoft is the carrier. With Operator Connect, a Microsoft-certified carrier provides the numbers and you manage them in the Teams admin center. With Direct Routing, your own session border controller connects any carrier. We recommend one in the calling design.
How long does a Teams Phone migration take?
Our calling design takes about a week; implementation for up to 100 users takes about 4 weeks; multi-site rollouts of 100 to 500 users take 4 to 8 weeks. Number porting sets much of the pace, so we start the port requests early.
Questions buyers ask
Before you decide
Can we keep our phone numbers?
Yes. Numbers are ported to Microsoft or your carrier in planned windows.
Do we still need desk phones?
Only where people want them. Most staff use Teams on their computer and mobile; reception and shared spaces often keep certified desk phones.
What about 911 and emergency calling?
Emergency locations and dispatchable addresses are configured as part of the project.
Can we add a voice agent later?
Yes. Voice agents run on Teams Phone lines, so the platform is ready when you are.
Retire the old phone system
Start with a free assessment of your phone system, numbers and call flows.
