15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Proposal

Free IT Support Proposal Template

An IT support proposal covers the support scope, how tickets get handled, who’s on the team, pricing, and the terms for access, security, and handover.

IT Support Proposal template preview

Language:

en

Category:

Last updated:

October 2026

Share template

Support lands back on admin, the interruptions keep coming, and the buyer needs to know the phones, email, and files won’t go down because someone arrived and changed everything at once. This IT support proposal answers the practical questions up front: who actually picks up, what counts as urgent, and what happens when the same fault keeps coming back. The pages sit under Raleway headings with Roboto body text, with panel green and a tool-finish rose-red used for the key callouts.

The proposal starts with What this covers, then backs the promise up with Meet the team and a detailed Team section so support doesn’t feel like an anonymous inbox. How the service runs and the technical sections spell out triage, remote support, on-site call-outs, Microsoft 365 admin, endpoint management, network support, and joiners and leavers, so the buyer can picture what happens after the first email. The later pages cover what you need for setup, how access and approvals work, and how repeat issues move from “another ticket” into a root-cause fix.

  • What this covers Explains the service outcomes and the kind of gaps the support is meant to cover, including how repeat interruptions get owned until they stop happening.
  • How the service runs Describes the ticket queue, how triage works, when remote support comes first, and when on-site call-outs get booked.
  • Pricing Holds the single plan, including the note that pricing is per month, so you only change the figures before sending.
  • Setup and handover Spells out what access and documentation get shared at the start, how setup is paid, how ongoing billing works, and what happens with on-site call-outs.
  • Access and security Covers secure credential sharing, approvals before changes, how repeat issues get reviewed, and how either side can end the monthly plan.

In Plutio, you replace the numbers in Pricing, send the proposal, and the client signs online in Get started. The same section carries a fee summary, so acceptance and the monthly plan price sit together where the client makes the decision.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in an IT support proposal

PartWhat it covers

What this covers

Frames what the service takes ownership of day to day, including how urgent work gets treated and how repeat faults move beyond ticket-by-ticket fixes.

A bit about us

Gives the background story the buyer checks for, including when the team tends to get called in and how the handover avoids a reset.

Meet the team

States that support has named owners across tickets, Microsoft 365, and on-site work, so requests don’t drift between inboxes.

Team

Lists the roles and responsibilities for service desk, Microsoft 365 admin, field support, and the day-to-day client contact.

Recent work

Introduces the kind of support jobs the buyer can expect to see handled, with examples that focus on owning the queue and reducing repeat interruptions.

Portfolio

Describes recent service desk, Microsoft 365, and on-site network work, so the buyer can map the service to familiar faults and outcomes.

How the service runs

Explains how tickets get raised, how priorities get adjusted, and how work moves from triage to remote fixes to on-site time when needed.

Ticket handling and triage

Defines what gets logged and tracked each working day, then covers remote user support and Microsoft 365 support in practical terms.

Endpoint management (Intune/RMM)

Covers endpoint monitoring and onboarding, then describes how network support and joiners and leavers get handled and confirmed back.

Pricing

Puts the monthly plan in a priced table, so you swap in your own figures for the Standard option before you send it.

Get started

Holds the acceptance step with a signature and fee summary, then answers the response-time question and what counts as urgent before the client signs.

Setup and handover

Covers setup scoping and scheduling, payment timing, how support requests should be logged, and how on-site call-outs are treated under the plan.

Access and security

Explains secure access handling and approvals, how repeat issues get reviewed into root-cause proposals, and what ending the plan looks like.

Who it is for

IT support and managed services providers quoting monthly helpdesk and support cover for small and mid-sized companies that need a clear handover and response expectations.

The proposal in full

What this covers

Your users get a single place to ask for help, fast first responses, and fewer repeat interruptions because the same problem gets owned until it stops happening.

You’re getting cover because support has landed back on admin, and Microsoft 365 changes, new starters, or a move are making the gaps show. You’ll know who picks up, what “urgent” means, and what happens next.

Helpdesk and support starts with triage, so the first person to read a ticket can either fix it or route it with the right detail. We handle day to day user issues remotely, and we come on-site for desk-side faults, Wi‑Fi, printers, and moves. When something keeps coming back, we stop treating it as “another ticket” and remove the cause.

