Keep Sales Prompts Out of Your Screen Share

TL;DR

• Hiding notifications, hiding a panel and stopping capture are three different controls, and only one of them does what most people assume.
• Check the audience view rather than your settings. What the other side sees is the only reliable test.
• The mistakes happen at transitions: starting a share, switching windows, changing displays. Steady state is rarely the problem.
• Notifications from other applications are the most common leak, and they sit outside the meeting tool's control entirely.

Your demo can be well prepared and still expose an internal note at the wrong moment.

A pricing reminder, a competitor card or a message from a colleague might be useful to you and inappropriate for the customer. The practical question is which parts of the computer the meeting application is sending to everyone else.

Check that before the live call. Use a second participant's view, the actual sharing mode and a harmless test prompt. A feature labeled invisible is not enough information to skip the check.

This guide provides a procedure you can run. It does not report tested compatibility for any particular combination of assistant, operating system and meeting application.

Choose the surface you intend to present

Meeting applications offer different sharing choices. Google Meet documents tab, window and entire-screen options. Microsoft Teams distinguishes sharing a screen from sharing a window. Zoom supports an entire desktop, specific applications and other content modes. Availability and controls depend on the client and configuration. 1 2 3

For a browser-based product demo, a dedicated tab or window is a useful starting point. Keep unrelated tabs and internal material elsewhere. For a presentation, share the intended presentation surface rather than assuming the entire desktop is necessary.

This is a risk-reduction choice, not a universal guarantee. You still need to confirm how the selected mode behaves when the application opens a dialog, launches another window or changes displays.

A customer who needs to see one product should not need a view of your email, internal chat and account research. Design the presentation around that requirement.

Separate three controls that sound similar

Closing an assistant panel, hiding its notifications and stopping its capture can produce different results.

The first changes the interface you see. The second changes a class of visual interruptions. The third changes whether the application continues processing the meeting. Treat them as separate controls until the documentation and a test establish the behavior.

Magic Screen's meeting guide describes a dock with a Record/Stop control and an eye control for showing or hiding notifications. It recommends hiding notifications when screen sharing. That is useful operating guidance; it should not be interpreted as proof that all application content is excluded from every capture method. 4

Fathom also documents an invisible-when-sharing setting in its desktop interface. Screen-share controls are therefore worth checking in the selected product rather than assuming they are unique to one assistant. 5

For a live demo, decide whether you need the guidance visible to you, hidden temporarily or stopped entirely. Practice the appropriate action so you are not discovering the difference in front of the customer.

Check the audience view, not your memory of the settings

Create a short test meeting with a colleague or a second device signed in as a participant. Use fictional account information and an obvious sample prompt such as "Internal test: pricing review required."

Start the exact share you expect to use in the customer meeting. Ask the observer to describe what appears. Then trigger the prompt, open the assistant panel, move between the intended demo screens and end the share.

Do not rely solely on your own preview. The remote participant's view is the acceptance check for the live presentation. If the meeting will also be recorded, inspect the resulting recording through the approved process as a separate check.

Write down the application version, operating system, sharing mode and date. A successful result belongs to that configuration. After a relevant update, a new device or a changed presentation setup, repeat the check.

Test the transitions where people make mistakes

A stationary demo screen is an easy case. Your test should include the actions you expect to take when a buyer asks an unexpected question.

Opening supporting material. Move from the product to the approved slide or document. Check which surface remains shared and whether anything unrelated becomes visible.

Changing windows or tabs. Practice the intended transition. When uncertain, stop sharing, arrange the next surface and start a new share deliberately.

Opening a dialog. Test file pickers, authentication prompts and other required dialogs with harmless data. Avoid using customer records or sensitive filenames in the rehearsal.

Moving across displays. A second monitor can help organize the workspace, but its presence does not establish which display the meeting application is sharing. Verify the selection and the remote result.

Responding to an assistant cue. Open or dismiss a sample cue while the observer watches. Include any expanded view you might use to read the full answer.

Returning from a break. End and restart the share. Confirm that the application did not select a broader surface than you intended.

