Customer support runs on screen shares. "Let me show you," the agent says, and shares their screen to walk a customer through the fix. But the support desktop is a PII environment: ticket queues with customer names and emails, chat panels with conversation history, internal notes about the person on the other end of the call. Sharing "the app" often means sharing the queue around it.
The Standard Setup (And Why It Fails)
"I only share the help center article or the product window."
Why it fails:
- Escalations go sideways: the agent needs the admin panel mid-call, shares a different window, and the ticket queue renders beside it.
- Notifications: a new ticket toasts with the customer's name and subject — over the shared screen, during the call, with the customer watching.
- Window titles name the ticket: "Zendesk — #48291 — [customer name]," visible in every switcher frame.
- Team leads screen-share queue reviews with the whole ticket wall visible — dozens of customers' PII in one frame for the recording.
Support is also a compliance surface: GDPR, CCPA, and PCI obligations attach to every name and email that renders on a shared screen. An accidental exposure isn't just awkward — it's a reportable incident.
The NoCapture Setup for Support Desks
Cloak the queue. Ticket queues, chat panels, and customer-context sidebars go on the protected list. Agents share the product, the article, the admin panel — and the capture stream receives only that. The customer's PII stays in the tools, not on the customer's screen.
Mask the titles. Ticket numbers, customer names, and subjects live in window titles. Title masking sanitizes them in the window manager — switcher frames and enumeration read a generic label, so even the existence of a specific ticket stops being visible metadata.
Shield the shift. Route Zendesk, Intercom, and email notifications through the shield during any shared or recorded session: new-ticket banners hold, queue alerts hold, customer names never toast over the call.
A routine per call. Screen-share starts → routine fires: queue cloaked, titles masked, notifications held. Armed by the behavior, not by the agent's pre-call checklist — because support volume doesn't leave time for checklists.
Live preview before every share. Ten seconds in the preview pane confirms what the customer will see. On a compliance surface, verification is the cheapest control in the stack.
The Honest Limitation
Cloaking protects the agent's screen — it doesn't fix what's in the product itself. If the admin panel legitimately displays customer data the call requires, that's a data-minimization problem no capture layer can solve: mask fields in the tool, use test accounts for walkthroughs, and route PII-heavy operations to non-shared sessions. And a customer can still see their own data — that's the job. The architecture keeps other customers' data out of every frame; your tool configuration keeps the necessary data minimal.
The Bottom Line
Every support screen share is a compliance event with a customer watching. Cloak the queue, mask the titles, hold the ticket banners, preview before sharing — and let the customer see exactly the fix they called for, never the forty other people waiting in line.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
