MSP Proposal Template for Hosted Voice (Free Outline)

Tom Reed · Updated 19 November 2026
A good MSP proposal template for hosted voice has eight sections: summary, current setup, proposed solution, scope of work, cutover plan, apps and devices, support, and commercials with next steps. Keep it to what the customer agreed in discovery and leave the legal detail to the contract. If you run SessionPBX, a multi-tenant PBX you can host on your own servers or have SessionTalk host, you can describe the platform, tenant setup and apps in your own name.
This guide is for MSPs, ITSPs, VoIP providers and IT resellers who need to put a hosted voice deal in writing. It works as a managed services proposal outline and an IT proposal template you can reuse for every voice customer, and it ends with a checklist to run before you hit send.
What should an MSP proposal for hosted voice include?
An MSP proposal sells the project and summarises it. It is not the sales conversation and it is not the contract. If you still need to qualify the customer and run the demo, start with our MSP sales playbook for hosted voice, then come back here once discovery is done and you are writing the document.
Use these eight sections, in this order, so the decision-maker can find what they care about quickly:
| Section | What to write | Tip |
|---|---|---|
| Summary | Goal, users, sites, go-live month | One paragraph the decision-maker reads |
| Current setup | Phone lines, PBX, numbers, contract end dates, pain points | Use their words from discovery |
| Proposed solution | Hosted PBX, call flows, features, where it is hosted | Only features you will deliver |
| Scope of work | Extensions, trunk, call flows, apps, training, and an out-of-scope list | Mirrors the statement of work in the contract |
| Cutover plan | Dates, parallel running, user invites, rollback | Name an owner for every step |
| Apps and devices | Softphones per platform, headsets, any desk phones | Link the app download pages in the document |
| Support | Tiers, contact routes, hours you offer | No promises you cannot back |
| Commercials and next steps | Your own pricing, term, sign-off, kick-off date | Keep legal terms in the contract |

How do you write the summary and current-setup sections?
Start the summary with the customer's problem in the customer's own words, not with a feature list. A sentence such as "calls are missed when reception is busy and staff cannot take calls away from the office" tells the buyer you listened. Then state the goal, the number of users and sites, and the month you expect to go live.
The current-setup section proves you understand what you are replacing. Record the existing phone system or lines, the numbers in use, when each contract ends, and what is not working today. Keep it factual and short. This section also protects you later, because it shows what the customer had at the start of the project.
What goes in the proposed solution?
Describe the hosted phone system in terms of outcomes the customer asked for. For a typical office that means call flows that greet callers and send them to the right team, ring groups, call queues, an auto-attendant and IVR, business-hours routing, voicemail and call recording where the plan includes it.
Stay inside what the platform really offers. The call flow designer, queues, recording and supervision belong to the Teams Business plan, which is a SessionPBX plan name and has nothing to do with Microsoft Teams. Check the features on the hosted PBX page before you write them down, and only promise features you will switch on.
Also say where the system runs. You can host SessionPBX on your own servers, which suits MSPs that want control of the platform, or you can have SessionTalk host it in the UK (London), the US (New York) or Singapore. If you are weighing the two, read how self-hosted PBX works for VoIP resellers and how multi-tenant PBX lets one platform serve many customers. If you package hosted voice into tiers, our guide to packaging hosted PBX for resellers helps you keep the proposal simple.
How do you write the scope of work (statement of work)?
The scope of work is the part that stops arguments later. Many buyers search for a statement of work template when they really need a clear list of deliverables, so write it as one. List what you will set up and what you will not.
A scope of work for hosted voice usually covers:
- Users and extensions you will create
- The SIP trunk: SessionPBX is bring-your-own-trunk, so say which carrier relationship the customer holds, and that any SIP-compliant carrier works
- Call flow design, including greetings, menus and business-hours routing
- App rollout to each user, and how they are invited
- Training for administrators and end users
- A clear out-of-scope list, for example cabling, network changes and hardware you are not supplying
SessionTalk does not supply the trunk, so be explicit that the carrier bills for numbers and calls. The proposal summarises the scope and the contract binds it, so make sure both say the same thing. Our MSP voice contract checklist shows which clauses to carry across.
What should the cutover plan cover?
The cutover plan tells the customer what happens on the days that matter. Set out the dates, any period when the old and new systems run side by side, how users are invited, who is on call during go-live, and what you will do if something has to be rolled back. Give every step a named owner.
For the invitations, SessionPBX lets you invite people by email, set up mobile apps with a QR code and send a setup link for desktop apps, so users can get connected without typing settings. Your customer onboarding guide for hosted PBX goes deeper on the steps after signature. Before cutover day, run through the network readiness checklist for a cloud PBX so the customer's network is not a surprise.

