How to Blur Intercom During Screen Sharing Without Exposing Customer Data

Short answer

Before sharing Intercom, blur customer identity fields, conversation lists, and internal notes so support calls stay useful without exposing private data.

Direct answer

To blur Intercom safely, mask customer names, emails, conversation lists, and private notes before sharing, then present only one window.

Step-by-step

1. 1Open the exact Intercom view you plan to share and close unrelated tabs.
2. 2Blur customer identifiers, conversation previews, and internal notes.
3. 3Verify the shared view with a 2-second preview before going live.

FAQ

What is most often leaked in Intercom screen shares?

Conversation list previews and side-panel customer details are the most common accidental exposures.

Should I blur only one ticket or the whole inbox?

For training and recorded calls, blur the inbox list too, not only the active conversation.

Can this workflow be reused for Zendesk and other support tools?

Yes. The same approach works across most support dashboards with minor UI differences.

Intercom is fast for support teams, but its UI is dense with customer data. During QA calls, onboarding sessions, or vendor walkthroughs, one shared screen can reveal far more than intended.

The risk is usually not the main conversation pane. It is the surrounding interface: conversation list previews, side-panel attributes, and internal notes.

What to blur in Intercom first

Before you share, hide these areas:

• customer name and email in the profile panel
• phone number, organization, and user attributes
• conversation list snippets in the left sidebar
• teammate-only internal notes
• tags and custom attributes that identify accounts

If you are also showing deployment/admin tools in the same session, include secret protection steps from vibe coding security.

Fast workflow for support teams

Use this sequence before every call:

1. Open your target view in Intercom.
2. Activate blur mode and mask identity fields first.
3. Blur sidebars and conversation previews.
4. Scroll once to catch internal notes and custom attributes.
5. Share one window only, never your full desktop.

The same method is recommended in our Zendesk guide for blurring support dashboards.

Recorded calls need stricter defaults

If a session is recorded, use stricter masking:

• blur all identity-related fields by default
• hide unrelated conversations entirely
• remove notifications and popups before joining

This simple upgrade reduces compliance and trust risk, especially for teams handling personal or billing data.

For a broader prep routine, use the screen sharing checklist before each session.