Field note / voice and Teams telephony

You do not need to be a phone-system dealer to own this lane.

Hosted VoIP and Microsoft Teams Phone administration is a genuine recurring lane for agencies, consultants, and IT firms that are not already in the business of selling phone systems. It is a different audience than the connectivity-dealer question this site answers elsewhere - this page is for the partner adding voice as a new lane, not resolving one they already sell.

Who this lane is for

The other side of the telecom-dealer boundary.

Telecom and office-equipment dealers already sell and service phone systems, so a managed IT lane for them explicitly excludes phone-handset and system faults - that work already has a home. This page is for the partner on the other side of that line: an agency, consultant, or IT firm whose clients run hosted VoIP or Microsoft Teams Phone, and who wants to administer it as a recurring lane rather than leaving it to whichever vendor sold the licence.

Read the dealer-side boundary this contrasts with →

Coverage area

Teams Phone administration

A tenant already has calling plans or direct routing configured.

Included pattern: Number assignment, calling-plan or direct-routing configuration, and user/queue changes inside an existing Teams Phone deployment.
Required inputs: Tenant calling-plan or carrier setup already in place, and current admin access.
Explicit exclusions: Negotiating or replacing the underlying carrier or calling-plan contract.

Coverage area

Hosted VoIP platform administration

A hosted VoIP platform outside Teams is already deployed.

Included pattern: User, extension, and call-routing changes on an already-deployed hosted VoIP platform.
Required inputs: The platform in use and current administrative access.
Explicit exclusions: Physical handset deployment or desk-phone hardware faults.

Coverage area

Auto-attendant and call-queue changes

Greetings, queues, and routing rules need routine upkeep.

Included pattern: Routine updates to greetings, hold queues, and routing rules within an agreed change process.
Required inputs: Current call-flow documentation, even informal.
Explicit exclusions: A full call-flow redesign without a separate scoping step.

Coverage area

Porting and number changes

A number needs to move between carriers or accounts.

Included pattern: Coordinating a number port or reassignment request through the carrier's own process.
Required inputs: Current carrier details and account-holder authorization.
Explicit exclusions: Carrier-side delays or outages, which stay a vendor dependency.

Boundary table

What voice administration is qualified to cover.

Question	Why the public bands cannot answer it	Where it gets answered
Does this include desk-phone hardware faults?	Hardware faults are a device-support question, closer to the endpoint lane than to voice administration.	Scoped separately if a client has physical handsets to support.
Who owns the carrier or calling-plan relationship?	Whoever holds the billing relationship with the carrier, same principle as any other vendor dependency.	Named in the vendor-escalation record.
What happens if a port takes longer than expected?	Number-porting timelines are set by the carrier, not by delivery.	Communicated honestly as a vendor dependency, not guessed at.
Is this available to a telecom or office-equipment dealer?	It can be, but the fit question is different - most dealers already own this work.	Confirmed during partner-fit qualification either way.

What not to promise yet

Keep the offer honest until the carrier and hardware boundary is named.

A guaranteed porting date
Coverage for a carrier or ISP outage
Desk-phone hardware repair or replacement
A call-quality guarantee tied to a connectivity provider outside this scope
Emergency-calling configuration without confirming it explicitly as part of scope

Review the network lane voice traffic actually runs on →

Related decision

Teams Phone lives inside the same tenant as everything else.

Number and user administration for Teams Phone follows the same tenant-handoff record as the rest of Microsoft 365 fulfilment.

Review Microsoft 365 fulfilment

Bring the platform and one routine change type.

Naming the platform and a common request - a new number, a queue change - is enough for an initial fit review.

Discuss a VoIP or Teams Phone lane