Skip to content
MCPDial

Compliance · not legal advice

AI calling rules, enforced by the runtime.

Phone rules differ by country and the fines are real. AI disclosure, consent, calling hours and opt-outs are built into the call path of every AI phone agent — not left to a prompt or a policy page.

Start freeSee the rule table

consent ✓ · suppression ✓ · local hours ✓
then, and only then, dial()

Everywhere

6 rules every call follows

These run on every call, inbound and outbound, in every workspace. No prompt, agent setting or API flag switches them off.

01

AI disclosure, first sentence

Every call — inbound and outbound — opens by saying it is an AI assistant for your company. Enforced by the runtime (EU AI Act Art. 50, from 2 Aug 2026).

02

Opt-out the same turn

“Stop calling me” writes the number to suppression before the call ends, and the agent confirms it.

03

Calling hours per country and state

Outside the recipient’s window, a call is scheduled for the next open slot — never dialled.

04

Recording by jurisdiction

Where every party must consent to recording (e.g. DE, AT, FR, BE, PL), the agent asks first — or the call is not recorded.

05

Consent ledger

Consent, opt-outs and list hits are stored as append-only evidence: source, basis and time.

06

Data residency

Transcription, the model and the voice run in the workspace’s region — CH in Switzerland, EU in the EU — with no automatic cross-border fail-over. Call audio is carried by our media layer in the EU (Frankfurt).

By jurisdiction

Which calls are allowed where — at launch

The posture the dialler enforces for B2C, B2B, consented and inbound calls, with the public sources it is based on. Not legal advice; reviewed with counsel before general availability.

  • AllowedDialled once the always-on checks pass.
  • Consent onlyDialled only with a recorded consent.
  • Not without opt-inNot dialled without an opt-in or existing relationship.
  • Counsel reviewConsent by default until counsel signs off.
AI calling rules by jurisdiction and call type
JurisdictionB2C coldB2B coldWarm / consentedInboundCalling hours
DEGermanyUWG §7 · EU AI Act Art. 50
Not without opt-inPrior express consent (UWG §7).
Consent onlyAutomated / AI voice calls need prior express consent even B2B.
AllowedWith a consent record.
AllowedAI disclosure first.
Business hours, recipient-local
FRFranceLaw 2025-594 Art. 13 · EU AI Act Art. 50
Not without opt-inOpt-in required from 11 Aug 2026 (Law 2025-594), or an existing contract.
Consent onlyB2B scope under review — consent-only at launch.
AllowedWith documented consent.
AllowedAI disclosure first.
Weekdays 10–13 h and 14–20 h
CHSwitzerlandUWG Art. 3(1)(u)
Not without opt-inNot to starred directory entries or Robinson-listed numbers without a relationship.
Consent onlyUnder review — consent-only at launch.
AllowedWith a consent record.
AllowedAI disclosure first.
Business hours, recipient-local
UKUnited KingdomPECR · ICO B2B guidance
Counsel reviewTPS screening required; consent recommended.
AllowedAfter TPS + CTPS screening (every 28 days); caller ID shown.
AllowedWith consent or an existing relationship.
AllowedDisclosure recommended.
8–21 h recipient-local
USUnited StatesTCPA · FCC Declaratory Ruling (Feb 2024)
Not without opt-inPrior express written consent — AI voices are “artificial voice” under the TCPA (FCC, 2024).
Counsel reviewCounsel review; state laws vary — consent by default.
AllowedWith a consent record.
AllowedDisclosure required in some states (e.g. CA AB 2905).
8–21 h local; stricter in some states (e.g. OR 8–20 h)

Not legal advice. Sources are listed per row; your counsel decides what applies to your business. Planning outbound? Read how the AI sales caller handles consent.

Your workspace

Stricter if you want. Never looser.

The table above is the runtime minimum. Workspace rules can only tighten it.

  • Tighten calling hours below the local legal window.
  • Require a recorded consent everywhere, not only where the law does.
  • Disable outbound calling altogether and run inbound only.
  • Every consent, opt-out and list hit stays in the append-only consent ledger.

Every call leaves evidence

Sub-processors

Who processes call data, and where

MCPDial processes call data as your processor. These are the sub-processors involved and where they run. Data residency detail lives on the security page.

Sub-processors, purpose and region
Sub-processorPurposeRegion
phi-cloudInference gateway (STT, LLM, TTS), region-pinnedCH / EU / US
LiveKit CloudReal-time media transport and SIPEU (configurable)
TwilioPhone numbers and call termination (one subaccount per workspace)Per number; US-hosted account
TelnyxPhone numbers and call termination (alternative carrier)Per number
DeepgramStreaming speech-to-text during calls (model-improvement opt-out set)EU endpoint for EU/UK/CH calls; US otherwise
Fly.ioCall media worker (runs the voice agent)Frankfurt, Germany (EU)
SupabaseApplication database and authSwitzerland (eu-central-2)
CloudflareWeb hosting and API edgeGlobal edge
StripePaymentsEU / US

See security and Swiss data residency for the full call data path, and our privacy policy.

FAQ

Compliance questions

More in the calls & compliance FAQ.

Is this legal advice?
No. The table is the posture the product enforces at launch, based on public sources. Your counsel decides what applies to your business; you can make the rules stricter per workspace, never looser than the runtime minimum.
Can I turn the AI disclosure off?
No. The runtime speaks it before your greeting on every call. You choose the wording of the rest of the greeting.
What happens to a call outside the local calling window?
It is not dialled. It is scheduled for the recipient’s next open slot and placed by the scheduler then — after the consent and suppression checks run again.

Compliant by default, stricter if you want.

Workspace rules can tighten calling hours, require consent everywhere or disable outbound altogether.

Start freeSecurity & residency