Microsoft Teams Phone

What the phone system does with a call: local geographic numbers in the customer's own area code and in other countries, number blocks and porting of existing numbers, extensions, IVR menus, queues, ring groups and hunt groups, time-based and holiday routing, call forwarding and transfer, voicemail to email, fax to email, conference calls, call recording, call park and pickup, busy lamp fields, caller ID per user or team, and emergency calls (110 and 112) with the caller's location.

0 — Places no phone calls on the public telephone network; a chat or meeting tool with internal calling only.

3 — Phone numbers and extensions with forwarding and voicemail; IVR, queues, time-based routing and porting are basic or not described.

5 — Local numbers in the customer's area code with porting documented, IVR menus, queues and ring groups, time-based and holiday routing, voicemail to email, call transfer and pickup, call recording, fax or fax to email, and emergency calling described.

8 — Number blocks and international numbers in many countries, a visual call flow editor, skills or priority routing, call park and busy lamp fields, recording rules per user or queue with consent announcements, emergency calls with a registered location per user or site, and the porting process and its timelines documented.

10 — Call handling a large multi-site company runs on: every feature above with number provisioning and porting by API, routing by caller data from the CRM, location-aware emergency calling for home offices, and the full feature set documented per plan with its limits.

Where the calls are made and taken: desktop and mobile softphone apps, a browser client, presence, desk phones and DECT handsets from named makers (Yealink, Snom, Gigaset, Poly, Cisco) provisioned automatically, devices for sale or rent, the mobile phone as an extension with the company number shown, fixed-mobile convergence, Microsoft Teams calling through Direct Routing or Operator Connect, headset support, and the apps' ratings and update notes.

0 — No app and no device support; calls only through hardware the customer configures by hand.

3 — A softphone or mobile app; desk phones, Teams calling and the company number on mobile are basic or not described.

5 — Desktop, mobile and browser apps with presence, desk phones from named makers provisioned automatically, the company number shown on outgoing mobile calls, call handover between devices, and a Microsoft Teams integration or connector.

8 — A list of supported desk and DECT phones with auto-provisioning documented, devices sold or rented, Microsoft Teams calling through Direct Routing or Operator Connect with certification stated, fixed-mobile convergence with a SIM or mobile network, and app features documented per platform.

10 — Every endpoint a workforce uses, managed from one place: desk, DECT, mobile, browser and Teams with feature parity stated, device fleet management and firmware updates from the portal, and the app's accessibility and offline behaviour documented.

How a team that lives on the phone is run: ACD queues with skills and priorities, agent states and wrap-up time, a wallboard, live monitoring with listen, whisper and barge, callbacks instead of waiting, outbound and power dialers, call statistics and reports per agent and queue, missed-call handling, AI transcription, summaries and sentiment, an AI receptionist or voicebot, and SMS or WhatsApp beside calls.

0 — No queues or call statistics of any kind; calls ring until someone answers.

3 — A simple queue and a call history; agent states, live monitoring, reports and AI features are basic or not described.

5 — Queues with agent log-in and log-out, wrap-up time, a wallboard or live view, call statistics per agent and queue, missed-call lists with callback, call recording for coaching, and AI transcription or summaries offered.

8 — Skills-based routing, listen, whisper and barge, callback in queue, outbound or power dialers, scheduled and exportable reports, AI transcription, summaries and sentiment with the languages listed, an AI receptionist or voicebot, and SMS or messaging channels beside calls.

10 — A contact centre that replaces a separate suite: workforce management and quality scoring, omnichannel routing, real-time AI coaching, and every AI feature documented with its model provider, data handling and an opt-out.

How the phone system fits the company: integrations with CRM and helpdesk tools (Salesforce, HubSpot, Pipedrive, Zendesk, Microsoft Dynamics) with click-to-call, caller pop-ups and automatic call logging, a documented REST API and webhooks for call events, SIP trunks for an existing PBX and bring-your-own-carrier, an admin portal with roles, single sign-on (SAML) and SCIM, two-factor authentication, multi-site and multi-company set-up, bulk user import, audit logs, and partner or reseller accounts.

0 — No integrations and no administration beyond one login per number.

3 — A web portal to manage users and numbers and one or two integrations; the API, roles and SSO are basic or not described.

5 — Integrations with the common CRM and helpdesk tools with click-to-call and call logging, a documented REST API and webhooks, an admin portal with roles, two-factor authentication, several sites in one account, and SIP trunking or a connection to an existing PBX.

8 — Caller pop-ups and call data written to the CRM record, an API covering users, numbers, routing and call records, single sign-on (SAML) and SCIM provisioning, audit logs, bulk import and templates, partner or reseller accounts with sub-customers, and SIP trunks documented for named PBX systems.

10 — Administration that scales across many sites and companies: every setting reachable by API with parity stated, granular roles per site and team, SSO enforced with SCIM, audit logs exportable to a SIEM, and a partner portal with white-label and separate billing.

Whether the service holds on a bad day and in an audit: redundant data centres and carrier connections, a stated availability or SLA with credits, the vendor's own public status page and incident history, call quality measures (codecs, quality monitoring), encryption of signalling and media (TLS and SRTP), registration as a telecoms provider with the national regulator (Bundesnetzagentur or its EU equivalent), the secrecy of telecommunications, recording consent and retention, emergency call handling for remote users, fraud protection against toll fraud, and security certifications such as ISO 27001.

0 — Nothing on availability, security or the provider's status as a telecoms operator.

3 — A claim of high availability or "German data centres"; encryption, the SLA, the status page and regulatory status are basic or not described.

5 — Redundant data centres named by country, a public status page, TLS and SRTP encryption offered, the provider's registration with the national regulator or the carrier behind the numbers stated, a stated availability, and call recording rules described.

8 — An SLA with credits published, the incident history public, encryption on by default with the protocols documented, ISO 27001 or comparable certification with its scope, toll fraud protection and spending limits, emergency calls from softphones and home offices documented, and retention of recordings and call records stated.

10 — Carrier-grade operation evidenced: geo-redundant platforms with failover tested and published, end-to-end encryption options, independent audits (ISO 27001, BSI C5 or SOC 2) with reports available, and the regulatory and lawful-interception obligations explained in plain language.

Who the contracting entity and the parent company are, where call records, voicemails, recordings, transcripts, contacts and account data are stored and processed, which carriers carry the calls, and who the subprocessors are (hosting, carriers and number providers, SMS gateways, AI transcription and summary models, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. International numbers and carriers needed to reach other countries are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted phone system the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (AI transcription, SMS, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting, carriers and every subprocessor including the AI models, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Whether a buyer can compute the real annual cost from public pages alone: price per user or extension and per plan, what numbers, number blocks and porting cost, which calls are included in a flat rate (landline, mobile, international) and what the rest cost per minute, which features (call centre, recording, AI, CRM integrations, Teams calling) cost extra, device prices or rent, set-up fees, minimum term and notice period, and VAT.

0 — No public prices at all; every customer is a sales call or a partner quote.

3 — A starting price per user exists, but what numbers, minutes, porting and add-ons cost is unclear.

5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (number blocks, porting, international minutes, call centre seats, AI or recording) is unpriced or "on request".

8 — Every plan priced publicly with its scaling rule, a per-minute price list for calls outside the flat rate, numbers, porting and devices priced, add-ons priced, set-up fees, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of users, numbers, sites and call minutes, with every add-on, device, porting and support fee and the cancellation and number-export terms published.