How CustomerShip turns customer feedback into shipped code
Most feedback loops break at the handoff. A customer says what they want, it lands in a spreadsheet or a Slack channel, and then someone has to notice it, understand it, and actually write the code. CustomerShip collapses that handoff into one flow: request in, reviewable pull request out.
1. Collecting the request
You add a small button to your own site — either a popup that never leaves your page, or a link to a CustomerShip-hosted page. Either way, the customer writes what they want in plain language and it lands in your dashboard immediately. No account required on their end.
2. Reviewing and shipping
Every request sits in your inbox as RAISED until you act on it. You can reject it, mark it already done, or ship it. Shipping is the only step that costs anything — collecting requests is always free.
3. What happens when you ship
Once you approve a request, it's queued for a coding agent. The agent works against a real, temporary clone of your connected repository — never your live branch directly — reads the relevant files, makes the change, and runs your test suite if you have one. Only the working tree it produces is trusted; nothing it does inside the sandbox is taken on faith.
4. A pull request, not a merge
The result is a normal pull request against your default branch, opened through your existing GitHub App installation. You review it exactly like you'd review any other PR. CustomerShip never merges on your behalf.
That's the whole loop. See how shipping works for the details on doubloons and refunds.