"The export drops the last row of every month. Our accountant said the totals never match in December."
Next: Ana fixes it in GitHub #412 (pull request #418 open).Next: 1 of 4 customers still to confirm it works. Closes Friday if they don't answer.
Ship with coding agents and still answer every customer. Merle is a feedback button for your app. Every request lands in one inbox with an owner, a status and a next step. When it ships, everyone who asked is told.
Free to start. Bugs go to GitHub or Linear. Merle doesn't touch your code.
Two lines in your app. Your backend changes only if you want customers' names.
<script type="module" src="https://feedback.hellomerle.com/button.js"></script>
<merle-feedback product="your-product" endpoint="https://feedback.hellomerle.com"></merle-feedback>
Inside your app, not on another site. They type it, say it, or show you the screen. Merle keeps the address of the page they were on and, when your sign-in vouches for them, who they are.
Each request gets an owner, a status and a Next: line that Merle writes from where things stand. Bugs go to GitHub or Linear with one click and come back when the issue closes.
When it ships, everyone who asked is told through the feedback button, and by email if they asked for that, and asked if it works. "Still broken" comes back to you, not to them.
This is the whole back office. No boards to groom, no fields to fill. Decide, and the customer side takes care of itself.
One name. Until someone takes it, the Next: line says "someone decides" and the request waits in Needs a decision.
New, decided, in progress, fixed and checking, done. Later for what you parked, Answered for what needed a reply, not a fix.
One line Merle writes from where the request is: who decides, which issue it's in, who still has to confirm it works. Nobody types it.
Merle doesn't fix code. Your engineers do, in the tools they already use. Merle keeps the asking and the telling in one place.
Typed or spoken. A spoken message is turned into text and the audio is dropped.
A picture of the page with every text field blurred, and a circle or an arrow on the part that's wrong. Or a recording of the tab while they show you, with their voice if they allow the microphone.
The page address, the window size, and what they tapped on the way. Never what they typed into your app, never your request bodies.
When your sign-in vouches for a customer, their name comes with the message. The same request from six people is one request with six people to tell.
Free to start. Sign in, add two lines to your app, and the first request shows up the moment someone presses the button.