Guide G13 VoIP & telephony
A phone-system change is its own project - not an unnamed line item in IT support.
A dropped call gets treated as a generic 'IT is down' ticket. Porting a number, changing VoIP providers, or redesigning call routing is a different, bounded project with its own risks: porting windows, emergency-call routing, and call quality. This guide separates the two.
G13 · Entry 01 Three different phone-system jobs
Name the job before naming the provider.
Calls are dropping or a phone won't register
Bring the extension, device, network location, and error. This is a support ticket.
You're porting numbers or changing providers
A number port, new provider, or routing redesign is a scoped project with its own timeline.
Call quality needs an ongoing owner
When the business depends on the phone system daily, coverage and quality may need recurring ownership.
G13 · Entry 02 Decision matrix
Match the situation to the right first route.
| Observed need | Best first route | Useful evidence | Boundary |
|---|---|---|---|
| One phone or extension stopped working | Support | Extension, device, network location, error | Not a phone-system migration |
| You're porting a number to a new VoIP provider | Scoped project | Current provider, contract end date, number(s) | Porting windows are set by carriers, not any provider |
| Call routing or after-hours rules need a redesign | Scoped project | Current call flow, hours, desired routing | Not a same-day change on shared infrastructure |
| Call quality is inconsistent across the office | Managed IT (network) or a scoped project | Bandwidth, wired vs. Wi-Fi handsets, time-of-day pattern | May depend on the firewall and Wi-Fi picture too |
G13 · Entry 03 Prepare the brief
Bring these facts to a VoIP or telephony conversation.
- Current provider, contract end date, and number(s) to port.
- Number of users, extensions, and any shared or reception lines.
- Whether emergency-call location routing is set correctly per site.
- Call-flow needs: hours, hold, voicemail, and after-hours rules.
- Network readiness: bandwidth, wired versus Wi-Fi handsets.
- The trigger: a contract end date, an outage pattern, or a new site.
G13 · Entry 04 What this covers
What this guide covers, and what it does not.
- In scope
- Separating a phone outage from a porting/migration project or ongoing ownership, and the evidence a phone-system change needs.
- Out of scope
- Carrier porting timelines, set by the losing and gaining carriers, and legal advice on emergency-calling obligations.
- Possible next decision
- Immediate support, a scoped porting or migration project, or ongoing ownership of call quality and routing.
G13 Next
Scope the port or redesign before you switch providers.
Compare a scoped connectivity or phone-system project, or check the network guide if call quality is the underlying symptom.