Skip to main content
Consent & Compliance controls how marketing opt-outs are enforced across a workspace. Suppression enforcement is always active. Workspace owners and admins configure the mode under Settings → Data → Suppression; other members have read-only access.
Consent mode selector with universal and per-channel opt-out options

Settings → Suppression → Consent & Compliance: choose Universal Opt-Out or Per-Channel Opt-Out, then select Save changes.

​
Universal opt-out

An opt-out received on any channel blocks marketing outreach to the linked contact on voice, SMS, email, and supported messaging channels. Universal mode is the conservative default and remains available on every plan.

​
Per-channel opt-out

An opt-out applies only to the originating channel. For example, an SMS opt-out blocks SMS marketing while independent voice or email consent can remain usable. Per-channel mode requires the Consent & Compliance plan feature. If that feature is unavailable, the workspace remains in universal mode; suppression enforcement is never disabled.
Changing the workspace mode does not rewrite earlier opt-outs. The rule that applied when the contact opted out remains visible in the audit history.

​
Suppression records

Add contact suppression form with phone number, optional reason and Add

Settings → Suppression → Add contact: enter the phone number and an optional reason, then choose Add to exclude it from campaign dialing.

An active record can be linked to a contact, phone number, or email address. It shows the affected channels, where the request was received, its reason, and when it was created. Listing with a channel filter returns both that channel’s records and universal (all) records, because both block outreach on the requested channel. Restoring consent does not erase compliance history. The active suppression is revoked and an opt-in event is appended to the audit trail. Use the suppression record ID whenever possible. The API also accepts a URL-encoded E.164 phone number or email address.
Only restore consent when you have an appropriate, documented basis to do so. Product settings assist with enforcement but do not replace legal review for your jurisdiction, outreach purpose, and communication channel.
This section is general information, not legal advice. Marketing and telemarketing rules vary by country and channel — confirm your specific case with legal counsel before launching a campaign.
Voice, SMS, and email outreach are regulated wherever you call or message into, not just where your workspace is based. A few frameworks come up most often: Practical baseline regardless of region: keep a documented basis for each contact (consent record, existing relationship, or legitimate interest), make opting out easy and immediate, and keep the audit trail suppression records already provide. Pair this with your workspace’s data retention settings so contact and consent records aren’t kept longer than needed. For outbound calling specifically, see Dialer, retries & compliance.

​
AI disclosure requirement

Since August 2026, the EU AI Act’s transparency obligation (Art. 50) requires that people be told when they’re interacting with AI — for example an AI voice assistant on a call — unless it’s obvious from context. A short, clear line is enough, such as telling the caller up front that they’re speaking with an AI assistant. For workspaces whose AI inference region is EU, Famulor reviews this automatically after an assistant is saved. Consent wording, the effective greeting, and the opening prompt are assessed together. One clear AI introduction in any of those active sources is sufficient; the disclosure does not need to be repeated in every source. Uploaded audio greetings are checked from their transcription. A missing disclosure blocks the assistant until the opening is corrected or approved through compliance review.
The simplest way to comply is to have your assistant say so as part of its opening — see Prompt writing for structuring an assistant’s greeting. If your assistant uses a cloned voice, a related but separate labelling duty also applies — see Voice cloning consent.

​
REST API

Read or update the workspace mode:
Record an opt-out:
The suppression API accepts at least one of contact_id, phone, or email. When channel is omitted, phone defaults to voice and email defaults to email. Use GET /api/v1/suppression-list?channel=sms to list records that block SMS. Restore one record with DELETE /api/v1/suppression-list/{id-or-identity}. REST scopes are settings:read / settings:write for the mode and suppression:read / suppression:write for records.

​
MCP

  • get_consent_mode and set_consent_mode;
  • list_suppression_entries;
  • add_suppression_entry;
  • remove_suppression_entry (restores consent and retains the audit trail).
MCP follows the same permissions and returns the same customer-facing data as the REST API.