Mixed feedback in one submission
Testimonials That Include a Complaint
Two paragraphs of praise, then one line about the invoice that went out wrong. Marketing wants to publish it, support wants to fix it, and nobody wants to cut the line out and pretend it was never written. Decide as a team, once, with the same questions every time.
- Publish whole, fix first, re-ask or hold
- Who on the team acts next
- No silent trimming of the criticism
The problem, solved
Where mixed testimonials get stuck, and how StoryProof keeps them moving
A mixed submission is not a bad review. It is a good review with a job attached, and the job usually belongs to someone other than the person moderating.
Someone wants to quietly cut the complaint
Publishing only the praise changes what the customer said. If they see it, the trust you were trying to show is gone.
With StoryProof: Nothing is public until you approve it, so the testimonial can wait in the queue while you ask the author whether a shorter version is fine with them.
Four stars, so it went live automatically
A rating can look positive while the text carries a sharp complaint, and an approval rule only sees the stars.
With StoryProof: From Pro, auto-approve handles 4 and 5 star testimonials with text. If your customers mix praise and complaints, leave that rule off and read each one.
Support never hears about the complaint
Marketing reads the testimonial for the quote and moves on. The broken invoice or slow reply it mentions is never fixed.
With StoryProof: Tag mixed submissions with a label your support lead filters on every week, so the complaint lands with the person who can act on it.
It is fixed now, the quote is not
The issue was resolved a month ago, but the testimonial still describes it as a live problem.
With StoryProof: Send the customer the collection link again and invite a fresh version. They can write, record a video or leave an audio note, with no app to install.
Low score with a kind sentence attached
Sometimes it is the other way round: mostly unhappy, with one generous line. That is a support case first.
With StoryProof: From Pro, a review of 2 stars or fewer can alert your team and send the customer a personal apology email.
Flip the switch to see how StoryProof handles each one.
Decision helper
Decide what happens to this testimonial
Answer for the one submission in front of you. Moderation and support should agree on the answers, not take turns overruling each other.
Scoring runs in your browser from the rules on this page. Your answers are not stored.
One mixed testimonial, three honest handlings
Illustrative sample, not a real customer
Submission: “Setup took one afternoon and the team answered every question the same day. The first invoice charged us twice, which took two weeks to sort out. Still, I would recommend them to anyone in our position.”
Publish whole: approve it as written. The billing line is true, it was fixed, and it makes the recommendation sound earned.
Fix and re-ask: support confirms the refund, then the account manager sends the collection link with a note that a fresh version is welcome if they would like to update it.
Shorter version: the customer is asked whether the first and last sentences may be used alone. Only a written yes from them lets the shorter version go up.
In StoryProof
A weekly routine for mixed submissions
- You will need
- A StoryProof space where both marketing and support have a seat
- One agreed tag for mixed testimonials
- 1
Keep approval manual for mixed feedback
If you use auto-approve from Pro, remember it passes any 4 or 5 star testimonial with text. Teams that often receive mixed feedback should review by hand.
- 2
Tag and leave it in the queue
When a submission holds a complaint, add the mixed tag and do not approve it yet. Unapproved testimonials stay private.
- 3
Support reviews the tag weekly
Give your support lead a seat in the same space. They filter by the tag, deal with the complaint and note the outcome on the testimonial’s tags.
- 4
Run the decision helper together
With the complaint dealt with, answer the five questions above and act on the result: approve, re-ask, request permission for a shorter version, or keep holding.
- 5
Place it where the context helps
A testimonial that praises how you handled a problem belongs near support or onboarding content. Choose the widgets it appears in.
What happens next: Once a month, count how many mixed submissions mention the same issue. Three customers naming the same problem is product feedback, not a moderation question.
Before you start
Where StoryProof stops
You cannot edit the words in StoryProof
There is no claim here that testimonial text can be changed in the app. A shorter or updated version comes from the customer resubmitting through the collection link.
It does not read the text for complaints
Nothing flags a complaint inside a positive testimonial. The tag is applied by a person who read it.
No public reply under a testimonial
StoryProof shows the testimonial. If you want to explain what you fixed, do it on your own page or directly with the customer.
Auto-approve looks at stars and text only
The rule approves 4 and 5 star testimonials that include text, whatever the text says. Mixed feedback with a high rating passes it.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is it misleading to publish only the positive part?
It can be, if the part you removed changes the overall impression. Ask the author first and publish the shorter version only with their agreement, or publish the whole thing.
Does a testimonial with a complaint hurt conversions?
We have no data to quote either way. What it does is make the praise around it read as honest, which is why a minor, resolved complaint is often worth leaving in.
Who should decide, marketing or support?
Both. Support decides whether the complaint is resolved; marketing decides how the testimonial is used. The decision helper gives them a shared set of questions.
Should we reply to the customer before publishing?
Yes, whenever the complaint is about something you can fix. A customer who sees their testimonial go up while their problem is still open will not feel heard.
What if the customer says “use whatever you like”?
Take them at their word for the full text. For a shorter version, still confirm the exact words you plan to publish so there is no surprise later.
Still have a question? Ask the StoryProof team or book a demo.
Moderate mixed feedback as a team
Keep every submission private until you decide, tag the ones support needs to see, and approve when it is right. No credit card needed to start.
Last updated 2026-11-11.