A bit about us

We’re Bessemer Support, a Sheffield-based team that does helpdesk and support for small and mid-sized businesses that need steady cover. Most clients come to us right after an “IT person” leaves, or when support gets dropped onto ops again and small faults start eating hours. We step in without a reset.

We learn what you’ve already got, then we keep it running while we tidy the parts that keep failing.

paragraphs 2? nope

Meet the team

You’ll have named people looking after tickets, Microsoft 365 admin, and on-site call-outs, so requests don’t drift between inboxes.

Team

Gareth Wilson, Service desk lead. Gareth runs the service desk, triages new tickets, and keeps the queue moving so urgent issues get picked up first, every day.

Aisha Khan, Microsoft 365 engineer. Aisha handles Microsoft 365 admin, mailbox and SharePoint access, and the changes that usually trigger lockouts and permission problems.

Tom Sykes, Field support engineer. Tom takes on-site call-outs, desk-side fixes, Wi‑Fi and printer faults, and the hands-on parts of moves and setup days.

Hannah Price, Client services manager. Hannah is your day-to-day contact for priorities, onboarding dates, and making sure recurring issues get a proper root-cause slot.

Recent work

Here are three recent support jobs that show the kind of interruptions we take off your desk, and what changes when someone owns the queue.

Portfolio

Service desk takeover. Took over an overloaded ticket queue, set clear priorities, and moved repeat issues into tracked fixes. First responses stabilised within the first week and the backlog stopped growing.

Microsoft 365 tidy-up. Fixed recurring mailbox access and SharePoint permission issues by cleaning up groups and documenting who owns what. New starters started getting access on day one instead of via follow-up tickets.

On-site network fixes. Resolved dropouts on Wi‑Fi and desk ports by tracing cabling, correcting switch port settings, and replacing a failing access point. Support calls about “internet down” dropped after the changes.

“Tickets stopped hanging around, and the same problems finally stopped coming back.”

Operations manager, a busy office and workshop

How the service runs

Helpdesk and support runs through a single ticket queue, with remote fixes first and on-site call-outs booked when hands on time will be faster. You can raise tickets by email or phone, and you can speak to Hannah when priorities need adjusting.

1. Triage and first reply Every day We log and categorise each request, confirm impact, and reply with either a fix or the next question we need answered. Urgent issues go straight to the top of the queue and get owned until service is back. 2. Remote support Every day We handle most user and device issues remotely, including Windows and macOS support, Microsoft 365 queries, and access problems. We use your approved tools where possible, and we explain any new agent we need before we install it. 3. On-site call-outs As needed When a fix needs hands on work, we book Tom in for desk-side support, printers, Wi‑Fi, switches, and office moves. We confirm what will be touched before we start, and we leave a short note on what changed so you are not guessing later. 4. Repeat-issue fixes Each month We review the issues that keep resurfacing, pick the ones costing the most time, and schedule a root-cause fix. You get a clear description of what we changed and what to watch for, so the fix sticks and support demand drops.

Ticket handling and triage

Logged, prioritised, and assigned every working day, with clear notes on what we tried, what worked, and what we need from you next.

REMOTE USER AND DEVICE SUPPORT

Daily remote support for common Windows and macOS issues, software hiccups, password and sign-in problems, and day to day how-do-I questions.

MICROSOFT 365 SUPPORT

Ongoing Microsoft 365 support and tenant administration, including mailbox changes, SharePoint access, group management, and basic security settings you approve.

Endpoint management (Intune/RMM)

Continuous device monitoring and management where in place, plus onboarding of new endpoints so updates, encryption, and key settings stay consistent.

NETWORK SUPPORT

As needed support for switches, Wi‑Fi, and firewalls, including fault finding, configuration checks, and on-site testing when remote checks are not enough.

JOINERS AND LEAVERS

For each starter or leaver, we handle accounts, kit setup, and access changes, and we confirm completion back to you so nothing is left half done.

Pricing

Pick the plan that matches how often you want on-site cover; all plans include daily ticket triage, remote support, and monthly work on repeat issues. Prices are per month.

Priced items

Get started

Sign to start helpdesk and support, and we’ll set up the queue, access, and the first round of user and device checks.

