Private Meetings in Spiky: Secure Confidential Sales Calls

Private Meetings is Spiky's access-control feature for sales calls: it lets an org restrict who can view a specific meeting's recording, transcript, and AI analysis, instead of making every call visible to everyone with dashboard access by default. You turn it on at the org level, then apply it per meeting — before, during, or after the call happens — so pricing negotiations, legal reviews, and executive conversations stay confidential without you having to manually lock things down after the fact.

Why this matters beyond "privacy"

Conversation intelligence platforms create a new kind of exposure that didn't exist when sales calls just... happened and were forgotten. Once a call is recorded, transcribed, and summarized by AI, it becomes a searchable, shareable artifact — which is exactly the point for coaching and forecasting, but a liability for anything touching discount thresholds, legal terms, or an exec's unfiltered read on a deal. Two scenarios where this shows up constantly:

Renewal negotiation with margin exposure. A rep is fighting to keep a churn-risk account. The call covers the actual discount floor the company will accept, a direct comparison to a competitor's undercut pricing, and a contractual workaround legal hasn't signed off on yet. If that analysis is visible org-wide, any rep — including ones on competing accounts or without a need to know — can search and read the exact numbers. Private Meetings lets the organizer restrict that meeting to the deal team and their manager before the call even starts.

Regulated-industry compliance reviews. Sales teams in financial services, insurance, fintech, and cybersecurity often loop in legal or compliance on calls that reference specific regulatory language or client PII. Spiky is used in production by teams in exactly these industries — a major insurance provider, for instance, runs Spiky across strategy evaluation, real-time coaching, and offline compliance review as part of its regular workflow. These orgs frequently need to prove that sensitive conversation data was only accessible to a defined, auditable list of people — not exposed platform-wide.

How this connects to the rest of Spiky

Private Meetings isn't a bolt-on setting — it works inside the same pipeline that powers Spiky's coaching and intelligence features, which is why the trade-offs matter:

• Whisper (real-time coaching) is architecturally private to the seller and separate from the post-call analysis layer that privacy controls govern.

• Signals (cross-call intelligence) normally surfaces patterns by pulling insights across many calls. A private meeting's content is excluded from that aggregate pattern-matching for anyone outside its access list, which is the point — but it also means a genuinely useful signal buried in a private call won't surface to a manager who isn't on the list. That's a deliberate trade-off between visibility and confidentiality, not a bug.

• CRM and dialer integrations still log that a call happened, for pipeline and activity tracking, even when the underlying analysis is locked down.

How Spiky helps: the mechanics

• Three org-wide privacy modes. Strict Privacy requires explicit access-list membership for every user, including admins. Moderate Privacy keeps default access for admins but requires managers to be added explicitly. Privacy Disabled turns the feature off entirely — no meeting can be marked private.

• Per-meeting control, set any time. Once an org mode is on, any authorized organizer can mark a meeting private before it starts, mark a past meeting private retroactively, or reopen a previously private meeting.

• A safeguard against self-lockout. If someone tries to make a meeting private without putting themselves on the access list, Spiky is designed to flag it first so they don't accidentally lose their own access.

• Visibility without exposure. Non-authorized users can see that a private meeting exists (so it doesn't vanish from pipeline or calendar views) but can't open the transcript, recording, or participant details. Lock icons and dashboard filters (all meetings / accessible meetings / private meetings) are intended to make the access boundary visible at a glance rather than hidden.

FAQ

Does Private Meetings hide a call from admins too?
Only under Strict Privacy mode — there, even admins must be explicitly added to a meeting's access list to view it. Under Moderate Privacy, admins retain default access.

Can we retroactively lock down a meeting we forgot to mark private?
Yes — authorized users can mark a past meeting private after the fact, and can reopen it later if the sensitivity has passed.

Does turning off org-wide privacy delete existing private meetings' restrictions?
No — if privacy is disabled at the org level, no new meetings can be marked private and per-meeting controls become unavailable, but this changes what you can configure going forward rather than instantly re-exposing everything that was previously private.

Does marking a meeting private affect real-time coaching during the call?
No — Whisper's live, in-call nudges to the rep are designed to be separate from the privacy controls, which govern access to the post-call recording, transcript, and analysis.