Customer Says No Recording. What Are Your Options?

TL;DR

• Stop first, clarify second. What a customer prohibits is often narrower than no recording, but that is not an assumption to make mid-objection.
• Bot-free creates no exemption. The absence of a visible participant does not change what was agreed or what rules apply.
• Law and organisational policy are separate checks, and the stricter of the two governs regardless of which you consulted first.
• A factual description of what the tool does beats a blanket promise you may not be able to keep.

A customer says they do not want the meeting recorded. The seller's next job is straightforward: respect the boundary and keep the conversation useful.

Do not start a debate about whether a transcript technically counts as a recording. Explain what the tool does, clarify what the customer permits and stop anything outside that permission.

A desktop assistant, native meeting integration or transcript-only mode can change the technical behavior. It does not decide the customer's policy or the law that applies to the conversation.

This article provides operational guidance, not legal advice. Have the appropriate legal, privacy or security owner approve the process for your organization and the jurisdictions involved.

Stop first, clarify second

If capture is already running, pause the sensitive discussion and stop the relevant function. Confirm the application state rather than assuming that hiding its panel or closing a notification stopped it.

Magic Screen's meeting guide distinguishes its record/stop controls from show/hide controls. It describes automatic detection and recording/transcription behavior, so users need to understand those controls before a restricted call. 1

For a bot-based assistant, use the provider's supported stop or removal procedure. For desktop capture, the person running the application needs to stop it there. A clean participant list does not prove that every participant's local software stopped receiving the conversation.

Once the disallowed activity has ended, clarify the customer's requirement without pressuring them to approve a different label for the same practical concern.

Clarify what the customer prohibits

Different restrictions can cover different things:

These questions help establish scope. They should not become a negotiation designed to wear down a refusal.

If the customer says no automated capture or AI processing, use that boundary. If they are unsure, continue with an approved fallback while the relevant owners resolve the question outside the call.

Keep the language factual. Describe the actual capture, processing and retention behavior you have verified. Do not promise local-only operation, no storage or no third-party access because the application looks unobtrusive.

Bot-free does not establish an exemption

Bot-free describes how the assistant participates or receives meeting information. It does not establish whether a transcript is created, where processing happens or what content remains afterward.

Fathom's documentation illustrates the distinction by offering different capture modes, including transcript-only and audio-only choices. The selected mode changes the artifacts, but it does not tell you what a particular customer has authorized. 2

Magic Screen's privacy policy and meeting documentation address meeting data and recording/transcription. Those are the materials to review when describing the product's behavior. Do not replace them with an assumption that native software creates no record. 3 1

A customer may be concerned about the information leaving the conversation at all. Renaming the resulting artifact from recording to notes will not answer that concern.

Law and organizational policy are separate checks

California Penal Code section 632 addresses certain recording and eavesdropping involving confidential communications without all parties' consent. The statute includes definitions and exceptions; its application depends on the circumstances. It is not a universal description of every meeting in every jurisdiction. 4

Organizational rules can be more specific about the tools and use cases they permit. UC Davis, for example, publishes guidance that covers AI meeting functions as well as recording and calls for approved tools and appropriate participant notice and consent. That is an institutional policy example, not a nationwide rule for all businesses. 5

For a sales organization, the practical step is to obtain an approved policy before asking each rep to improvise. Have the policy address capture modes, customer restrictions, sensitive information, disclosure, retention and the escalation path when the answer is unclear.

Cross-border meetings, regulated information and contractual restrictions deserve qualified review. A tool's marketing page should not be the authority deciding whether a particular call may be processed.

Use a factual disclosure, not a blanket promise

A disclosure should describe the actual proposed behavior and give people a meaningful way to object under the approved process.

Here is a drafting framework for internal review. It is intentionally incomplete until the organization supplies verified facts; it is not a universal consent script.

We propose using [approved tool] for [specific purpose].

It will capture or receive [verified inputs].
It will create [verified artifacts].
Processing and storage follow [approved description or policy].
Access is limited according to [verified controls].
Retention follows [applicable approved terms].

Please let us know if this is not permitted for this conversation.
We will use [approved alternative] when automated capture is not allowed.

