They see
Your heading and prompt
Your words, not a generic form title, so the request looks like it came from you rather than from a tool.
testimonial collection
The hard part of a customer testimonial form is not the fields — it is asking in a way someone busy will actually answer. This page covers what to put in the prompt, what the customer sees, and what you can promise them about how their words will be used.
The prompt is the one line you write, and it is shown above the story field and used as its placeholder. Ask about a change the customer experienced, not about you.
Six fields, one page, no account. This is the whole thing from their side.
They see
Your words, not a generic form title, so the request looks like it came from you rather than from a tool.
They see
The email field is labelled as kept private, and the page states that nothing publishes without review.
They see
Plain language, no pre-tick, no small print. Submitting is impossible without it.
They see
The last thing they read after submitting, and a chance to say what happens next.
Each of these is enforced by the product, so you can put them in your ask.
Useful search results start with an accurate promise. These limits apply today, in the shipped product.
As little as possible, aimed at a change rather than an opinion. A name, a private email, an optional role and company, a short story, and a rating are enough to publish credible proof.
Two or three sentences is a good target. The field accepts 20 to 1,200 characters and shows a live count, so customers can see that a short answer is welcome.
Yes, and asking for it in the form is far easier than chasing it afterwards. PraiseHarbor requires an explicit display-consent tick and stores the exact sentence the customer agreed to alongside the story.
Hide it, or delete it. Nothing publishes on submission, so an off-topic or unusable story costs you a click. Editing is limited to obvious spelling or length, which is what the consent sentence permits.