Collecting¶
Five doors, one queue. Whatever route a piece of feedback takes, it lands in the same moderation inbox as pending, and nothing is published without a person approving it.
-
A page we host at a URL you can send people. No code.
-
One script tag on your own site — a launcher panel, or a wall.
-
In-browser recording, on a hosted page or in the widget.
-
Versioned, so editing one mid-flight cannot corrupt your results.
-
Bring testimonials you already have, with their provenance intact.
Which door to use¶
| Situation | Use |
|---|---|
| Emailing customers a link | A hosted page |
| Asking visitors already on your site | A collect widget |
| You have your own form design | The public API |
| Moving from another tool | A CSV import |
| Your app knows when to ask | The widget's open call, or the API |
What every door has in common¶
- Pending on arrival. No exceptions, including anything created through the API or flagged as good by AI moderation.
- Consent is separate. Reading a submission and publishing it are different permissions, and the second one comes from the person who wrote it.
- Provenance is recorded, not claimed. Which widget or page something came through is resolved server-side; a caller cannot relabel its own traffic.
- Email addresses are checked for deliverability at the point of entry, so a typo is caught while the person is still there to fix it.