How it works
Read for risk, step by step
It reads on arrival, not on request
There is no button to press and no queue to remember. A testimonial is read the moment it lands and carries its flags into Pending.
It says what it found, and why
A promised outcome, a figure, a claim of specialization, a named third party, somebody's private detail. The reason is written beside the flag; you are not asked to trust a score.
You decide, every time
Nothing is rejected automatically and nothing is published automatically. The flag is information for the person whose license it is.
Every word arrives as they wrote it — even the 555-0142 they meant to leave out.
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 does not make you compliant with anything, and does not claim to.
- It does not know your regulator's rule and will not pretend to have read it.
- It will not reword a testimonial to make it publishable — see removing a detail, which is the only kind of change allowed here.
Where it lives in the code: lib/ai.ts · lib/ai-budget.ts
Questions
Asked about this
From Help, where every answer is written from the product as it runs.
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. The span becomes [removed], every other character stays exactly as written, and the reader is told something was taken out. If the proposal differs from the original by a single word anywhere else, the whole proposal 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.
A customer asked me to take theirs down. What happens?
Delete it, and it is out of every widget, wall, image and API answer at once — a real delete, the record and the files both. There is no archive here: a testimonial is pending, approved or rejected, and once it is approved the dashboard's own way to take it off your pages is Delete. Reject is the button while it is still pending.
Next to this
Works together with
This is running now
Open a project and use it. Nothing on this page is a roadmap.