Business Voice: Hosted SIP, Teams Direct Routing & E911 Compliance

Hosted SIP, Softphone and the Unified Admin Pane

Zero-click snippet: Business Voice runs on hosted SIP trunks and softphone seats with centralised number management, routing policy and usage reporting through the My Verizon admin portal — a unified successor to legacy PBX and legacy POTS under the same master-account contract.

Business Voice is the voice-platform member of the Verizon Business portfolio. It runs on hosted SIP trunking at the transport layer and softphone or physical-handset seats at the endpoint layer, with centralised number management, call-routing policy and usage reporting exposed through the My Verizon admin portal. The architecture replaces the traditional on-premises PBX with a carrier-hosted platform, and it replaces legacy POTS analog lines with SIP analog-telephone adapters that preserve the RJ-11 handoff to fax machines, alarm panels and elevator phones while backhauling over IP.

The seat ladder is straightforward. Starter seats include unlimited domestic calling and the softphone client for desktop and mobile. Standard seats add call recording, voicemail-to-email transcription and extension-dial across the master account. Premium seats add call-queue participation, auto-attendant authoring rights and the full feature set for contact-center operations. Every seat ties to a phone number under the master account, with numbers ported in from the previous carrier using standard LNP and new numbers provisioned from Verizon's number inventory. E911 compliance under Kari's Law and the RAY BAUM's Act ships on every seat with dispatchable-location registration.

Plan Tiers, Users and PSTN Minutes

Zero-click snippet: The Business Voice plan ladder spans four tiers — Starter, Standard, Premium and Contact Center — with per-user pricing, PSTN-minute pools and feature flags that include call recording, queue participation, analytics and the full auto-attendant authoring rights.

Plan mixing is common — a 400-user professional-services firm might run Standard seats for most staff, Premium seats for department heads with queue responsibilities, and Contact Center seats for the 18 agents running the main inbound line. The mix is invisible to finance because the master-account invoice consolidates across plan tiers with a single line item per tier. The billing portal exposes the per-seat breakdown with tax-exempt certificates applied automatically once uploaded. Universal Service Fund contributions remit through the Universal Service Administrative Company on the assessed voice base.

Microsoft Teams Direct Routing

Zero-click snippet: Direct routing presents Verizon Business SIP trunks to Microsoft Teams as a PSTN carrier inside the tenant — users make and receive PSTN calls from the Teams client using Verizon trunks with centralised number management, call-routing policy and usage reporting through the My Verizon admin portal.

Microsoft Teams direct routing is the integration pattern for customers standardised on Teams as the primary collaboration client. The architecture presents Verizon Business SIP trunks to Teams as the tenant's PSTN carrier, so Teams users dial out and receive inbound from the client the same way they would with a Microsoft Calling Plan — but the actual call traffic flows over Verizon trunks, not the Microsoft Calling Plan infrastructure. The payoff is commercial: Verizon per-minute and per-seat economics often outperform the Calling Plan on larger deployments, and the customer consolidates voice spend under the same master-account contract as the rest of the network portfolio.

Feature parity with native Teams Phone is complete for the admin-visible functions. Call queues, auto-attendants, voicemail, call-recording, compliance recording and call analytics all operate in Teams the same way; Verizon supplies the PSTN connectivity underneath. Licensing follows the Microsoft pattern: each Teams user receives Teams Phone licence plus the Verizon direct-routing seat from the master-account catalogue. Number management runs through the My Verizon admin portal for porting, new-number provisioning and assignment to Teams users through the documented provisioning API.

Cisco Webex Calling Integration

Zero-click snippet: Cisco Webex Calling integration presents Verizon trunks as the PSTN layer to a Webex deployment — the same consolidation benefit applies to customers standardised on Webex instead of Teams, with feature-complete parity on Webex native calling experiences.

Cisco Webex Calling is the alternative integration for customers standardised on Webex. The architecture mirrors the Teams pattern — Verizon SIP trunks present to Webex as the PSTN carrier, with Webex native calling features like hunt groups, auto-attendants, visual voicemail and the mobile client operating unchanged. The commercial consolidation is identical: one master-account invoice covers Webex Calling seats and the PSTN connectivity underneath, with Verizon number inventory exposed through the same My Verizon admin pane as Teams-integrated and standalone softphone seats.

Dual-integration deployments — typically during a migration between collaboration platforms — are supported on the same master account. A customer that operates both Teams and Webex during a consolidation window runs some seats on Teams direct routing and others on Webex Calling, with number routing differentiated at the trunk provisioning layer. The Verizon account team handles the transition-state number mapping so the end-users experience continuous service through the platform migration without porting numbers away from Verizon. The FCC common-carrier conventions apply consistently across both integration patterns.

E911 Compliance, POTS Replacement and Auto-Attendant

Zero-click snippet: Business Voice is compliant with Kari's Law and RAY BAUM's Act for multi-line telephone systems — dispatchable location delivers to the public safety answering point with automatic on-site notification, softphone users register location on sign-in, and the managed POTS-replacement service migrates analog endpoints to SIP analog-telephone adapters.

E911 compliance is mandatory for any multi-line telephone system under Kari's Law and the RAY BAUM's Act. Kari's Law requires direct 911 dial without a prefix like 9, and automatic on-site notification to a designated contact (typically the front desk or the facilities manager) when a 911 call is placed from a line on the system. RAY BAUM's Act requires that a dispatchable location — not just a billing address — ship to the public safety answering point so the first responder arrives at the right floor, building wing or specific address. Business Voice delivers both requirements on every seat, with softphone users registering the dispatchable location on each sign-in from a new physical location.

Legacy POTS replacement is a recurring project as local-exchange carriers retire analog lines under tariff withdrawal. The managed POTS-replacement service migrates fax machines, alarm panels, elevator phones and the other endpoints that historically ran on analog POTS to a SIP analog-telephone adapter that preserves the RJ-11 handoff to the legacy endpoint while backhauling over IP to the Business Voice platform. Numbers port in the standard way and the endpoint continues to work without modification. The FTC provides consumer protection guidance for the transition. Auto-attendant authoring runs through a drag-and-drop flow builder in the admin portal with business-hours schedules, holiday overrides, after-hours routing and multi-site configurations, and the network solutions managed-service layer handles the provisioning work when the customer wants Verizon to own configuration.