Which apps and devices will users run?
Say what each person will use to make and take calls. SessionTalk's softphone apps run on Windows, macOS, iOS and Android, so most customers need no new hardware beyond headsets. List any desk phones only if they are in scope. Link to the softphone apps your customers' users run so the buyer can see what staff will install.
If you want the customer's staff to see your name, SessionPBX partners can put their own logo and in-app name on the softphones. Mention it as an app branding option, not as a separate product. If you are worried about how apps reach users safely, our guide to provisioning softphones securely covers the process.
How do you describe support without overpromising?
Say who handles what. Typically your help desk takes user issues, your voice engineer takes tenant and call-flow changes, and the carrier handles anything on its own network. Explain how a customer raises an issue and the hours you actually offer, and nothing beyond that.
Do not copy service promises from another document. If you cannot back a commitment, leave it out and describe your process instead. Our guide to the VoIP support model for MSPs lays out tiers and escalation you can summarise in this section.
How do you present pricing and next steps?
Pricing is yours to set, so use your own price list. List each user or extension line the way you normally quote, state the term, and explain what triggers billing, such as go-live or signature. Our guide to how to set your hosted voice pricing walks through how to build that price in the first place. Keep the pricing section short and put legal terms in the contract.
Finish with the next steps: who signs, by when, and the kick-off date. A buyer who knows exactly what happens after signature is more likely to sign.
Checklist before you send
- The customer's goal is stated in their words
- User count, sites and numbers match your discovery notes
- Every feature listed is on the plan you are proposing
- Cutover dates are realistic and agreed with the carrier
- Out-of-scope items are listed
- The support section matches what your help desk really offers
- Pricing matches your price list, and the contract is attached or referenced
FAQ
What is an MSP proposal template?
An MSP proposal template is a reusable outline for winning a managed services deal. For hosted voice it has eight sections: summary, current setup, proposed solution, scope of work, cutover plan, apps and devices, support, and commercials with next steps. You fill it in for each customer using your discovery notes.
What is the difference between a proposal and a statement of work?
The proposal sells and summarises the project for the decision-maker. The statement of work defines the deliverables and what is out of scope. The contract is what binds both parties. Keep the three consistent, and let the proposal point to the statement of work rather than repeating every detail.
How long should a hosted voice proposal be?
Short enough that the decision-maker reads all of it. A few pages plus the scope table is a sensible shape. If a section grows long, move the detail into the statement of work or an appendix, and keep the main document focused on the customer's goal and next steps.
Should the proposal include pricing?
Yes. Include your own pricing and term in the commercials section so the buyer can decide. Keep the legal terms, such as notice periods and liability, in the contract. If you need help setting your price, build it before you write the proposal, not while you are writing it.
Can I propose a platform I host myself?
Yes. SessionPBX can run multi-tenant on your own servers, which is available to approved partners, or SessionTalk can host it for you. In the proposal, say clearly which option you have chosen and who looks after the servers, hosting and network, so the customer knows who to call.
What apps do users get?
Users run SessionTalk's softphone apps on Windows, macOS, iOS and Android. You invite them by email, set up mobile apps with a QR code and send desktop users a setup link. List the platforms in the proposal and link to the apps so the customer can see what staff will install.
Put the proposal on a platform you control: become a SessionPBX partner
Have a platform to propose? Become a SessionPBX partner and put hosted voice in front of your customers, with the platform, tenant setup and apps described in your own name.


