Legal

Call Recording & AI Voice Disclosure

Effective Date: September 8, 2026  ·  MF Automations LLC

This page explains how MF Automations handles call recording and automated voice, and what customers must do to deploy an AI Operator lawfully. It is incorporated into our Terms of Service by reference.

Florida is an all-party consent state

Fla. Stat. § 934.03 makes intercepting or recording a wire or oral communication without the consent of every party a third-degree felony, and Fla. Stat. § 934.10 creates a private civil action. Roughly a dozen other states have comparable all-party rules, including California, Illinois, Pennsylvania, Washington, and Massachusetts. An AI Operator that answers a business phone records people who never agreed to anything in advance.

1. What we record

Where recording is enabled for an account, the Services capture audio of inbound and outbound calls handled by the AI Operator, generate a text transcript, and derive summaries and structured data from it. Recording can be disabled entirely at the account level, and can be suppressed for individual calls where the caller objects.

2. Consent is the deploying business's responsibility

MF Automations supplies the recording capability and the disclosure tooling. The business that deploys an AI Operator decides who it talks to and is responsible for obtaining every consent the law requires. That business must:

  1. Announce recording at the start of every call, before any substantive conversation, using the disclosure language below or equivalent wording;
  2. Give the other party a genuine way to decline — a route to a live person, a callback, or an unrecorded line;
  3. Honor a request to stop recording immediately;
  4. Apply all-party consent standards to any call where either party may be in an all-party state, or where the location is unknown. The safe default is to treat every call as all-party.
  5. Disclose the same on any outbound campaign, and comply with the TCPA and state telemarketing law for the call itself.

3. Disclosing that the caller is talking to an AI

Separately from recording, several states require disclosure that a person is communicating with a bot rather than a human in certain contexts — California's B.O.T. Act (Cal. Bus. & Prof. Code § 17940 et seq.) where the intent is to incentivize a sale or influence a vote, and Utah's AI disclosure requirements on request, among others. Federal rules treat AI-generated voice as an artificial voice for TCPA purposes, which means outbound calls using it generally require prior express consent, and prior express written consent when the content is marketing.

Our standing requirement, regardless of state: every AI Operator must identify itself as automated within its first turn. We do not support configurations that claim to be a named human being.

4. Standard disclosure language

Use these as written, or have counsel adapt them. Bracketed values are filled from your account configuration.

Inbound call — combined recording and AI disclosure

"Thanks for calling [BUSINESS NAME]. You're speaking
with an automated assistant, and this call is recorded
for quality and accuracy. If you'd rather not be
recorded, just say 'no recording' and I'll get you
to a person."

Outbound call — disclosure plus identification

"Hi, this is an automated assistant calling on behalf
of [BUSINESS NAME] about [REASON]. This call is
recorded. Is now a good time?"

Caller declines recording

"No problem - I've stopped the recording. Let me take
a message and have someone call you back, or I can
transfer you now."

Caller asks whether they are talking to a person

"I'm an automated assistant, not a person. I can
handle this for you, or connect you to someone on
the team - whichever you prefer."

5. Sensitive calls

Do not deploy an AI Operator to record calls that are privileged or specially protected — attorney-client communications, medical consultations covered by HIPAA absent a Business Associate Agreement, or calls collecting payment card data — without a separate written agreement with us covering that use.

6. Access, retention, and deletion of recordings

Recordings are retained for 90 days by default and then deleted; transcripts persist for the life of the account unless configured otherwise. Access is limited to the deploying business and to MF Automations personnel who need it to support or secure the Services. A caller who wants a recording deleted should contact the business they called; that business can delete it from their account, and we will honor a documented request forwarded to us.

7. Questions

Email [email protected].

This page describes contractual allocations between MF Automations and its customers. It is not legal advice to any business about its own recording obligations, which depend on where its callers are located.

MF Automations LLC · 233 NE 27th St, Miami, FL 33137 · [email protected] · (305) 965-9624