Onboarding calls are screen shares by design. The CSM walks the new customer through their instance — settings, integrations, first workflow. The product's value is the customer's own data rendering on screen. But the CSM's desktop renders every other customer's instance too: the support queue, the admin panel, the CRM with the full book. The new customer should see their data. Nobody else's should be within capture range.
The Standard Setup (And Why It Fails)
"I share only their instance."
Why it fails:
- The admin panel is the escalation surface: "Let me check that setting on our end" — and the admin view lists other customers, their plans, their usage.
- Notifications: a support ticket from another customer, a billing alert with a company name, a Slack ping in the shared customer channel — over the shared screen.
- Window titles name the surfaces: "[Product] — Admin — Customers," "Salesforce — Opportunities," readable in every switcher frame.
- The support queue renders beside the instance during troubleshooting: other customers' names, subjects, and statuses in the sidebar.
Every other customer's name on screen is a confidentiality event — and onboarding is when the new customer is most attentively watching.
The NoCapture Setup for Onboarding
Cloak the book of business. The customer's instance visible; admin customer lists, support queues, CRM, and billing — cloaked. The capture stream receives their data and your guidance; your other forty customers were never in the frame. Internal tools stay accessible to you — they just can't be captured.
Mask the titles. Admin and CRM titles carry surface and customer-adjacent labels. Title masking sanitizes them in the window manager — enumeration and switchers read generic labels, so even the tooling around the call stays private.
Shield the session. Support, billing, and internal notifications held during the call — another customer's emergency never banners over the new customer's onboarding.
A routine per onboarding. The calendar event fires the configuration: instance visible, book cloaked, shield up. Protection that arms with the schedule, including back-to-back onboarding days.
Live preview before sharing. The preview pane confirms the share shows their instance. When the audience is a paying customer evaluating your professionalism, ten seconds of verification is part of the product.
The Honest Limitation
The frame controls visibility, not access — a CSM whose permissions span all customers can still pull up other accounts deliberately. Role-scoped admin views, customer-level permissions, and support-tool configuration are the substantive controls. NoCapture makes the accidental exposures impossible; your provisioning makes the deliberate ones unnecessary. Screen and system, both.
The Bottom Line
Onboarding is the moment a new customer watches you handle data — theirs and, accidentally, everyone else's. Share their instance with the book cloaked: titles masked, banners held, routine armed, preview checked. They should leave the call trusting your product with their data, never wondering whose else's data they just saw.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
