Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Manage consent, unsubscribe and suppression

Consent, reachability, and sender readiness are separate checks. A valid address can still be unsubscribed, suppressed, or ineligible for a marketing audience. A reachable WhatsApp number does not prove the customer opted in.

Channel preferences

Preferences are channel-specific for email, SMS, and WhatsApp, with states including unknown, subscribed, unsubscribed, and suppressed. A customer's email preference should not be silently treated as WhatsApp or SMS consent.
Marketing segment audiences require affirmative consent. Suppression, unsubscribe preferences, legacy suppression timestamps, blocked contact status, and missing addresses are honored. Eligibility is rechecked at delivery even if the segment preview previously included the contact.

Record permission accurately

Capture consent at the source, such as a signup form or documented customer request. Keep the requested channel and purpose clear. Only use API fields such as whatsapp_opt_in: true when they reflect actual permission.
Imports do not manufacture permission. Review what consent your source data actually records before launching a campaign. Buying or receiving a list is not equivalent to customer subscription.

Unsubscribe and suppression

Email unsubscribe stops future eligible sends through Convert's preference and suppression checks. Hard bounces and complaints can suppress an address before later submissions. Sender changes, list copies, or new templates should not be used to evade these checks.
Transactional purpose remains subject to policy. The current SMTP flow is transactional and retains global unsubscribe and suppression behavior. The API's purpose field is not an override for blocked destinations or sending restrictions.

Work with previews and duplicates

A segment preview is an estimate, not a promise of immediate delivery. Preferences can change between preview, audience expansion, and sending. Campaign expansion deduplicates normalized destinations, and the delivery flow considers suppression across duplicate destination records.
Next: collect signups using forms, inspect segments, or review deliverability.
Retain useful history. Prefer changing messaging preferences over deleting a contact when the customer no longer wants messages.