Filter customer context
Audience presets can use customer and job context; available audience size remains bounded by CRM data and plan capacity.
Email and SMS campaigns
Build campaigns from permission-aware customer context.
Audience previews use CRM filters and opt-out exclusions; campaigns are text-only today and remain subject to consent, provider capacity, and plan limits.
Campaign audienceSafe CRM preview
SMS1 Audience filters
Job or customer recordService customers with SMS permission
First name and last service are available
Exclude opt-outs visibly
The preview exposes opt-out exclusions before confirmation; recorded consent is still required for the selected channel.
Review before queueing
Drafts, merge fields, confirmation, and queue state are inspectable; text delivery depends on provider readiness and capacity.
Build a bounded campaign audience
The illustrative flow keeps Ava Brooks excluded because marketing SMS permission is not granted, then stops before any send.
- 01
Filter customer context
Audience presets can use customer and job context; available audience size remains bounded by CRM data and plan capacity.
- 02
Exclude opt-outs visibly
The preview exposes opt-out exclusions before confirmation; recorded consent is still required for the selected channel.
- 03
Review before queueing
Drafts, merge fields, confirmation, and queue state are inspectable; text delivery depends on provider readiness and capacity.
- 04
Campaigns can send text when consent and provider readiness are satisfied.
Campaigns are text-only today; MMS Studio attachments are not supported.
Change filters, keep exclusions visible
Switch the local audience preset to inspect filter state; the demo sends nothing and keeps opt-out handling visible.
Campaign audienceSafe CRM preview
SMS1 Audience filters
Job or customer recordService customers with SMS permission
First name and last service are available
Demo workspaceProduct evidence
Permission is part of the product
The demo proves inspectable filtering, count, exclusion, and text-only states; it does not prove delivery, response, or revenue.
- Filter customer context
Audience presets can use customer and job context; available audience size remains bounded by CRM data and plan capacity.
- Exclude opt-outs visibly
The preview exposes opt-out exclusions before confirmation; recorded consent is still required for the selected channel.
- Review before queueing
Drafts, merge fields, confirmation, and queue state are inspectable; text delivery depends on provider readiness and capacity.
- Campaigns can send text when consent and provider readiness are satisfied.
Campaigns are text-only today; MMS Studio attachments are not supported.
Review the operating boundaries.
Open each question to inspect the mechanism, dependency, or plan condition beside the capability it qualifies.
Filter customer context
Audience presets can use customer and job context; available audience size remains bounded by CRM data and plan capacity.
Exclude opt-outs visibly
The preview exposes opt-out exclusions before confirmation; recorded consent is still required for the selected channel.
Review before queueing
Drafts, merge fields, confirmation, and queue state are inspectable; text delivery depends on provider readiness and capacity.
Guided beta onboarding
Start with the workflow you run today.
Use guided beta onboarding to map the workflow, provider connections, permissions, plan gates, and review steps before launch.