For managed service providers and IT support firms
Managed IT Service Provider Client Testimonials
When an MSP does its job well, nothing happens. Clients only think about IT when it breaks, so the natural moments to ask are the ones you would rather avoid. Enter the contract start date and get a plan that asks when the value is visible: after onboarding, after a review meeting, in a quiet stretch, and well before renewal.
- Asks timed to reviews, not to outages
- Office manager and owner asked about different things
- Kept clear of the renewal negotiation
The problem, solved
Why MSPs struggle for proof, and how StoryProof helps
Most MSPs have loyal clients and a website with no client voices on it. These are the usual reasons.
Situation 1 of 5
Clients only notice us when things break
A month without problems feels like nothing happened, so there is no prompt to say anything good.
How StoryProof solves it
Email the request on dates you choose, such as the week after a quarterly review, from contacts you have added.
Situation 2 of 5
We asked right after an outage
A request that lands during an incident, or the day after, gets either silence or a complaint.
How StoryProof solves it
On a plan with automations, a review of 2 stars or fewer alerts your team and sends the client an apology email, so a bad moment gets a human reply.
Situation 3 of 5
The owner signs, the office manager knows
The person who could describe the help desk is not the person a prospect’s owner wants to hear from.
How StoryProof solves it
Send each a request with the same link; they can record a short video, leave a voice note or type.
Situation 4 of 5
Busy clients never get round to it
Small business owners mean to reply and then do not.
How StoryProof solves it
On a plan with automations, two reminders follow and stop when the client responds.
Situation 5 of 5
A dental practice wants to hear from dentists
Prospects look for an MSP that knows their sector and their software, not general praise.
How StoryProof solves it
Tag testimonials by client sector and service, and choose which approved ones appear on each service page.
Contract year planner
Plan the first year of asks from the contract start
Enter the date the contract began. The plan avoids onboarding turbulence, uses review meetings as the cue, and keeps the testimonial ask well away from renewal pricing.
Day +45
Onboarding settled
Once migration and device rollout are done, ask the office manager how the switch from the old provider went.
Day +95
After the first quarterly review
You have just shown the ticket trends and patching status. Ask the owner what it is like to not think about IT.
Day +180
Quiet month check
If no major incident has happened this quarter, ask one or two staff users what day to day support is like.
Day +270
Third review: video invite
For your happiest client, invite a short recorded testimonial, while renewal is still months away.
Day +300
Stop asking
Renewal talks start soon. Do not send testimonial requests in the run up to the price conversation.
Day +395
After renewal
A client who renewed has made a decision. Ask why they stayed, in a sentence or two.
Dates are calculated in your browser. Nothing is saved or sent.
Incident handled well: ask later, not now
Asking during the incident
- Request lands while the server is down
- Client replies with frustration, or not at all
- Quote, if any, is about the outage
Asking two weeks after it is resolved
- Post incident report sent and acknowledged
- Client remembers how fast you responded
- Quote is about how the team handled pressure
In StoryProof
Run it in StoryProof
- You will need
- Contract start dates for each client
- A named owner and office manager at each client
- 1
Add client contacts
Owner, office manager and a couple of staff users, grouped by client.
- 2
Send requests on the plan dates
Email the collection link after each review meeting. On a plan with automations, reminders follow.
- 3
Approve and remove sensitive detail
Read each answer before approval. Take out anything that names systems, vendors or security setups the client would not want public, with their agreement.
- 4
Tag and show by sector
Tag by sector and service, then pick testimonials for each service page.
What happens next: Add a line to your quarterly review template: “ask for a testimonial if the quarter was quiet”.
Before you start
What StoryProof does not do
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
No PSA or ticketing integration
StoryProof does not read tickets, contract dates or review meetings from your PSA. You decide when to send.
- 02
Security details stay out
StoryProof does not screen answers for sensitive detail. Read every testimonial for system names and setup details before approving it.
- 03
Uptime figures are the client’s to state
If a quote mentions a figure, it should be one the client wrote and agreed. Do not add numbers from your monitoring.
- 04
Email requests only
Requests go by email or a link you share. If a client prefers a phone call, ask by phone and send the link afterwards.
FAQ
Questions people ask
Short answers to what usually comes up next.
When should an MSP ask clients for testimonials?
After a quarterly review that shows how quiet things have been, after an incident has been resolved and reported, and after renewal. Avoid outages and the weeks before renewal pricing.
Who at the client should give the testimonial?
The owner or director for why they chose and stay with you; the office manager or staff for what support is like day to day.
Are case studies better than testimonials for MSPs?
They do different jobs. A short testimonial works on service pages; a case study suits a sales conversation. A good testimonial is often where a case study starts.
Can a client mention the security tools we use for them?
Usually better not. Naming a client’s security setup can help an attacker. Keep quotes to how the service feels, not what is installed.
Still have a question? Ask the StoryProof team or book a demo.
Turn quiet months into proof
Set up a form and send it after your next quarterly review. No credit card needed to start.
Last updated 2026-11-07.