New plan names, features in new places
Testimonials After Changing Pricing Tiers
Repackaging is quieter than a price rise and does more damage to old proof. A quote that says the Growth plan gave us reporting is now wrong twice if Growth was renamed and reporting moved up a tier. Pricing page proof was picked for columns that no longer exist. This checklist audits every testimonial against the new tier map, retires what misleads, and collects fresh quotes for the tiers that have none.
- Quotes naming retired plans found
- Each testimonial mapped to a new tier
- Fresh asks for tiers with no proof
The problem, solved
How a tier change breaks testimonials you already had
Quotes name a plan we retired
A visitor reads praise for a plan name they cannot find in the table and wonders what else on the page is out of date.
With StoryProof: Export the library as a CSV and search it for every old plan name, including the ones customers shortened or misspelt.
Praise for a feature that moved tiers
A quote under your middle tier celebrates a feature that now sits only in the top one. That is a promise the column no longer keeps.
With StoryProof: Tag each testimonial with the current tier that actually includes what it praises. Tags are on every plan, Free included.
Column proof no longer matches
Widgets were filled for the old columns, so a merged tier shows two quotes about different things and a new tier shows none.
With StoryProof: Filter by the new tier tags and choose the testimonials each pricing widget shows from that filtered list.
Our new tier has no voices
A tier created in the restructure has customers but no testimonials, because nobody has asked them yet.
With StoryProof: From Pro, an automation can start when a contact gets a tag, so tagging customers by their new tier can trigger a request written for that tier.
Fresh submissions mention old names
Customers keep the plan name they signed up under for months, so new testimonials arrive with the retired label in them.
With StoryProof: Every submission waits for approval, so a reviewer can catch an old plan name before it reaches the pricing page.
Flip the switch to see how StoryProof handles each one.
Tier change audit
Bring every testimonial onto the new tier map
Have the old and new plan tables open side by side. Work from the library outwards: find, classify, then place.
Ticks stay in this browser tab. Nothing is saved or sent.
Keep, remap or retire
A rule of thumb for each kind of quote the audit turns up.
In StoryProof
Do the audit in StoryProof
- You will need
- The old and new plan tables
- A tag name for each new tier
- Pro if you want requests to start from a tier tag
- 1
Export and search
Download the space’s testimonials as a CSV and search it for old plan names and moved features.
- 2
Tag by current tier
Add a tier tag to every testimonial you keep, using the new plan names only.
- 3
Rebuild the pricing widgets
Filter by each tier tag and choose that tier’s testimonials for its widget. Take retired quotes out of every widget.
- 4
Ask the empty tiers
Tag the contacts on tiers without proof. A tag can start an automation that sends a request using merge tags for their name.
- 5
Approve with the new names in mind
Nothing new publishes until approved, which is where the reviewer catches a retired plan name.
What happens next: Keep the list of old plan names with your review notes. Customers will use them for longer than you expect.
Before you start
What the audit does not do for you
No editing of the customer’s words
StoryProof does not claim a way to change a testimonial’s text. A quote with an old plan name is kept off pricing placements, or the customer submits it again through the collection link.
Search is outside the app
The export gives you a file to search. StoryProof does not search testimonial text for plan names for you.
Video says what it says
A plan named aloud in a video stays in the video. Edit the file outside StoryProof and upload the new one, or keep it away from the pricing table.
Your billing tool knows the tiers
StoryProof does not read which plan a customer is on. Tier tags on contacts come from you or from an automation you connect.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is a testimonial that names an old plan misleading?
It is confusing on a pricing page, because the visitor cannot buy what it names. Elsewhere it is often fine if the praise is about something every current tier still includes.
Should I ask customers to update their testimonial?
For your best quotes, yes: send them the collection link and ask for a fresh one about their current plan. Do not rewrite their words yourself.
How soon after the change should I ask the new tiers?
Give customers enough time on the new tier to have used what changed. A request in the first week tends to get comments about the migration instead.
What about customers left on a grandfathered plan?
Their testimonials are real but describe a plan nobody can buy. Keep them for general placements, not the pricing table.
Still have a question? Ask the StoryProof team or book a demo.
Line your proof up with the new tiers
Export, tag by current tier and rebuild each pricing widget from tagged testimonials.
Last updated 2026-11-20.