Ticket system
The person who found it can see you looking at it.
A form for what broke, and a private conversation with the person who found it.
A bug report that arrives as "it doesn't work" is not a bug report.
You need to know where, what they expected, and how to reach them again — and every round of asking loses somebody. A form that collects it up front and a thread that stays open is most of the work.
Save button does nothing on the settings page
What it does
It knows where it happened
The form captures the page it was embedded on — prefilled, and editable, because the guess is sometimes wrong. "On the pricing page" is the first thing you would have had to ask for anyway.
A thread, without an account
The reporter gets a private link. No sign-up, no password, nothing for you to administer — and they can come back to it whenever they like.
A status they can watch
Received, Looking into it, Fixed, Not a bug. You set it, and they see it change without having to write and ask.
Notes only you can see
Add an internal note to any report. It is filtered out by the query that builds the reporter's page, not hidden with a style, so no future edit can leak one.
Closing is not a status
Fixed and Not a bug say what happened to the bug. Closing says the conversation is done. Keeping them apart means a closed report still tells you which one it was.
The link survives a lost inbox
The reporter's private link is stored encrypted and shown to you on the report, so somebody who deleted the email is one copy-and-paste from being back in.
Four ways it shows up
What they fill in
Short and specific, and it already knows which page it broke on.
What went wrong?
Where did it happen?
What they see afterwards
A private thread and a status, without an account or a password.
Save button does nothing on the settings page
Reproduced it — a caching bug. Fix goes out this week.
What you see
One list across every form you run, with what needs you at the top.
PH-8F3K2A · Looking into it
PH-QW71LM · Fixed
PH-4RTZ9P · Received
A note only you can read
Left on the report, filtered out of the reporter's page by the query itself.
Save button does nothing on the settings page
Internal note
Cache layer — same root cause as PH-4RTZ9P.
Fair questions
Is this a helpdesk?+
No — and deliberately so. There are no queues, agents, SLAs or seats. One form, one thread per person, one status they can see.
Do I need to set up email?+
Not to start. The reporter gets their link on screen the moment they send, so the thread is reachable with no mail configured at all. Adding email just means neither of you has to remember to look.
Works with
Adding it
One script tag on the page you want it, or a link to the page we host. Both come with every widget.
<div id="changelog"></div>
<script src="http://localhost:3000/embed/your-slug" data-target="#changelog" async></script>Your product moved this week. Your website should say so.
Set up the first widget in a few minutes and put it live today.