Redact a customer support screenshot before Slack

The ticket is “refund failed.” The screenshot is the customer’s Gmail, their kids’ names in the inbox, and an order ID you did not need.

Support work is a conveyor of other people’s screens. Someone pastes a decline modal. Someone else pastes the whole desktop: mail, CRM sidebar, a Slack huddle with a coworker’s last name. The ask was the error string. The file is a personnel record with a toast overlay.

Treat the capture like a document you would not leave on a printer: bar mailbox, phone, street, salary fields, and government ID numbers if a KYC upload leaked into the thread. Keep the error toast. Paste the PNG in Slack, not a second photo of your laptop at an angle.

What the ticket actually needs

A useful support screenshot answers one question: what did the product show at the moment it failed? That is usually a modal, a banner, a network error, or a specific row in an order table. It is almost never the customer’s inbox list, the agent’s internal URL, or the last four of a card sitting in a wallet widget.

Crop first when extra chrome is noise. Bar when leftover pixels are identifiers. Cropping Gmail still leaves the account chip if you were sloppy. A black rectangle on the chip, subject lines, and address-book preview makes the file safe to paste into Slack or a vendor ticket.

A boring checklist

• Email and phone in headers, signatures, and quoted replies
• Home or shipping address, including apartment numbers in maps
• Last four of a card, full PAN, expiry, and CVC if they appear
• National ID, passport numbers, or “verification” photos of IDs
• Other tickets in the sidebar, including names of other customers
• Internal admin URL, tenant slug, and SSO tiles
• Salary, refund amount paired with a name, or payroll labels

Agents copy-paste from the CRM. The CRM repeats the same fields in the header, the activity feed, and the hover card. One bar on the toast is not enough if the left rail still names the household. Walk the edges of the frame the way you would walk a form before you submit it.

Why a black bar, not a smear

Phone numbers, emails, and ID strings survive light blur. Chat apps recompress. A “professional” Gaussian that looks unreadable on your monitor can still leave enough glyph shape for someone to recover digits after another resize. Paint opaque rectangles. If you already used highlighter on a phone, start over from the original capture.

Export PNG when you control the file. If Slack or Zendesk will turn it into a JPEG, make the bars oversized so ringing does not outline the text you meant to kill. Do not photograph the screen; that adds EXIF, glare, and a second copy of every notification that floated in.

Where the file goes after you hit send

Internal Slack is not a vault. Threads get shared to vendors, to “the other pod,” to a Google Doc of “funny tickets.” Assume the PNG will leave the company. If legal or a processor needs the unbarred original, keep it in the ticketing system with access control, not in a #random channel. The version you paste for debugging should already be the barred one.

Shared screens in a huddle get screenshotted. Bar the CRM before you present, or share a window that only contains the sanitized PNG.

Should support ask customers to redact first?

Yes, in the canned reply: error text and time, not the inbox. Many will still send the whole desktop. Bar before you escalate. If a customer sent a government ID “to prove they paid,” do not re-upload it to a public status page. Cover face, number, address, and barcode; keep only what policy retains in the private ticket.

What if the bug only shows with live customer data?

Reproduce with a test account when you can. When you cannot, capture the smallest region that shows the defect, bar every name and identifier around it, and write the order ID in the ticket field instead of leaving it in the pixels. Dummy data that still contains a real email is not dummy data. If a staging database was copied from production, treat those rows as production.

FAQ: can I leave the order ID visible?

Internal tickets can keep an order ID if policy says it is not a secret and the rest of the frame is barred. Public changelogs and status pages should not. An order ID plus a visible email is enough to harass someone. When in doubt, bar the ID in the image and type it into the private system of record.

FAQ: is crop enough for a long email thread?

Crop removes area. It does not remove quoted signatures lower in the same message, nor the account chip, nor the notification that slid in from the corner. Scroll the thread, cover every repeat of the address and phone, then crop. If you only needed the bounce error, crop to the bounce and bar the remaining chip.

Slack chrome and huddle leaks are covered in the Slack screenshot guide. Payment widgets that print card digits belong with the bank app notes. When the next refund screenshot lands, bar it in the browser tab before it becomes someone else’s Slack history.