How it works
What they keep saying, step by step
It quotes rather than summarizes away
Where it says a theme recurs, it points at the testimonials it read. You can go and check every claim it makes.
Sentiment, and the arrivals figure
How ratings have moved, how many arrived, where they came from.
It is useful for the product, not only the page
Eleven people praising the same thing you thought was minor is information about what to build next.
Ask your testimonials, and get their words back
Type a question on the dashboard — who mentioned price, which line suits the pricing page — and the answer is excerpts and nothing else, each linked to the testimonial it came from. Every excerpt is checked in code to be an exact stretch of what that testimonial publishes; anything else the model wrote is thrown away, and you are told how many were. It searches terms across all testimonials approved for your website, then reads up to 200 matching passages of at most 600 characters each. When no terms match, it reads recent passages instead. Every answer says how the passages were selected.
Safe by design
The rule that makes it safe to have
Clear boundaries
What it will not do
Every capability page ends with this list. It is the part that says what you are actually buying.
- It will not write a testimonial.
- It will not produce a statistic your customers did not give you.
- It does not compare you with anybody else's customers.
- A question is never answered in the machine's own sentences, never from a testimonial whose writer did not allow your website, and never from the words a removal took out of the published version.
Where it lives in the code: app/dashboard/[token]/report/page.tsx · lib/ai.ts · lib/ai-budget.ts · app/api/ai/ask/route.ts · components/AskTestimonials.tsx · lib/ai-filters.ts
Questions
Asked about this
From Help, where every answer is written from the product as it runs.
What does Hazelsong check before publishing, and what does it not verify?
Before anything is public, Hazelsong checks three things: that its recorded permission (the writer's own sentence, or, for an import, the API or a feed, the business's statement that it has permission) allows the place it would appear, and it is served nowhere else; the risk reading of its typed words, when the month's AI readings allow, while a recording or a picture is never read by AI and anything not read says so; and that the business approved it, in person or through the automatic moderation it chose to switch on. Nothing is published before that approval. Hazelsong does not verify that what a testimonial says is true, who wrote it, or that they bought anything, beyond what its record shows: how it arrived (the business's collection page, an import, the API or a feed), its permission and when it was given, whether a reward was attached, and whether a second person approved it. Publishing through it is not an endorsement of any testimonial.
Can I fix a typo in a testimonial?
No. There is no route in this product — no dashboard control, no API field, no administrator, no support request — that can change a testimonial's text. That is the rule the whole product is built around, and it is checked in code rather than promised in a policy.
Then what do I do about a phone number somebody left in it?
Remove that span: press Check for things to remove for a proposal, or Remove a part yourself to select the words, which uses no AI reading. The span becomes [removed], every other character stays exactly as written, and the reader is told something was taken out. If a result differs from the original by a single word anywhere else, it is discarded rather than applied.
Can I shorten a long testimonial for a widget?
Not by storing a shorter version: nothing here can keep a cut-down copy as though it were what somebody wrote. What a layout may do is show less of it — the compact, marquee, toast and sidebar layouts stop a long testimonial at six lines, and there is no control that opens the rest. Every other layout shows the whole of it, so the choice to make here is the layout.
This is running now
Open a project and use it. Nothing on this page is a roadmap.