Cradle vs Microsoft Teams Phone: cloud phone system comparison for AU and NZ accounting firms
Microsoft Teams Phone bolts calling onto a collaboration product. Cradle is a calling product first. Here is an honest comparison for accounting and professional-services firms in Australia and New Zealand: where each tool fits best, and why for many firms the right answer is to keep Teams for chat and meetings and run Cradle alongside it for calls.
Last verified:
Cradle is a calling product, not a collaboration product with calling bolted on. The desktop and mobile apps are shaped around taking calls all day: ring groups, smart routing, voicemail transcription, recording, caller ID against the practice tool.
FYI, Xero Practice Manager and HubSpot all live on every paid Cradle tier. AI summaries post into the FYI activity feed, time entries draft on FYI Elite with FYI AI, HubSpot picks up the call with caller ID and recording.
Keep Microsoft Teams for chat, channels and meetings. Run Cradle alongside it as the calling layer. The two products run on the same device. See /integrations/ms-teams.
Try Cradle in your browser
Click through the call log, in-call screen, messages and settings. Every contact-bearing row shows the FYI, XPM and HubSpot badges, so you can see what Cradle running inside your practice tools looks like before you book a call.
Trusted by accounting firms across Australia and New Zealand
“The biggest game changer for us is that every call is automatically saved into FYI. That means no more missed notes or chasing people for messages. The accountants can just go back and see the conversation for themselves”
How Cradle helps
Three things accounting and professional-services firms in Australia and New Zealand consistently tell us they want from a phone system. Cradle is built for all three.
Purpose-built for calls-as-primary-channel
Cradle is a calling product first, not a calling layer on top of a chat tool. The Cradle desktop and mobile apps are shaped around the work of taking calls all day: ring groups, sequential ring, round-robin, business-hours routing, fail-safe routing, voicemail transcription, call recording, smart caller ID against the practice tool. Teams Phone can do most of these too, but the configuration sits inside the Teams admin centre, the PowerShell module or a Power Automate flow, and is generally the domain of an IT admin rather than a front-desk team lead.
Built around the accounting workflow
FYI activity logging, draft time entries on FYI Elite with FYI AI, XPM client lookup, HubSpot calling. Calls log themselves into the right client record. AI summaries land in the FYI activity feed, time entries draft on FYI Elite with FYI AI, and HubSpot picks up the call with caller ID against the right contact. Teams Phone has no native FYI, XPM or HubSpot integration. The equivalent write-back can be built with Power Automate or a third-party connector, but that is engineering work for an IT team rather than a checkbox.
Works alongside Teams, doesn't replace it
Keep Teams for chat and meetings. Run Cradle for calls. If your firm already runs Microsoft 365 and your team uses Teams every day for chat, channels and meetings, you do not have to give that up. Cradle works alongside Teams: keep Teams as the collaboration product, and run Cradle as the calling layer that writes into FYI, XPM and HubSpot. See /integrations/ms-teams for how the two products coexist on a single device.
Which one wins for your stack?
Four common stacks, four direct recommendations. The honest answer for many firms is to run both.
You're a chat-and-meetings-first firm taking occasional calls
If your firm already has Microsoft 365 (especially E5) and your team takes a handful of calls a day, Teams Phone is fine and already bundled with the rest of your stack. Cradle would be over-specified.
Your firm makes calls central to the workflow (accounting, legal, professional services)
Calls are how the work gets done, and the calling tool needs to write into the practice tool. Cradle ships FYI, XPM and HubSpot today; AI summaries land in the activity feed; time entries draft on FYI Elite with FYI AI. Teams Phone does not.
You already use Teams for chat and want a purpose-built calling layer
Keep Teams for chat, channels and meetings. Run Cradle as the calling layer that writes into FYI, XPM and HubSpot. The two coexist on a single device. See /integrations/ms-teams.
You're committed to Microsoft 365 with IT capacity for Direct Routing or Operator Connect
If your IT team is happy to configure SBCs, certificates and routing policies, and building FYI / XPM / HubSpot write-back via Power Automate is acceptable, Teams Phone fits. Cradle is plug-and-play for firms that would rather not run that project.
Cradle vs Microsoft Teams Phone: the detail
Six views of the comparison: the headline summary table, the integrations side-by-side, AI features, pricing positioning, the setup experience, and a FAQ.
Where each tool fits best
Microsoft Teams Phone fits best when: your firm is chat-and-meetings-first and takes occasional calls; you already run Microsoft 365 (especially E5); your IT team is happy to manage Calling Plans, Operator Connect or Direct Routing; you do not need write-back into FYI, XPM or HubSpot; you would rather pay one vendor for the whole communications stack.
Cradle fits best when: calls are central to how your firm bills (accounting, legal, professional services); you run FYI, XPM or HubSpot and want the calling tool to write into them without a Power Automate project; you want a front-desk team lead to manage routing without opening a PowerShell module; you want the desktop and mobile experience shaped around calls rather than channels and meetings.
For many firms the honest answer is to do both: keep Microsoft Teams for chat, channels and meetings, and run Cradle alongside it as the calling layer. Cradle is built to coexist with Teams. See /integrations/ms-teams.
| Capability | Cradle | Teams Phone |
|---|---|---|
| Product shape | Cloud-native calling product | Calling bolted onto Microsoft Teams |
| Built for | Firms where calls are the primary channel | Microsoft 365 collaboration users |
| Provisioning | Browser, same day | Calling Plans, Operator Connect or Direct Routing |
| Direct Routing required | Required if you bring your own carrier | |
| FYI integration | ||
| Xero Practice Manager (XPM) | Deep accounting workflow | |
| HubSpot CRM | no (Power Automate / third-party) | |
| Karbon | On roadmap | |
| Coexists with Microsoft Teams | yes (alongside) | n/a (is Teams) |
| AI call summaries + transcripts | On Pro + Enterprise | Via Copilot for Microsoft 365 |
| AI summaries into FYI activity feed | ||
| Time entries on FYI Elite + FYI AI | ||
| Mobile and desktop apps | yes (Teams) | |
| Call recording | yes (policy-based) | |
| Ring groups, IVR, business-hours routing | yes, configured by team lead | yes, configured by IT admin |
| Number porting handled end-to-end | yes (Cradle onboarding) | Depends on connectivity model |
| Free trial on public site | yes (one-month, Teams Phone Standard) | |
| Self-serve sign-up | Via Microsoft 365 or partner |
Teams Phone offers a one-month free trial of Teams Phone Standard via the Microsoft sign-up flow (credit card required). Cradle exposes a free-trial path alongside its demo CTA on /pricing.
Microsoft Teams Phone has three PSTN connectivity modes (Calling Plans, Operator Connect, Direct Routing), each with its own licensing and setup path. Confirm which mode your firm would run before comparing list prices. The full set of options is documented at learn.microsoft.com/en-us/microsoftteams/cloud-voice-landing-page.
Practice tools side-by-side
For accounting and professional-services firms, the depth of the practice management integration is the biggest single difference between Cradle and Teams Phone. Cradle ships FYI, XPM and HubSpot on every paid tier. Teams Phone has none of these natively; the equivalent write-back can be built with Power Automate, Logic Apps or a third-party connector, but it is an IT project rather than a checkbox.
| Integration | Cradle | Teams Phone | Notes |
|---|---|---|---|
| FYI | Cradle ships FYI activity logging, voicemail transcription and AI summaries into the FYI activity feed, with time entries drafting on FYI Elite with FYI AI. Teams Phone has no native FYI integration. See /integrations/fyi. | ||
| Xero Practice Manager (XPM) | Cradle covers client identity on inbound calls, click-to-call and call logging into the right client record. Teams Phone has no native XPM integration. See /integrations/xpm. | ||
| HubSpot CRM | Cradle is a HubSpot calling app: click-to-call, caller ID, call recording and (on Professional and Enterprise) HubSpot conversation intelligence. Teams Phone has no native HubSpot integration; write-back requires Power Automate or a third-party connector. /integrations/hubspot. | ||
| Karbon | On roadmap | On Cradle's roadmap. Teams Phone has no native Karbon integration. | |
| Microsoft Teams (chat and meetings) | Works alongside | Is Teams | Cradle is designed to run alongside Microsoft Teams. Keep Teams for chat and meetings; use Cradle for calls. See /integrations/ms-teams. |
| Power Automate / Logic Apps | Via webhooks | Teams Phone's extension story sits inside the Microsoft Power Platform. Cradle exposes webhooks and a public REST API, which Power Automate can call. | |
| Microsoft 365 sign-in | yes (SSO) | Native | Both products support sign-in through Microsoft 365. Teams Phone is provisioned from the Microsoft tenant; Cradle supports Microsoft single sign-on. |
AI summaries, transcripts and time tracking
Both products ship AI features. Microsoft Teams Phone has Copilot for Microsoft 365: AI-generated notes, real-time summarisation and intelligent recap, for users with a Copilot for Microsoft 365 licence. Cradle includes AI call summaries and voicemail transcripts on Professional and Enterprise.
For accounting firms, the substantive difference is where the AI output goes. On Cradle, the summary posts into the FYI activity feed against the right client the moment the call ends. On FYI Elite with FYI AI, Cradle also drafts a time entry against the right job, ready for a partner to approve at month-end. Nobody types the call up after.
On Teams Phone, the AI output lives inside Teams. Getting the summary into FYI, XPM or HubSpot requires Power Automate or a third-party connector. The Copilot summary is genuinely useful for chat, meetings and ad-hoc context, and pairs well with the collaboration product. It just is not shaped around writing into the accounting practice tool.
Worth noting: Copilot for Microsoft 365 is licensed per user, separately from the Teams Phone tier. If AI features are decision-critical for Teams Phone, add the Copilot licence cost to the comparison.
Pricing positioning
The two products price very differently, which makes list-price comparisons easy to read wrong.
- Cradle publishes per-user subscription tiers on /pricing: Standard, Professional and Enterprise. Calling credit is included on each paid tier. FYI, XPM, HubSpot, MS Teams compatibility, business-hours routing, fail-safe routing, mobile and desktop apps, call recording and number porting are included on every paid tier.
- Microsoft Teams Phone publishes four per-user tiers on the Microsoft sales site, before the Teams licence and (if you want AI) the Copilot for Microsoft 365 licence. The plans are Teams Phone Standard, Teams Phone with Pay-as-you-go Calling, Teams Phone with Domestic Calling, and Teams Phone with Domestic + International Calling. Teams Phone Standard is the cloud phone system on its own; the calling minute bundles are add-ons layered on top.
For New Zealand, Microsoft's published prices on microsoft.com/en-nz/microsoft-teams/microsoft-teams-phone as of 14 May 2026 are NZ$16.20 (Standard), NZ$21.00 (Pay-as-you-go), NZ$35.60 (Domestic), and NZ$55.00 (Domestic + International) per user per month, assuming annual commitment.
For most accounting firms, the right way to compare total cost is to add the Teams Phone tier, the Teams licence (if not already in your Microsoft 365 plan), a Copilot for Microsoft 365 licence (if AI features are decision-critical), and the integration build-out cost for FYI / XPM / HubSpot write-back. Set that total next to Cradle's per-user subscription on /pricing, where the practice tool integrations are included.
Prices change. Check /pricing and the relevant Microsoft Teams Phone page before deciding.
What getting started looks like
Cradle. Start a free trial from /pricing without booking a sales call. If you would rather have someone walk you through it, book a 30-minute demo and the Cradle team will provision your number, users and basic routing during the call. The FYI, XPM and HubSpot integrations are configured from admin.cradle.io: a few minutes per integration, no engineering project.
Microsoft Teams Phone. Setup depends on which connectivity mode you choose:
- Calling Plans. Microsoft is the operator. Assign licences, buy numbers from Microsoft, set policies in the Teams admin centre. Simplest path, but Microsoft Calling Plans are not available in every country.
- Operator Connect. A participating operator (your existing carrier, or a new one) manages the trunk. Sit between the simplicity of Calling Plans and the flexibility of Direct Routing. List of participating operators is on learn.microsoft.com.
- Direct Routing.Bring your own carrier. Requires a certified Session Border Controller, public-trusted certificates, FQDN and DNS configuration, firewall ranges for SIP and media traffic, codec configuration. Real IT project; Microsoft's planning guide is at learn.microsoft.com.
Porting your numbers.Both products port. Cradle's onboarding team handles the LOA paperwork and the carrier liaison end-to-end; typical porting takes around two weeks. On Teams Phone, number porting depends on the connectivity mode: Microsoft handles it for Calling Plans, your operator handles it for Operator Connect, and you (or your SBC vendor) coordinate with the carrier for Direct Routing.
Frequently asked questions
Can I use Cradle and Microsoft Teams together?
Does Cradle integrate with FYI?
Does Cradle integrate with Xero Practice Manager (XPM)?
Does Cradle integrate with HubSpot?
Does Cradle integrate with Karbon?
How does pricing compare?
Which has more capable AI features?
What are the connectivity options for Teams Phone?
Can I keep my existing phone numbers if I switch from Teams Phone or another provider?
Can I try Cradle without booking a sales call?
What if I am currently on Teams Phone?
Which is better if I am a chat-and-meetings-first firm taking occasional calls?
Which is better if my firm makes calls central to the workflow (accounting, legal, professional services)?
Which is better if I already use Teams for chat and want a purpose-built calling layer?
Which is better if I am committed to Microsoft 365 and have IT capacity to manage Direct Routing or Operator Connect?
Keep reading
How Cradle coexists with Microsoft Teams, and the broader accounting workflow story.
Live integrations
For accounting firms
Book a 30-minute demo of Cradle
Bring your practice tool, your team size and your Microsoft 365 setup, and we will model how Cradle runs alongside Teams in your firm. If Teams Phone on its own is the better fit, we will tell you.


