Turn customer problems into verified fixes.
A ticket describes a symptom. Patch turns it into a reproduction, a test that fails for the right reason, and a change that makes it pass — then replays the customer's original workflow.
- TicketSUP-4471 · 3 similar open
- ReproductionIsolated in 41s
- Failing testWritten from the report
- Diff1 file · 4 lines
- VerificationOriginal workflow replayed
- Pull requestWaiting on a human
“Exporting a project whose name contains a slash gives me an empty file.”
export() → 0 bytes
✗ expected 2.4 KB, got 0
Most of the work in a bug fix happens before anyone writes code.
What you can already see
- Open tickets
- 184
- Median first response
- 2h 10m
- Median time to fix
- 9 days
- Tickets that are duplicates
- 38%
What nothing tells you
- Which of those 184 are the same bug wearing different words.
- Which one has 27 people behind it.
- Which could have been reproduced in under a minute.
Nine days is rarely nine days of engineering. It is waiting, clarifying, reproducing, and finding the person who knows which service owns it.
Sorted by how many people are actually affected.
Duplicate reports are collapsed into one problem, so the queue is ordered by impact rather than by arrival time.
- SUP-4471Export empty when project name contains a slash4 reportsPR ready
- SUP-4468Invite email never arrives for .edu addresses11 reportsVerifying
- SUP-4452Dashboard totals disagree with the CSV3 reportsReproducing
- SUP-4449Session drops after switching workspace27 reportsNeeds a human
Reproduce first. Everything else follows from that.
- 01
Cluster
Reports describing the same underlying problem are grouped, whatever words the customer used.
- 02
Reproduce
Patch reconstructs the conditions from the report and confirms the failure before touching any code.
- 03
Prove
A failing test is written from the reproduction, so the fix has something to satisfy.
- 04
Propose
A diff, the passing test, the replayed customer workflow, and a pull request waiting on review.
Sources this product is designed to read
Intercom, GitHub, PostHog can be connected today. The rest are sources the model is built for and cannot be connected yet — the app never offers a provider whose consent flow it cannot complete.
Support
- Intercom — can be connected today
- Zendesk
- Front
- Help Scout
- Slack
Engineering
- GitHub — can be connected today
- GitLab
- Linear
- Jira
Runtime
- Sentry
- PostHog — can be connected today
- Staging environments
- Preview deploys
Patch is in early access.
We are working with a small number of teams whose support queue is bigger than their engineering team. If that describes you, tell us what your queue looks like.