Consent and calling compliance
Outbound calling, SMS, WhatsApp, and call recording carry consent requirements that vary by jurisdiction. What 11x provides, and what remains your responsibility.
Outbound calling, SMS, WhatsApp, and call recording all carry consent and disclosure requirements that vary by jurisdiction. 11x provides consented outbound calling capability, disclosure configuration, and per-channel controls — but the lawful basis for contacting a given person on a given channel is yours, not the platform's.
This page is not legal advice. Requirements differ materially by country, and in the US by state. Get sign-off from whoever owns compliance at your company before enabling calling or recording. The relevant 11x terms are the autodial terms and privacy policy.
Two things people conflate
Consent is channel-specific
Permission to email someone is not permission to send an automated SMS or place an automated call. Each channel has its own rules.
Consent is jurisdiction-specific
The same contact, the same channel, and a different country can produce a different answer. Geography is part of your targeting decision.
A form submission is not automatically consent to place an automated call. This is the single most common misconception in outbound setup. Someone requesting a whitepaper has not necessarily consented to an automated dialer, and in several jurisdictions that distinction is legally significant.
Where this applies in 11x
| Feature | Consideration |
|---|---|
| Consented outbound calling | Only enable where you have the required consent |
| Julian callbacks | An inbound form submission may not permit an outbound automated call |
| Multichannel — SMS, WhatsApp | Separate consent from voice and from email |
| Dynamic triggers | An internal CRM change is not consent from the contact |
| Call flows | Recording disclosure configured per your policy |
| Website visitor tracking | Tracking consent, plus lawful basis for subsequent outreach |
Configuring
Establish lawful basis per market and channel
Before enabling anything. Document the basis you're relying on for each combination.
Map consent state into the CRM
So exclusions can act on it. Consent that lives only in a marketing tool can't gate a call.
Set channel-level exclusions from consent state
A contact who consented to email but not calls must be excluded from call steps specifically, not the whole sequence.
Configure recording disclosure in the call flow
Where required. Some jurisdictions require all-party consent.
Honour opt-outs across every channel
An opt-out on one channel should be treated as authoritative rather than narrowly scoped.
Restrict geography where you lack basis
It's cleaner to exclude a market than to run a channel you can't justify there.
Mapping consent state into your CRM is the step that makes all of this enforceable. If consent isn't a field 11x can read, it can't be an exclusion — and then compliance depends on people remembering, which does not scale.
Do-not-contact and opt-outs
- Maintain a do-not-contact list and reference it in exclusions. See ICP and targeting.
- Treat an opt-out as global by default, narrowing only where you have a clear basis.
- Ensure opt-outs propagate to your CRM so they survive changes to your 11x configuration.
Recording, transcripts, and data handling
Every Julian call is recorded, transcribed, and summarized — which is what makes quality auditable, and also creates a data-handling obligation.
- Configure your disclosure notice per jurisdiction
- Consider who can access transcripts internally; they contain verbatim personal statements
- Avoid piping full transcripts into systems with broad internal access
- See security and data handling