Connect Attentive to SiteOps
A text gets read in minutes; an email waits in a folder. Attentive is where a lot of DTC brands already keep their SMS program — the subscribers, the opt-ins, the compliance. Connecting it lets SiteOps plan and send SMS to that program without moving it anywhere.
Once connected, SMS becomes a sendable channel for sequences and one-off sends. A day-2 reminder in a lifecycle sequence can go out as a text; a send-now message can reach your subscribers the same afternoon — every message riding the same queue as everything else, behind the trust dial you set for SMS.
Two honest notes. SMS is regulated and paid per message: SiteOps only ever sends to people already opted in through Attentive, and only what you approved. And the channel goes live once your Attentive registration is cleared — a one-time carrier review, not something SiteOps can hurry.
Set it up, step by step
0 of 4 done
- Audience
- Subscribers
- Settings
- API keys
- Settings
- Connections
- Attentive
If something does not work
- SMS won't send
- Almost always the Attentive messaging registration hasn't cleared yet — a one-time carrier review that gates delivery. Check its status in Attentive; until it's through, texts queue but don't deliver.
- A send was blocked as no-consent
- By design. SiteOps only sends to subscribers opted in through Attentive. A number that never opted in — or opted out — is suppressed, and the queue item says so. This keeps the channel compliant, not broken.
- Can SiteOps add subscribers or collect opt-ins?
- No — deliberately. Consent collection stays in Attentive, where the opt-in flow and records live. SiteOps sends to who's already opted in and never edits your subscriber list.