VoIP Support for MSPs: Tiers, Escalation and Runbooks

Tom Reed
Read time: 9 minutes
VoIP Support for MSPs: Tiers, Escalation and Runbooks

Tom Reed · Updated 18 November 2026

A good VoIP support model for an MSP has three tiers: your help desk handles tier 1 support (logins, devices, network checks), a voice engineer or platform admin handles tier 2 (call flows, trunks, tenant settings), and the carrier or platform vendor handles tier 3. Write a runbook for each common fault before you go live. With SessionPBX, a multi-tenant PBX you can run on your own servers or have SessionTalk host, tiers 1 and 2 sit with you because you manage each customer's tenant.

This guide is for MSPs, ITSPs, VoIP providers and IT resellers who resell SessionPBX and need a clear model for supporting their customers' phone users after go-live. It covers what first-line staff should fix, when to escalate, and which runbooks to write before the first user has a problem.

What does VoIP support look like when you resell it?

The reseller owns the customer relationship, so first-line support is yours. When a phone user cannot sign in, a headset fails, or calls stop ringing, they will contact you, not the platform vendor and not the carrier. That is what voip support services means to a customer: one team that will take the problem and either fix it or move it to the right owner.

You should describe that model in the contract, including who handles user issues, tenant changes and carrier faults, without attaching service-level promises you are not in a position to make. Our MSP voice contract checklist is the place to capture support scope. Day-to-day voip technical support then sits with your help desk and your voice engineer. The carrier, and SessionTalk when it hosts the platform, only come in when the fault is outside the tenant.

What does tier 1 support handle?

Tier 1 support is your MSP help desk. It deals with problems that affect one user or one device, and that a first-line agent can work through from a runbook without changing the customer's tenant.

Typical work includes:

  • Sign-in and password problems, including app sign-in on the softphone
  • Re-inviting a user by email, QR code or setup link if they cannot register
  • Device and headset checks, including microphone permissions
  • Basic network checks: Wi-Fi versus mobile data, and whether a VPN is in the path
  • Push notifications, so the device actually rings
  • Voicemail, forwarding and missed-call notification settings for that member

These are member-level settings and device checks. If several users share the same symptom, or the fix needs a change to call flow, numbers or permissions, it is no longer a first-line job. Clean provisioning cuts a lot of this work; secure softphone provisioning for MSPs covers how to invite and sign users in consistently.

How do you troubleshoot common VoIP issues at tier 1?

When a user says calls fail, stay on this VoIP troubleshooting checklist before you escalate. It is the practical first-line answer to how to fix VoIP issues.

  • Confirm the user, the device, the app version, the time of the problem and the number dialled.
  • Check sign-in; re-invite by email, QR code or setup link if needed.
  • Check the network (Wi-Fi versus mobile data, and any VPN), the headset, and microphone permissions.
  • Check that push notifications are allowed, especially when calls are not ringing.
  • Check forwarding, voicemail and caller ID settings for the member.
  • Check call history for the call, then try an internal call to another extension.
  • If the runbook fails, or more than one user is affected, escalate to tier 2 with the details above.

If the complaint is audio quality itself (echo, delay or muffled speech), do not start redesigning the call flow. Use the guide to softphone call quality troubleshooting and treat that diagnosis as a separate path until you know the tenant or the trunk is at fault.

Laptop open on a desk being repaired with tools

What goes to tier 2?

Tier 2 is a voice engineer or platform admin who can change the customer's tenant. That includes call flows and IVR, ring groups and queues, business-hours routing, numbers and caller ID, extension, seat and permission changes, and questions about call recording. These are portal jobs, not help-desk jobs.

On SessionPBX, Teams Business adds a visual call flow designer, auto-attendant and IVR, business-hours routing, ring groups, call queues, call recording, supervision (listen, whisper and barge) and reports. Teams Phone and Teams Business are SessionPBX plan names. Everyday calling on Windows, macOS, iOS and Android, hold and transfer, team chat and presence, voicemail in the portal and by email, missed-call notifications, and invites by email, QR code or setup link sit with the base plan; the routing features above sit with Teams Business.

Because you manage each customer as a tenant, the same engineer can move from one customer to another without mixing their settings. That model is described in multi-tenant PBX for MSPs.

What is a good escalation process for voice?

A good escalation process makes it obvious when first-line work stops and who picks it up. Write the trigger, the owner and the details to collect into the runbook, so agents do not escalate a sign-in fault, and do not sit on a trunk fault.

TierWhoTypical issuesEscalate when
Tier 1MSP help deskSign-in, re-invite, app or device, headset, Wi-Fi, voicemail and forwarding settingsRunbook fails or more than one user is affected
Tier 2MSP voice engineer / platform adminCall flows, IVR, queues, ring groups, numbers, caller ID, seats and permissionsFault looks like trunk, carrier or platform
Tier 3Carrier, or SessionTalk (hosted) / your own infrastructure team (self-hosted)Trunk, number routing, platform or server issuesn/a