1. Sign this proposal in the box beside this section. 2. Send us your Microsoft 365 admin contact details and any current support logins. 3. Pick a start date for the service desk, then we’ll begin taking tickets.

IF SOMEONE CAN’T WORK, HOW FAST DO YOU RESPOND AND WHAT COUNTS AS URGENT?

If work is blocked, that’s urgent. We reply first and sort the ticket so it does not sit unseen, then we work the fix through until the user is back. If email, phones, or shared files are down for multiple people, it goes straight to the top of the queue.

DO WE GET ON-SITE SUPPORT IN SHEFFIELD, AND IS IT CAPPED?

Yes, we provide on-site support call-outs in Sheffield when the job needs desk-side time, kit swaps, or network and printer work. We agree the call-out plan and any caps in the pricing section, so you know what is included before you start.

WILL YOU WORK WITH WHAT WE’VE ALREADY GOT, OR ARE YOU GOING TO RIP IT OUT?

We work with what you already have. We start by mapping what is in place, who relies on it, and what breaks most often. If a change is worth doing, we explain the risk, the downtime window, and the rollback plan before anything gets touched.

WHO’S OUR DAY-TO-DAY CONTACT WHEN TICKETS ARE PILING UP?

Hannah is your day-to-day contact for priorities, onboarding dates, and what needs escalation. Gareth runs the service desk itself, so the ticket queue has an owner and you are not chasing different people for updates.

Signature

Fee summary

Setup and handover

Any setup work is scoped with you first, then scheduled around business hours where we can. We ask for admin access and existing documentation at the start so tickets do not stall.

Payment. Setup is paid 25% to start it and 75% when it is complete. Ongoing helpdesk and support is invoiced at the start of each month. Every invoice is payable within 7 days.

Support requests. Please log requests by email or your agreed ticket method so we can track owner, priority, and updates. If something is urgent, mark it urgent and include who is blocked and what stopped.

On-site call-outs. Where your plan includes on-site call-outs, unused call-outs do not roll over. Extra on-site visits are booked through Hannah and billed at our current call-out rate, agreed with you before travel.

Access and security

You will share passwords, MFA, and door codes through your password manager or a secure method you choose. We do not store login details in the proposal, tickets, or emails beyond what is needed to do the job.

Changes and approvals. We work with what you already have. If a change is worth doing, we will explain the risk, the downtime window, and the rollback plan before we touch anything, and we will wait for your approval.

Repeat issues. Each month we review repeat incidents and the top time-wasters, then propose a root-cause fix. If the fix is larger than routine helpdesk and support, we will quote it and only proceed once approved.

Ending the plan. Either side can end the monthly plan with notice, and we will confirm the notice period with you in writing when you start. We will provide a handover of admin access and key notes at the end.

Questions about this proposal template

What should an IT support proposal include?

An IT support proposal usually covers the support scope, how tickets are logged and prioritised, who provides the service, and what the monthly pricing includes. This one also includes setup and handover, plus access, security, and approvals so change doesn’t happen without sign-off.

What counts as urgent in IT support?

Urgent work usually means someone can’t work, or a shared service like email, phones, or shared files is down for multiple people. This proposal defines urgent in those terms and explains that urgent tickets go to the top of the queue and get owned through to recovery.

Who handles tickets day to day on a helpdesk?

Day-to-day handling normally has a service desk lead triaging and assigning tickets, with specialists covering areas like Microsoft 365 and on-site call-outs. This proposal names the people and what each one looks after so responsibility doesn’t feel vague.

Will an IT support provider work with existing systems or replace everything?

A managed service can support what’s already in place and only propose changes when a change is worth doing. This proposal states that changes come with a risk explanation, a downtime window, a rollback plan, and approval before anything gets touched.

Does managed IT support include on-site call-outs?

Some plans include on-site time and some keep on-site visits as booked extras, depending on how the service is priced. This proposal explains that plans differ by how often on-site cover is included and how extra visits are handled.

How are setup and ongoing IT support payments usually handled?

Setup is often paid in stages, and ongoing support is commonly billed monthly in advance with a defined payment term. This proposal specifies a split for setup payments and says the monthly helpdesk and support is invoiced at the start of each month with a 7-day due date.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away