Skip to main content

Messaging rules and beta caveats

Messaging rules​

CheckHow it applies
DNCLists without a channel apply everywhere; sms or whatsapp lists apply to their channel only
Consent (marketing category)Requires a consent date less than a year old, or an existing customer; otherwise the lead is excluded as no_consent or consent_expired. Not checked for utility
Sending windowThe same callingWindows, in the lead's time zone, and the contact-center calendar if one is linked
National call registryNot applied: it covers calls
Attempt limitmaxAttemptsTotal, as for voice

The consent rule reflects a reading of the Israeli Communications Law, section 30A (the anti-spam provisions). Confirm it legally before production use. See also Compliance and calling hours.

Send failures​

FailureWhat the dialer does
Permanent error (4xx), for example "from address must be a valid sender"The batch is marked failed, the leads are put back and the campaign is paused (every next batch would fail the same way). The error shows in the live view: "Sending is paused: Twilio rejected the last batch".
Transient error (5xx, network)The leads are put back and the campaign tries again after 60 s. A request that timed out is never resent, because Twilio may already have accepted it.
Unknown outcomeIf the service restarts after sending a batch but before Twilio's answer arrives, after 5 minutes the batch is treated as not sent and its leads are put back. In that case a message may arrive twice.

The Bulk Messaging API is a public beta​

  • No SLA, and response shapes may change.
  • Sender validity is opaque: a number that sent to a country yesterday may be refused for every destination today. The campaign pauses on the first refusal; check the senders list in the campaign form.
  • Per-sender MPS limits apply on top of the campaign's own pace.
  • Opt-out handling is the dialer's, not Twilio's.
  • Per-message error codes are not fully documented by Twilio, so some failures may show without a specific reason.