Escalation is where support screenshots become a second ticket system. The error toast that belonged in Zendesk suddenly lives in Slack, a vendor Jira, a partner Drive folder, and a public status draft, each with its own audience and retention. If the customer’s email, phone, and shipping line traveled with that PNG, every hop multiplied the exposure.
This page is the covering habit for that path: keep the broken UI, strip the person. It is technique, not a GDPR program. Teams that need the policy vocabulary should read GDPR and customer support screenshots after this one.
What the escalation actually needs
One question: what did the product show when it failed? Usually a modal, a banner, or one order row. It is rarely the customer’s full inbox, the agent queue, or three other tickets in the left rail. Zendesk repeats the requester email in the header, the properties pane, and the first comment. Intercom shows the same address in the user card plus a list of related conversations. Bar every repeat, then crop.
Order IDs sit next to names. That pair is enough to harass someone if the PNG leaves the company. Internal tickets can keep an ID when policy says so. Public status pages and social posts cannot. If you are unsure, bar the ID in the image and type it into the Slack message as text your teammate already has in the system of record.
Open larger image in a new tabHow to redact a support screenshot before Slack
- Open the one ticket. Collapse the customer sidebar if the product allows it. Scroll so other tickets are not in view.
- Capture a region around the error, not the full agent workspace. Prefer the computer’s snip over a phone photo of the monitor. Glare and a second notification are not helpful evidence.
- Draw a filled black rectangle over emails, phones, card digits, shipping lines, neighboring ticket titles, and any internal note that names a person.
- Save a PNG. Paste that file into Slack or the vendor form. Do not paste a live snip from the clipboard that still points at the raw capture.
- For a browser canvas that keeps the file in-tab, open BlurThis, pick Black bar, mark each region, then Download PNG.
Soft blur is not enough for short strings. Phone numbers and emails survive a polite smear. Opaque rectangles do not. Card PAN and CVC are the same class of secret. The card-specific walkthrough is hide credit card and account numbers.
Support screenshot checklist
- Email and phone in headers and signatures
- Home or shipping address
- Card digits, last four, PAN, expiry, CVC
- National ID or passport photos attached to the ticket
- Other tickets in the sidebar or related-conversation panel
- Internal admin URL or tenant slug in the browser bar
- Salary or refund amount next to a name
- Macros and drafts that still show a previous customer’s name
Freshdesk, Help Scout, and HubSpot Service look different and leak the same fields. Internal notes are not public to the requester, but they are public to whoever gets the Slack PNG. Cover the note if it names a person.
Why PNG beats a thin bar on a JPEG
Prefer PNG so you can inspect a flat fill. If Slack turns the upload into a JPEG, make the bars oversized so ringing does not outline the text. Thin bars grow halos. Format notes: PNG versus JPEG. The general rule for short secrets is blur versus black bar.
Open larger image in a new tabWhere the file goes after send
Internal Slack is not a vault. Threads get shared. Assume the PNG may leave the company. Paste the barred version for debugging. A vendor Jira, a partner’s Google Drive, and a public forum are all wider audiences than your #support-escalations channel. When the snip includes Slack chrome itself (workspace URL, huddle strip, sidebar emails), cover that rail too. Details: Slack screenshots.
Ticket platforms keep the original attachment. If a customer uploaded an unredacted PNG, bar it before you forward, and consider deleting the original from the ticket if policy allows. Your escalation should not multiply copies of the raw file.
Ask customers to redact first
Put it in the canned reply: error text and time, not the whole desktop. Many will still send everything. Bar before you escalate. Ask for a crop around the modal. Tell them not to photograph a card or a passport “for verification” into the ticket. If they already did, treat it like an incident, not like an attachment to react to with an emoji.
CRM and ticket tools (Salesforce, Jira, HubSpot)
CRM snips leak contact emails, deal amounts, and assignee names in the sidebar. Bar the contact row and any opportunity value before you paste into Slack. Jira titles often include customer names. HubSpot timelines reprint inboxes. Salesforce highlight panels stack phone, email, and billing address in one column. Intercom’s user card does the same with a smaller font. Zoom in. If a glyph remains at the edge of the bar, enlarge it.
Admin URLs in the browser bar include tenant slugs and sometimes record IDs. Cover the bar on a public post. Internal tokens in that URL: hide keys in the URL bar.
If the sidebar still shows three other tickets
Full-screen capture is the usual mistake. Use a region snip. If the product will not collapse the queue, bar the whole left column. Filter views named after a VIP are a name. Saved replies that include a sample email in the composer are a second mailbox. Close the composer before you capture.
FAQ: Leave the order ID visible?
Internal tickets, only if policy allows and the rest is barred. Public pages, no. Order ID plus email is enough to harass someone.
FAQ: Is crop enough?
Crop removes area. It does not remove quoted signatures or a notification in the corner. Cover every repeat, then crop. Notifications mid-capture: notifications in screenshots.
Recap
Crop to the error. Bar email, phone, card digits, shipping lines, and the queue of other tickets. Save a PNG. Paste that file into Slack, not the live agent workspace. Ask customers to send a crop next time, then bar what they still include. Related: hide a phone number or email and the how to blur hub.
