Compliance: consent, do-not-call, disclosures and Shabbat

Israel’s Communications Law (§30A, the “spam law”) governs marketing calls, and it applies to calls an AI makes just as it does to people. MoreVoice builds the rules into the dialer: every outbound call leg passes one compliance decision before it is placed, whether a campaign dials it, the AI places it, a person dials it, or it is a transfer, consultation or added participant.

You are the advertiser

MoreVoice gives you the controls and keeps the records. Under §30A the business that makes the call is the advertiser and stays responsible for having consent and for the content of its calls. This page explains how the product behaves; it isn’t legal advice. Have counsel review your use.

The call’s purpose

Every outbound call has a purpose, and the purpose decides which checks run:

Check	marketing	service	survey
Internal do-not-call list	Blocks	Blocks	Blocks
§30A consent on record	Required	—	—
National do-not-call registry (Israeli numbers)	Blocks registered numbers	—	—
AI and recording disclosure	On by default	Optional	Optional

A campaign has one purpose for all its calls. A call placed by the AI or by a person is a service call unless it says otherwise. Destinations that aren’t phone numbers (a SIP address or an internal extension) aren’t checked against the lists.

The decision, step by step

1. Internal do-not-call list. If the number is on your list, the call is blocked, whatever its purpose. If the list can’t be read, the call is blocked too: MoreVoice never dials when it can’t check.

   A supervisor can allow one call to a listed number, placed by a person or by the AI at a person’s request, within the next 30 minutes and with a written reason. The override is recorded in the audit log, and it never applies to campaigns or to the national registry.

2. Consent (marketing only). The number needs an active marketing consent record. Campaigns check consent per contact, from the consent column of the import or a consent record; contacts without it are skipped with the reason no-consent. This can’t be turned off.

3. National registry (marketing to Israeli numbers only). Once you connect the registry in National do-not-call registry, MoreVoice checks marketing numbers against it:

   • a registered number is blocked;
   • an answer is reused for up to 14 days (configurable up to 15, the legal limit) and checked again after that;
   • an hourly pre-flight checks the next 24 hours of campaign contacts ahead of time, so dialling rarely waits;
   • if the registry can’t answer and there is no recent answer, the call is blocked by default (Block when the registry can’t answer).

A blocked call isn’t placed. It is written to the audit log (outbound.blocked, with the reason dnc, no-consent, registry or registry-unavailable), and the app’s dial request answers 403.

Available with /v1

In the public API a blocked call will return an error of type compliance_error, and POST /v1/calls will require a purpose. The do-not-call list and consent records will be available at /v1/dnc and /v1/consents.

Do-not-call list

The list is checked when a contact list is imported and again right before every dial, because a number may have been added in between. Adding a number also takes it out of every campaign where it is still waiting to be called.

Numbers reach the list by hand, from an imported file, through the API, or when the person on a call opts out (below). You manage the list under SettingsCompliance.

Opt-out during a call

On campaign calls, people can ask not to be called again in three ways:

• Saying it. A list of opt-out phrases (“תורידו אותי”, “הסירו אותי”, “אל תתקשרו אליי” and more) is matched in what the person says, ignoring punctuation and niqqud. “לא להסיר אותי” is not an opt-out.
• Pressing a key. 9 by default; a campaign can choose its own key.
• Asking the AI in other words. The AI agent has an opt-out tool for wordings the phrase list doesn’t cover.

Any of the three adds the number to the do-not-call list at once, speaks a confirmation (“בסדר גמור, הסרנו את המספר שלך מרשימת החיוג…”), ends the call, and records the outcome. Your webhook endpoints receive a dnc.added event.

Disclosure

On campaign calls, the AI can say a disclosure line before its first message. The default is “שלום, זוהי שיחה ממערכת בינה מלאכותית, והשיחה מוקלטת” (“Hello, this is a call from an artificial-intelligence system, and the call is recorded”). It is on by default for marketing campaigns; service and survey campaigns can turn it on, and you can change the text.

Calling hours, Shabbat and holidays

Campaigns dial only when every time rule allows it:

• Global calling hours, which no campaign can exceed. The default is Sunday to Thursday 08:00–21:00 and Friday 08:00–14:00, Israel time.
• The campaign’s own windows, in each contact’s time zone. They can only narrow the global hours.
• Shabbat and Yom Tov. No calls from candle lighting until havdalah, on the Israeli calendar, with an extra margin before candle lighting (60 minutes by default). Multi-day holidays next to Shabbat count as one period.
• The campaign’s start and end dates.

When a rule says no, the dialer waits for the next moment every rule allows. A campaign whose windows never overlap the global hours in the next three weeks can’t start. Scheduled callbacks follow the same calling hours unless you give them their own.

Where it is configured

Setting	In the app
Calling hours, Shabbat and holiday rules, disclosure, opt-out phrases and key, do-not-call list	SettingsCompliance
National registry connection and its policy	SettingsComplianceNational do-not-call registry
A campaign’s purpose, windows, disclosure and opt-out key	The campaign’s setup