Agoralia docs
Compliance

Compliance overview

Recording is optional and enforced per country, in-call disclosure is added only where the law requires it, DNC is respected, and an attestation is signed before launch. This is the moat.

Compliance

Compliance isn't a checkbox you tick — it's enforced at the gate, on every surface, before a call is placed. This is the core of what Agoralia is: the encoded rules that let you hand voice campaigns to an AI agent without it calling the wrong people, the wrong way, in the wrong country.

Recording — optional, enforced per country

Recording is optional and controlled by recording_enabled on the agent, call, or campaign. It is then enforced per destination country, resolved from the called number's prefix:

  • Some countries forbid recording — it is auto-disabled there even if you requested it. No audio is stored, but transcript, summary, and structured_data are still produced.
  • Some countries require a spoken recording notice — when recording is on and the country mandates it, Agoralia announces the notice automatically at the start of the call.
  • A call can disable recording, but never force it on where the jurisdiction forbids it.

The API returns a structured recording advisory so callers are guided, not silently overridden.

In-call disclosure layer

The disclosure layer is minimal — "not required means not said". A line is spoken only where the law requires it for the destination country. Three components compose into one decision:

  1. AI disclosure — telling the person they're talking to an AI. Required per a country's own rule, and across the EEA under EU AI Act Art. 50 from 2026-08-02.
  2. Purpose disclosure — stating why you're calling, under GDPR / UK-GDPR Art. 13. Whether it applies depends on the campaign's purpose.
  3. Recording notice — spoken only when recording is on and the country mandates a notice.

AI disclosure and the recording notice are spoken natively by the voice layer; the purpose line is injected into the call's opening.

DNC

Do-not-call suppression is respected automatically. Opt-outs are honored, and a number on your DNC list is rejected before any call — both for single calls and campaign launches. Manage entries from Manage leads.

Attestation before launch

Before a campaign can launch, a compliance attestation (declaration) must be signed. This is part of the launch pre-flight: a campaign that isn't attested — or isn't compliant for its target countries — cannot launch. The gate blocks it and tells your agent exactly what's missing.

Call types (purposes)

The campaign purpose sets how strict the rules are:

  • quote_request, survey, appointment — buying-inquiry-like, lighter regime.
  • cold_calling — telemarketing, the strictest regime.

Check before you build

MCP
list_available_countries()        # where Agoralia can place calls
list_compliant_countries()        # where you're cleared to run, given your setup
get_compliance_status()           # gaps for your workspace + how to close them
get_attestation_status()          # is the launch attestation signed?

Errors are instructions

When a country isn't cleared, the response names the missing requirement and the next step — not a bare 403. Close the gap (e.g. add a disclosure, sign the attestation) and re-check.

Next steps