You sent a message campaign and the delivery count looks low. Triage in this order.
Step 1 — Confirm it actually sent
Open /messagecampaigns (Sent campaigns list). Find your campaign and check its state.
If it’s still in Draft, you didn’t complete the wizard. If it’s Scheduled for a future time, it’ll send then.
Step 2 — Check the segment
Open the campaign detail to see the segment that was selected at send time.
A small segment is the most common reason for low delivery counts. The segment selection happens in Step 2 — Select Lists of the create-message-campaign wizard.
Step 3 — Action alert vs message campaign
A common confusion:
- Message Campaign = a broadcast you composed and sent.
- Action Alert = automated trigger that fires only when a customer event happens.
If no customer has met the trigger condition for an Action Alert, it hasn’t fired — that’s expected. Check /actionalerts to confirm the alert is active and that recent customer activity matches its trigger.
What we don’t document precisely
- Per-message delivery stats (sent / delivered / opened / clicked) — the audited code shows the campaign list and detail flow but we haven’t enumerated which stats are surfaced where.
- Timezone behaviour for scheduled sends —
dateTimeis captured in the wizard but UTC vs local handling isn’t spelled out in the code we audited. - Member opt-in semantics — whether messages respect a marketing-consent flag, and how that flag is set on the customer side.
When to open a ticket
If delivery looks materially wrong (e.g. you sent to 200 selected, 0 delivered) or status is stuck on "processing" for more than an hour, open a ticket with the campaign name and approximate send time.
In one sentence
Confirm the campaign sent (not draft / scheduled) → check the segment selected → make sure you didn’t mean an Action Alert.