Turn customer bug reports into screen recordings engineers can act on
Updated
Customer bug reports are hard to act on when they arrive as a sentence in a support ticket. With Midge, a support agent reproduces the problem in Chrome and turns it into a screen recording or annotated screenshot that carries the console errors, network requests, steps and browser details engineering needs. When only the customer can reproduce it, a recording link lets them record their own screen without installing anything.
The goal is simple: one escalation, one link, no follow-up questions from engineering. Every recording includes console logs, network requests, user actions and device info.
The usual problem
A customer writes: "The export button doesn't work." The agent tries it, sees a spinner that never ends, and escalates with "Export broken for customer, please check." Engineering replies with questions. Which account? Which browser? Any error? The customer has gone quiet, and the ticket waits.
Midge shortens that loop. The agent records the attempt, and the report already answers the questions:
GET /api/exports/7731/status 200 every 2 s, 45 times
response: {"state":"failed","reason":"row_limit_exceeded"}
Console: no errors (the UI keeps polling and never shows the failure)
Engineering now knows the export failed on the server because of a row limit and the front end never told the user. That is a fix, not a conversation.
How support teams use Midge today
Reproduce in your own browser
Most customer issues can be reproduced by an agent: on a test account with similar data, in a sandbox, or through your product's own view-as-customer feature if it has one. Start a screen recording, follow the customer's steps, and stop when the problem shows. If the issue is visual, an annotated screenshot with an arrow and a short label is often enough.
Agents do not need to open DevTools or know what a HAR file is. Midge captures the technical side in the background, including errors that fired before the agent pressed record.
Escalate with one link
Every report is a link you can paste into any escalation, whether that is Jira, Linear, a Slack channel or your helpdesk's internal note. If a workspace admin has connected Jira, Linear, GitHub Issues or Slack under Settings › Workspace › Integrations, send the report from its page: it opens an issue or posts to the channel with the link, the AI summary and the steps to reproduce. See integrations. For a helpdesk note, paste the link. Set the report's sharing to "Workspace members" if the escalation channel is wider than your team.
When only the customer can reproduce it
Some bugs depend on the customer's network, browser extensions or data you cannot copy. For those, send a recording link (more below). If engineering needs the network log as well, ask the customer for a HAR file. Our guide on how to get a HAR file is written so you can send it to a non-technical customer. HAR files contain cookies and tokens, so run the file through the free HAR sanitizer before attaching it to a ticket. It works in your browser and uploads nothing.
Letting customers send recordings
Two features let customers send you reports directly:
- Recording links. Create a link under Settings › Workspace › Recording links and send it. The customer opens it in Chrome, Edge, Firefox or Safari on a computer, records their screen and sends it. No extension, no account. The recording lands in your workspace with a transcript and an AI summary. A browser page cannot read another site's logs, so link recordings carry the video and the customer's voice, not console or network logs. Customers on an iPhone can answer a link with Midge's iPhone app.
- Website SDK. Add one script tag to your product and it gets a Report a bug button. Reports made there carry console logs, network requests, clicks and your own metadata, redacted in the customer's browser. It only sends from domains your workspace has verified. The website SDK guide shows the setup.
For bugs that need the network log and happen outside your app, agent recordings and sanitized HAR files still cover the gap.
Customer data and redaction
Support works with real customer accounts, so privacy cannot be an afterthought. Passwords, card numbers, tokens and cookies are redacted in your browser before anything leaves your device. Emails and international phone numbers are half-masked, so [email protected] appears as m***@example.com. Engineering can still tell which account was affected without the full address being copied into every ticket.
Typed text is never recorded, and password and card fields are blurred in tab recordings. Two cautions for agents:
- Window and full-screen recordings are not blurred automatically. Close the CRM tab with other customers' details before recording your whole screen.
- Names and addresses shown on the page appear in the video. Use the blur tool in screenshots for anything personal.
The full rule list is on the redaction page and the security page.
Cost
Midge is free: unlimited recordings, videos up to 15 minutes, and no watermark. Support teams can add every agent to a workspace and keep folders per product area or per week, at no cost. Paid plans may come later; the pricing page shows the current terms.
Tips for better escalations
- Put the customer's words in the description, then what you observed.
- Name the symptom in the title: "Export spinner never stops for large workspaces".
- Mention whether you reproduced it on a test account or only the customer saw it.
For a fuller checklist, see how to report a bug.
Frequently asked questions
- Can customers record their own screen with Midge?
- Yes. Send a recording link: the customer opens it in Chrome, Edge, Firefox or Safari on a computer, records their screen and sends it, with no account or extension. The recording lands in your workspace with an AI summary. Support agents can also reproduce the issue themselves with Midge.
- Do support agents need technical knowledge to use Midge?
- No. They record the screen or take a screenshot as they would with any tool. Console errors, network requests and browser details are captured automatically, without opening DevTools.
- What if the bug only happens on the customer's computer?
- Send them a recording link so they can show it on their own computer. If engineering also needs the network log, ask for a HAR file using a step-by-step guide, then clean it with a HAR sanitizer before it goes into a ticket.
- Is customer data safe in a Midge report?
- Passwords, card numbers, tokens and cookies are removed in the browser before upload, and emails and phone numbers are half-masked. Redaction is rule-based, so agents should still blur anything unusual in a screenshot.