Collect the user, the device, the time of the problem, the number dialled, the call direction (inbound or outbound), and what the agent already tried. That is enough for a voice engineer to reproduce the issue, and enough to hand to a carrier or to SessionTalk if the fault leaves the tenant.

When do you escalate to the carrier or SessionTalk?

Escalate to the carrier when the fault looks like the trunk, or like inbound or outbound number routing, including porting faults on numbers the carrier supplied. SessionPBX uses your own SIP trunk from any SIP-compliant carrier. SessionTalk does not sell trunks, minutes or numbers; the carrier bills for those, and internal calls between team members are included.

If you self-host SessionPBX, you own the server, hosting and network, so infrastructure faults stay with your own team. If SessionTalk hosts the platform for you, platform-side issues go to SessionTalk. Keep the hand-off factual: what happened, when, which tenant and which numbers, and what you have already ruled out. Do not attach a response-time promise to either path.

Which runbooks should you write before go-live?

Write a runbook for each common fault before the customer goes live, then train the help desk on it. At a minimum cover:

  • New user, including invite by email, QR code or setup link
  • Leaver, including removing access and rerouting their extension
  • Lost phone, including signing the user out and re-provisioning
  • No audio or one-way audio
  • Calls not ringing
  • Change opening hours
  • Add a number

The new-user and leaver runbooks should match how you actually onboard and offboard people. Build them alongside MSP customer onboarding for hosted PBX, so first-line staff can complete the common tasks without waiting for a voice engineer, and so they know the exact point at which to stop and escalate.

Team discussing ideas at a whiteboard in an office

Self-hosted or hosted: how does it change support?

Lead with self-hosted if you want control. SessionPBX is a multi-tenant PBX you can run on your own servers: you manage every customer's tenant, and server, hosting and network costs are yours. Self-hosted is available to approved partners only, with annual licences. That is why tiers 1 and 2 sit with you: you operate the platform as well as the help desk.

SessionTalk can also host it, with regional hosting in the UK (London), the US (New York) and Singapore, so the infrastructure is not yours. User support does not change: you still own the customer relationship and the first two tiers. What changes is where a platform-side fault goes, and who looks after the servers. For the hosting choice itself, see self-hosted or hosted PBX for VoIP resellers. How a voice platform sits next to the rest of an MSP practice is covered in MSP tools: adding voice. For the wider path into the market, see starting a VoIP business as an MSP or ITSP.

FAQ

What is tier 1 support in VoIP?

Tier 1 support is the first-line help desk at the MSP or reseller. It covers sign-in, re-inviting a user, device and headset checks, basic network checks, push notifications, and voicemail or forwarding settings for one member. If the runbook fails, or more than one user is affected, the agent escalates to a voice engineer with the details already collected.

What should a VoIP escalation process include?

A VoIP escalation process should name the tiers, the trigger for leaving each one, the owner who takes over, and the details to collect: user, device, time of the problem, number dialled, call direction, and what has already been tried. Write that into the runbook so staff do not escalate a sign-in fault or hold a trunk fault.

How do I fix common VoIP issues?

Start with the tier 1 VoIP troubleshooting checklist: confirm the user, device, time and number, then check sign-in, network, headset, push notifications, forwarding, voicemail and call history, and try an internal call. If audio quality is the complaint, use the call quality guide. If the runbook fails, or several users are hit, escalate to tier 2.

Who supports the phone system when an MSP resells it?

The MSP or reseller supports the phone users for tiers 1 and 2, because they own the customer relationship and manage each tenant. The carrier handles trunk, number routing and porting faults on the SIP trunk you bring. If SessionTalk hosts the platform, platform-side issues go to SessionTalk; if you self-host, those issues stay with your own infrastructure team.

Can SessionTalk host the platform so I only handle user support?

Yes. SessionPBX can be hosted by SessionTalk, with regional hosting in London, New York and Singapore, or self-hosted on your own servers. In both cases you still own tiers 1 and 2, because you own the customer relationship and each customer's tenant. Hosting only changes who looks after the infrastructure when a platform-side fault appears.

What apps do users call from?

Users call from the softphone apps your customers' users run on Windows, macOS, iOS and Android. They sign in after an invite by email, a QR code or a setup link, and you manage extensions, seats and permissions centrally. Voice and video calling, hold and transfer, team chat and presence, voicemail and missed-call notifications are all available in those apps.

Build voice support on a platform you control: become a SessionPBX partner

Build voice support on a platform you control: become a SessionPBX partner. If you want to review the product first, See SessionPBX features.

Related Articles

More from the SessionTalk blog