Great story, hard to hear
Video Testimonials with Poor Audio Quality
The customer said exactly the right things, and the recording makes them hard to follow: a fridge humming, a room that echoes, a voice that drops away mid sentence. Before you spend an evening in an editor, decide what this clip is good for. Answer four questions below to choose between publishing it, using it in writing, or asking again.
- Four questions about the clip you already have
- A clear verdict with a runner up
- Re-ask wording that does not blame the customer
Clip verdict
Is this clip still usable?
Play the clip once on a phone speaker at normal volume, the way a visitor would, then answer honestly. The helper adds up the answers and shows the strongest option with a runner up.
Your answers are scored in this page only. Nothing is stored or sent.
The problem, solved
When the sound lets a good testimonial down
Each of these is a common way a clip with poor audio stalls, and what StoryProof does about it.
- Problem 1
Someone almost published it before listening
A clip looks fine as a thumbnail. Nobody notices the hum until a prospect presses play on the pricing page.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so a clip can sit in the queue while someone listens on a phone first.
- Problem 2
Their face adds nothing, but their voice is good
Asking for another video is a big request. Asking someone to talk for thirty seconds somewhere quiet is a small one.
How StoryProof solves it
The same collection link takes an audio note as well as video or text, and audio notes play in widgets and on the Wall of Love.
- Problem 3
The words are great, the recording is not
Copying a quote out of a clip yourself puts your hearing of it in their mouth, and nobody can check it.
How StoryProof solves it
Send them the same link and ask them to write the lines themselves. Their written testimonial arrives in the queue next to the video.
- Problem 4
They recorded a better take on their own
Some customers re-record in another app and email you the file, which then lives in an inbox nobody searches.
How StoryProof solves it
Video files you already have can be uploaded directly into StoryProof, so the better take sits with the rest of your testimonials.
- Problem 5
We lost track of which clips need a re-ask
Three clips with poor sound, one re-ask sent, two forgotten. A month later nobody remembers which customer is waiting.
How StoryProof solves it
Tags are on every plan. Tag a clip "sound re-ask sent" and keep it unapproved until the new take arrives.
- Problem 6
A usable clip sits next to a crisp one
A slightly noisy clip next to a studio quality one makes the noise stand out more than it would alone.
How StoryProof solves it
You choose which approved testimonials appear in each widget, so the rougher clip can go where it stands alone.
Sound faults, and how far each can be saved
In StoryProof
Handle a poor audio clip in StoryProof
- 1
Keep it unapproved while you judge it
Leave the clip in the queue. It stays off your site until you approve it, however long the decision takes.
- 2
Run the verdict and tag the outcome
Answer the four questions above, then tag the clip with what you decided, such as "sound ok" or "sound re-ask sent".
- 3
Send the re-ask with your link
Email the customer your collection link. They can record a new video, leave an audio note or write the lines, whichever suits them.
- 4
Bring in any file they send separately
If the new take arrives as an attachment, upload the video file directly so it joins the original.
- 5
Approve the best version and place it
Approve whichever version a visitor can follow, then choose it for the widget where it belongs.
What happens next: Once a new take is approved, decide whether the first clip is still needed. If not, leave it unapproved so it never shows by mistake.
Before you start
What this page does not do
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
No sound repair inside StoryProof
StoryProof does not clean up, normalise or re-mix audio. Any repair happens in your own editor before you upload a file.
- 02
No text version is made for you
StoryProof does not turn speech into text. A written version has to come from the customer, which also keeps the words theirs.
- 03
Repair has a ceiling
Distortion and heavy echo damage the recording itself. Software can make them less bad, rarely good, and over-processed voices sound strange.
- 04
One re-ask, then let it go
If a customer does not answer the second request, thank them for the first clip and move on. Repeated asks cost more goodwill than one testimonial is worth.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is it rude to ask a customer to record again?
Not if you thank them first and make the problem the room, not them. Offer an easier format, such as an audio note or a few written lines, so the second ask is smaller than the first.
Can I clean up the sound myself and publish that?
Reducing a hum or levelling the volume does not change what they said, so it is usually fine. Do it in your own editor and upload the result. If a repair changes how they sound in a way they might object to, show them first.
Should I type out what they said and publish it as a quote?
Better to ask them to write it. Your hearing of a muffled clip may be wrong, and a quote they typed themselves is one they have clearly approved.
Is slightly rough sound a problem at all?
Not always. A visitor forgives a little room noise from a real customer. The test is whether they can follow every sentence on a phone speaker without replaying it.
Still have a question? Ask the StoryProof team or book a demo.
Collect the take you can actually publish
One link lets a customer re-record, leave an audio note or write their words, and nothing goes live until you approve it.
Last updated 2026-11-17.