The point is to rehearse the actual presentation path, including interruptions. A test of an untouched window will not tell you what happens when you depart from it.

Include notifications from other applications

The sales assistant may be only one source of internal information on the machine.

Before the demo, close unnecessary applications, silence nonessential notifications and move confidential working material away from the presentation environment. Use the operating system's available notification controls according to your organization's practice.

Then test a harmless notification. Observe it from the participant's device in the selected sharing mode. Check any meeting chat, calendar reminder or messaging application you expect to remain open.

Do not populate the test with real sensitive content. You need to establish whether a surface is visible, not demonstrate that an actual confidential message can escape.

Keep a separate demo account where the product supports one. A clean set of fictional records is easier to present responsibly than a production account with unrelated customer data.

Audio needs a separate decision

A clean visual presentation does not answer what audio the meeting transmits.

Google Meet documents audio behavior that differs between sharing a tab and other sharing choices. Zoom also provides options for sharing audio from the device. Check the selected controls when the demo includes a video, sound or another audio source. 1 3

Use a harmless test sound and ask the observer what they hear. Keep unrelated audio applications closed. If the assistant has any audio output, include that behavior in the test rather than assuming a hidden visual panel also makes its sound private.

The same discipline applies when the meeting uses more than one microphone, headset or computer. Confirm the intended inputs and outputs before the customer joins.

Keep a small configuration log

Use the following blank log for your own verification. Every entry starts as Not run. This table contains no product test results.

Mark a check as passed only when the observer confirms the intended result. Mark an unexpected exposure as a failure and adjust the setup before retesting. Leave unsupported or untested combinations clearly labeled.

Save the successful configuration with the demo instructions. New team members should not need to reconstruct which sharing option was used.

Have a recovery action ready

If internal material appears during a call, stop the share first. Remove the exposed surface, acknowledge the issue appropriately and follow the organization's incident process when the content warrants it.

Do not keep clicking through confidential information while trying to repair the presentation. Resume with a deliberately selected surface after confirming the setup.

A recording creates an additional consideration. Restrict further distribution and involve the appropriate owner rather than assuming that ending the share removed the material from a saved artifact.

For less serious interruptions, such as a harmless internal reminder, the same basic response still helps: pause, reset and continue. Rehearsing that action makes it easier to handle without turning a small issue into a larger one.

Use Magic Screen with deliberate presentation controls

Magic Screen can keep prepared sales material in the live Mac workflow, so the rep can consult a resource without starting a separate search. Its documented notification control gives the rep another way to manage that interface during a presentation. 6 4

Start with one approved script or insight and the exact demo setup. Check whether the guidance is usable to the rep and excluded from the intended audience view. When those requirements conflict, simplify the presentation or hide the guidance for that portion of the call.

Keep capture permission separate throughout. A customer who declines recording or transcription has set a boundary about processing the conversation, not merely about seeing a tile or panel. The no-recording guide covers that decision.

Use this checklist before the next important demo, then retain the successful configuration. The useful result is a repeatable presentation setup with clear controls, not an assumption that every surface is always private.

Frequently asked questions

How do I hide AI prompts during a screen share?

Decide which surface you are presenting before the call, then verify in the audience view. Hiding notifications, hiding a panel and stopping capture are three different controls.

Will my AI assistant show up when I share my screen?

It depends on the configuration and the share mode, and it changes at transitions. Test a window share, a full-screen share and a display switch separately.

What is the most common way prompts leak?

Notifications from other applications, which sit outside the meeting tool's control entirely and appear at the worst possible moment.

Sources

1. Google Meet Help. Present during a video meeting. Checked September 10, 2026.
2. Microsoft Support. Present content in Microsoft Teams meetings. Checked September 10, 2026.
3. Zoom Support. Sharing your screen or desktop on Zoom. Checked September 10, 2026.
4. Magic Screen. Meeting Detection and Recording. Checked September 10, 2026.
5. Fathom. Desktop App Overview. Checked September 10, 2026.
6. Magic Screen. Sales Script Suggestions. Checked September 10, 2026.