Blur Zendesk During Screen Sharing: Hide Customer Tickets and PII

To hide customer tickets and PII in Zendesk while screen sharing, add a browser extension like BlurFirst that blurs the requester names, emails, phone numbers and ticket content directly in the page before you present. The blur is rendered as real pixels in the tab, so it holds up on Zoom, Google Meet, Teams and Loom, and a saved Zendesk profile re-applies the same masks every time you open Agent Workspace — even as the ticket queue refreshes and tickets get reassigned.

What support agents expose in Agent Workspace

Support teams screen-share all day — QA calibrations, coaching new agents, escalations with engineering, and demoing workflows to other teams. Every ticket you open is somebody's personal data, and Agent Workspace puts most of it on screen at once. Before you present, plan to cover each of these:

• Requester name and email — shown in the ticket header, the requester field, and the conversation panel.
• Ticket subject and body — the description and every public reply can carry account numbers, addresses, order details, or health and financial information.
• Phone numbers — in the requester profile and frequently pasted into ticket comments.
• Internal notes — the yellow private notes often hold candid context, account flags, or a colleague's name.
• The user (requester) profile panel — the right-hand context panel with name, email, phone, tags and organization.
• Organization names — a single B2B org name can identify the account instantly.
• The ticket queue and Views list — subject lines and requester names for dozens of open tickets at a glance.

Macros, side conversations and live queue updates

Agent Workspace is dynamic, and that is where fragile blurs break. Applying a macro injects new text into the composer, opening a side conversation slides in a panel with an external email thread, and Views refresh as tickets are assigned or updated. Because BlurFirst saves a CSS selector rather than the text underneath, its blurs re-attach when the composer changes or a side conversation opens, and a box over the queue stays put as tickets move around. The trick is to blur the containers — the requester field, the conversation pane, the context panel — so any new content that lands inside them is covered automatically, instead of chasing individual strings.

1. 1

   Add BlurFirst and open Zendesk

   Install BlurFirst, open your Zendesk Agent Workspace, and press Ctrl/⌘ ⇧ Y to begin.

2. 2

   Blur the requester and profile panel

   Element-blur the requester name and email in the header, then box-blur the right-hand context panel so name, phone, tags and organization are all hidden at once.

3. 3

   Cover ticket content

   Box-blur the conversation pane. This hides the subject, body, public replies and internal notes while you narrate the workflow.

4. 4

   Mask the queue

   Switch to your Views and box-blur the subject and requester columns so the entire open-ticket list is covered.

5. 5

   Save a Zendesk profile

   Save the setup as a per-site profile so it auto-applies on your next login and survives macro and side-conversation re-renders.

6. 6

   Reveal deliberately, Panic if needed

   Click an element to reveal just it when you need to show something specific, and hit Ctrl/⌘ ⇧ H to blur everything instantly if you open an unexpected ticket.

For pattern-based data, the Pro Scan gesture finds emails, phone numbers, credit-card numbers and API keys anywhere on the ticket in one click and blurs them locally. Scan detects patterns, not free-text names, so pair it with a box over the requester field and profile panel to be thorough. All of it stays on your machine: the content script runs in an isolated world with namespaced CSS so it will not interfere with Agent Workspace shortcuts, and the only network call BlurFirst makes is a license check.

Be clear about the boundary: BlurFirst only affects the browser tab, so it cannot hide a separate CRM window, a softphone app, or desktop notifications — mute or close those separately. It also cannot run on chrome:// pages or the Chrome Web Store. Think of it as one control in a wider screen-sharing hygiene routine, not the whole thing.