Do not say that continuing the meeting automatically resolves every legal or policy requirement. Use the process your organization has approved for the actual participants and situation.

If the product behavior is unclear, resolve it before using the feature on a sensitive call. An accurate, narrower description is better than a broad reassurance the seller cannot substantiate.

A manual fallback that still produces useful notes

When manual notes are permitted, use a small structure that supports the next step without attempting to capture every sentence.

Record the customer's priority, material requirements, confirmed decisions and agreed actions. Put unanswered questions in their own section. Mark missing owners or dates rather than filling them from memory later.

At the end of the call, read the important commitments back to the participants. That gives them a chance to correct the record and reduces dependence on a complete transcript.

An approved manual process might use:

Customer priority:
Requirements discussed:
Confirmed decisions and conditions:
Actions, owners and stated dates:
Open questions:
Items to confirm before sending a follow-up:

Keep those notes in an approved location. A restriction on external AI processing may still apply when a person types the notes themselves. Do not assume that manual capture authorizes a later upload to any summarization service.

Handle accidental capture without making unverifiable promises

If capture began before the objection, establish what happened. Identify the application, meeting, time range and artifacts that may have been created.

Ask the relevant owner to confirm saved content, access, distribution and available deletion actions. Stopping a live session should not be treated as proof that everything previously collected has been erased.

Follow the organization's incident or privacy process where applicable. The person speaking to the customer should distinguish what has been completed from what is being checked.

For example, "Capture has stopped, and our privacy owner is verifying the saved artifacts and deletion request" is more precise than claiming all data is gone before anyone has confirmed it.

Avoid distributing the accidental content while investigating it. Restrict access through the available approved controls and preserve any records your organization requires for handling the issue.

Prepare for restricted calls before joining

A sales team can make this easier operationally.

Include capture restrictions in the account's approved meeting guidance. Review automatic detection and calendar-join settings before a sensitive session. Make sure the rep knows the difference between pausing display, stopping capture and deleting saved content.

Check any other assistant the team uses. Turning off one application does not change a colleague's tool or a meeting-platform feature.

Where a recurring customer meeting prohibits capture, use a durable approved configuration rather than relying on someone to remember a last-second click every time. Retest after meaningful configuration changes.

Accessibility needs may require a separate authorized process. Work with the relevant internal owner to establish an appropriate accommodation rather than treating this article as a reason to deny one.

Magic Screen should fit the approved process

Magic Screen can reduce repetitive meeting work through its live resources and reusable outputs when the use is permitted. It should not be positioned as a way to bypass a customer's recording or processing restriction.

For a restricted call, the right decision may be to keep automated capture off and use approved static materials and manual notes. That protects the customer relationship and avoids creating a record the parties did not authorize.

Review the Magic Screen meeting controls before the next call. Pair them with the sharing checklist and your organization's approved policy. The seller should be able to explain the tool accurately, stop it confidently and continue the meeting without making the customer's boundary a problem.

In-person capture is the same question again

Recording a conversation in a room carries the same obligations as recording a call, and sometimes stricter ones, since consent rules can turn on where each person is physically sitting. This matters more now that phone and watch capture is common across the category — the tool being bot-free or wearable changes nothing about what was agreed.

MagicScreen's companion apps never start on their own; capture is always a deliberate act. The disclosure guidance in this article applies unchanged.

Frequently asked questions

A customer says no recording. Can I still use an AI notetaker?

Stop first and clarify second. What is prohibited is often narrower than no recording, but that is not a judgement to make while the objection is live.

Does bot-free mean I am exempt from a no-recording request?

No. The absence of a visible participant does not change what was agreed or which rules apply.

What should I tell the customer?

Describe factually what the tool does and does not do. A blanket promise you cannot verify is worse than a precise description of the actual behaviour.

Sources

1. Magic Screen. Meeting Detection and Recording. Checked September 10, 2026.
2. Fathom. Fathom 3.0. Checked September 10, 2026.
3. Magic Screen. Privacy Policy. April 19, 2026. Checked September 10, 2026.
4. California Legislature. Penal Code section 632. Checked September 10, 2026.
5. UC Davis Privacy. Recording meetings. Checked September 10, 2026.