Many SaaS companies sell support in tiers: a standard plan included with every account, and one or two paid plans with faster response, a named contact or phone access.
The page that compares those plans is an unusual sales page. The visitor already uses the product. Often they are there because something went wrong recently, or because their manager asked "what happens if this breaks during month-end?" They are not deciding whether the product is good. They are deciding whether paying extra for help is worth it, before they actually need that help.
That makes testimonials tricky. A quote praising the product does nothing here. A quote promising "they always answer in five minutes" creates a commitment your contract may not make. This guide covers where customer quotes help on a support plans page and what each one should show.
Understand what the buyer is really comparing
A premium support page is usually read by one of three people:
- The admin who got stuck. They waited for an answer during an outage or a migration and want to avoid that again.
- The budget owner. Finance or a department head who needs a reason to add a recurring cost.
- The procurement or IT reviewer. They compare response targets, coverage hours and escalation paths against internal requirements.
The admin wants reassurance that help will be different, not just labeled differently. The budget owner wants to know what a slow answer actually cost other companies. The reviewer mostly wants facts in a table, and quotes should stay out of their way.
Place each testimonial so it answers one of these people, and don't put quotes inside the comparison table itself.
Slot 1: under the headline, describing a real incident
The top of the page should explain why premium support exists. One short quote from a customer who used it during a stressful moment does that better than a list of benefits:
"Our invoice sync stopped on the last day of the quarter. We had a support engineer on a call within the hour, and the fix was in before our close." — Finance Systems Lead, 300-person manufacturing company
Why this works:
- It names a specific situation. Quarter-end, invoice sync and a deadline are easy for the budget owner to picture.
- It describes what happened, not what always happens. "Within the hour" is one customer's experience, which is different from a published response target.
- It connects support to a business outcome. The close finished on time.
Before you publish a quote like this, check that the timeframe is consistent with the plan's stated targets. If your premium tier promises a four-hour response, a quote about a ten-minute answer sets expectations your team can't meet every time.
Slot 2: beside the plan that includes a named contact
Tiers with a dedicated support engineer or technical account manager are hard to explain with bullet points. "Named contact" sounds nice but doesn't tell the buyer what changes day to day.
Place a quote beside that column (not inside the table cells) that describes the difference in practice:
"We stopped re-explaining our setup every time we opened a ticket. Our contact already knew which integrations we had and which ones we'd customized." — IT Director, multi-location healthcare group
This quote shows the value of context, which is the real reason people pay for a named contact. Avoid quotes that praise one support person by name. People change teams, and a quote tied to a specific name becomes outdated quickly.
For guidance on keeping comparison layouts readable, see where to place testimonials on a pricing page. The same rule applies here: tables carry the facts, and quotes sit next to them.
Slot 3: in the section about coverage hours or time zones
Many premium plans extend coverage to weekends, 24/7 or additional regions. This is often the deciding feature for companies with teams in several time zones, and the most doubted one.
A useful quote here is about timing and location:
"Our Singapore team used to wait until the US morning for help. On the extended plan they get answers during their own working day." — Global Operations Manager, logistics software company
Keep it specific to the coverage change. Don't combine coverage claims with speed claims in the same quote ("24/7 and they answer instantly"). That turns one real improvement into two promises.
Slot 4: near the escalation or incident process description
If your page explains how critical issues are escalated, the IT reviewer will read that section closely. This is the one place on the page where a quote should support process, not emotion:
"During a login outage we got status updates every thirty minutes, even when there wasn't a fix yet. That let us tell our own staff what to expect." — Systems Administrator, regional school district
This works because it describes communication, which customers value during incidents, rather than claiming the outage was solved quickly. It also matches what a reviewer is checking: whether the process described on the page actually happens.
If you publish uptime or incident history, link to it here instead of adding a quote about reliability. The approach for that page is covered in where to place testimonials on a status page or uptime page.
Slot 5: beside the "Talk to us about upgrading" button
Most support upgrades go through an account manager rather than a self-serve checkout. The last hesitation before contacting sales is usually "Will this turn into a long sales process?"
One short quote can address that:
"The upgrade took one call and a signed order form. Our first premium ticket was handled the same week." — Operations Director, 80-person architecture firm
Keep it to one quote and don't push the button below the fold on mobile. More on this position in where to place testimonials near the call to action.
What should not appear in a support testimonial
Support pages sit very close to contract terms. Some things are risky to put inside customer quotation marks:
Guaranteed response or resolution times. Response targets belong in the plan table and the service agreement, with the exact definitions. A quote saying "they fix everything in an hour" can be read as a promise.
Comparisons with the standard plan that insult it. "Before premium, support was useless" tells every standard-plan customer that you give them poor service. Describe what improved without attacking the other tier.
Details from real incidents the customer didn't approve. A support ticket may include system names, error details or internal problems. Get explicit approval for the final wording, and remove anything the customer wouldn't want public.
Quotes from customers who have since downgraded. If the customer who praised premium support no longer pays for it, retire the quote.
A quick check for each support quote
Before publishing, ask:
- Does it describe a real situation, such as an outage, migration, deadline or time zone problem?
- Is any timeframe in the quote consistent with the plan's published targets?
- Does it avoid naming individual support staff?
- Is the customer still on the plan the quote appears next to?
- Did the customer approve the exact wording and attribution?
A related question is how to show the tier and response context on the testimonial card itself. That's covered in testimonial cards with support tier and SLA response time attribution.
Where to find support-plan quotes
Your support team already has the source material:
- Post-incident follow-ups. After a critical ticket is closed, the account manager can ask what the fast response made possible for the customer's team.
- Renewal conversations. When a customer renews a premium plan, ask why. Their reason for paying again is usually the most honest quote you'll get.
- Satisfaction survey comments. Look for comments that mention a specific event rather than general praise, then ask permission to use them.
Always confirm the customer's current plan before publishing, and let them choose whether to show their name, role or only a company description.
A quick audit
Open your support plans page and check:
- Does the top of the page include one quote about a real incident?
- Is there a quote explaining what a named contact changes in practice?
- If you sell extended coverage, is there a quote about time zones or weekends?
- Does the escalation section include a quote about communication, not speed promises?
- Are all response times stated in the table, not only in quotes?
People pay for premium support to reduce the cost of a bad day. Each testimonial on the page should show one customer's bad day and what the support plan changed about it.