Step 1
Stored as pending
The story lands in your private inbox with its rating, consent record, and submission time. Pending stories are invisible to the public.
testimonial collection
Testimonial Form
Every PraiseHarbor space publishes one hosted testimonial form at its own address. Customers open the link, write a few sentences, tick a display-consent box, and submit. No account, no download, no login wall — and nothing they write appears anywhere until you approve it.
- Hosted link, no embed required
- Consent recorded per story
- Nothing auto-publishes
What the form actually asks for
The fields are fixed so the data stays clean and the consent record stays meaningful. Only the heading, the prompt, and the thank-you message are yours to write.
- NameRequired, 2–80 characters. Published with the story.
- EmailRequired, and kept private. It is used to reach the customer and to set the reply-to on your alert. It never appears on a wall, in an embed, or in the public API response.
- Role and companyOptional, up to 100 characters each. You choose whether the wall shows them.
- StoryRequired, 20–1,200 characters, with a live character count.
- Rating1–5 stars. You choose whether the wall shows the score.
- Display consentA required checkbox reading “I give permission to display this story publicly. It may be edited only for obvious spelling or length.” The exact sentence is stored on the record, so the permission you hold is the permission the customer read.
What happens after Send
The path from submit to published is four steps, and a person makes the last decision.
Step 2
You get an email
If the space has an alert address, PraiseHarbor emails it with the rating and the story, and sets the customer's address as reply-to so you can answer directly.
Step 3
You decide
Approve, hide, feature, or delete. Each decision is written to a moderation history kept with the story.
Step 4
It appears
Approved stories flow straight onto the public wall and every embed of that space. Featured stories sort first.
The spam and abuse controls that ship with it
These run on the public endpoint whether or not you configure anything.
- Hidden honeypot fieldA field no human sees. Anything that fills it is dropped silently and never stored.
- Rate limitingFive submissions per minute per IP address per space, applied at the edge.
- Payload boundRequests larger than 32 KB are rejected before parsing.
- Strict validationField lengths, email format, rating range, and the consent flag are all checked server-side, not only in the browser.
What this page does not claim
Useful search results start with an accurate promise. These limits apply today, in the shipped product.
- There is no video or file upload. Every story is text plus an optional 1–5 star rating.
- The field list is fixed. Custom or conditional questions are not supported.
- Collection pages and walls are served from praiseharbor.com. Custom domains are not available.
- Limits are bounded, not unlimited: five spaces per account and 500 stories per space.
Questions about testimonial form
Do customers need an account to fill in the form?
No. The collection page is public and anonymous to use. The customer gives a name, an email, and a story; the email stays private to you.
Can I change the questions on the testimonial form?
You can change the heading, the prompt shown above the story field, and the thank-you message. The field list itself is fixed, which is what keeps the consent record and the public projection predictable.
Is anything published automatically?
No. Every submission is stored as pending. A story only becomes public after you approve it in the moderation inbox, and you can hide it again at any time.
What does the consent checkbox actually record?
The record stores that consent was given, the moment it was given, and the exact sentence shown: “I give permission to display this story publicly. It may be edited only for obvious spelling or length.” That sentence is one shared constant in the codebase, so the form and the record cannot drift apart.