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.

Automatic blocking after calls

Change this setting below Consent Mode, then select Save changes. It is on by default. Turning it off skips automatic opt-out detection after calls. Existing and manual blocks and opt-outs in other channels still apply. Read this setting with famulor get-automatic-call-suppression. Turn it off with famulor update-automatic-call-suppression --automatic-call-suppression=false. The MCP tools are get_consent_mode / set_consent_mode.

Suppression records

Add contact form with phone number, Direction, optional reason and Add to suppression list

Settings → Suppression → Add contact: enter the phone number, choose a Direction and an optional reason, then select Add to suppression list.

An active record can be linked to a contact, phone number, or email address. It shows the affected channels, its direction, where the request was received, its reason, and when it was created. Listing with a channel filter returns that channel’s records and universal (all) records in every direction, so Inbound only records can appear. Add direction=outbound to list only Outbound only records.

Direction

Each record has a Direction. Choose it in the Add contact form under Settings → Data → Suppression: Inbound blocking applies to the phone number or email address on every channel, regardless of the record’s channel:
  • Phone number: incoming calls are hung up right away, before the assistant answers. SMS, RCS and WhatsApp messages (text and voice notes) get no AI reply, and incoming WhatsApp calls are declined.
  • Email address: incoming emails get no AI reply.
Blocked calls appear in History as failed calls with the reason Blocked caller. Blocked messages stay visible in History. Blocked calls use no minutes, and blocked messages get no AI reply, so no reply is charged. Incoming SMS and RCS on Famulor numbers still cost the normal receive fee. Web chat, web voice and the website widget are not affected, because their visitors have no phone number or email address to match. The channel of a record only limits outbound contact. Opt-outs recorded automatically, such as an SMS STOP, a spoken request not to be called again, an email unsubscribe or a CSV import, are always Outbound only. An opt-out therefore never blocks a contact from reaching you. If a record already exists for the same contact with a different direction, adding the new one updates it to Inbound and outbound instead of creating a second record. To change an entry, select the pencil next to it. The Add contact card above switches to Edit entry: choose another Direction or change the reason, then select Save changes. In Audience, use the pencil on the Block List (DNC) tab, or open a contact and choose Block list under More actions. Every direction change is recorded in the consent history. Restoring consent does not erase compliance history. The active suppression is revoked and an opt-in event is appended to the audit trail. Removing a record from the list, through the dashboard, the API, MCP or the CLI, removes it completely, including an inbound block. An automatic opt-in, such as an SMS START or the Remove from blocklist automation step, only lifts the outbound part: an Inbound and outbound record becomes Inbound only, and an Inbound only record stays in place. 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.

Federal and State DNC Checks (US)

US telemarketing rules require checking numbers against the FTC National Do Not Call Registry and some state registries. These checks run under your business’s own registry account, identified by its FTC Org ID and Subscription Account Number (SAN). If you don’t have them yet, register at telemarketing.donotcall.gov.
1

Open the card

Go to Settings → Data → Suppression and find Federal and State DNC Checks.
2

Turn the checks on

Turn on the switch. The FTC Org ID and Subscription Account Number (SAN) fields appear.
3

Save your registry access

Enter both identifiers and select Save changes. Each one has 3 to 40 letters, digits or hyphens.
Workspace owners and admins change the checks. Other members see the setting read-only, with only the last four characters of the SAN.

What waits while verification is pending

After you save, the card shows Pending verification. Until your registry access is verified, the workspace places no proactive call to a US number:
  • Campaign leads with a US number stay in the campaign, keep their attempts and show as Rescheduled. The dialer looks at them again every 15 minutes.
  • Calls from the dashboard, the API, MCP or the CLI to a US number are refused with a message that says why.
  • Scheduled callbacks to a US number wait.
Your own suppression list is still checked first. Canadian, Caribbean and other non-US numbers are not affected, and neither are inbound calls. When you turn the checks off, waiting contacts are dialed again at the next dialer run. The Org ID and SAN stay saved. Read or change the checks from the API, CLI or MCP:
The MCP tools are get_dnc_registry_checks and set_dnc_registry_checks. Responses show only the last four characters of the SAN. The scopes are settings:read and settings:write; user-owned credentials also need the owner or admin role to change the checks.
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:
Block incoming calls and messages from a number:
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. direction accepts outbound (default), inbound or both, and every record in a response includes it. inbound and both need a phone or email. GET /api/v1/suppression-list?channel=sms lists SMS and universal records in every direction; add direction=outbound to list only outbound blocks. GET /api/v1/suppression-list?direction=inbound lists only records with that exact direction. Change the direction or reason of a record with PATCH /api/v1/suppression-list/{id} and a body such as {"direction":"both"}; every direction change is recorded in the consent history. Remove 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.

CLI

MCP

  • get_consent_mode and set_consent_mode;
  • list_suppression_entries (optional direction filter);
  • add_suppression_entry (optional direction, default outbound);
  • update_suppression_entry (change direction and/or reason by record ID);
  • remove_suppression_entry (removes the whole record, including an inbound block, and retains the audit trail).
MCP follows the same permissions and returns the same customer-facing data as the REST API.