Launching campaigns from the CLI

crispy campaign launch <campaign-id> is the safe way to turn on outreach sending: it previews before anything goes out.

What the preview shows

1. The campaign name and a summary of the attached contact list (count plus sample names).
2. Block list hits: contacts who will be skipped because they are on your do-not-contact list.
3. Duplicate hits: contacts you have already invited, checked against your invitation history.
4. Sample first-touch messages rendered for real contacts, so you see exactly what the first recipients will receive, with template variables filled in.

After the preview, the CLI asks 'Confirm launch? [y/N]'. Nothing is sent until you answer y.

Skipping the preview

crispy campaign launch my-campaign --skip-preview

This confirms immediately. Reserve it for scripts where the campaign was already previewed.

After launch

Sends do not fire instantly. Crispy spreads the daily budget across the day in randomized slices and respects the sender's business-hours window, so expect a steady drip rather than a burst.

Check progress with:

crispy campaign state my-campaign

It returns the funnel (queued, sent, accepted, replied, with acceptance and reply rates), stall information with a reason, and the last run time. crispy campaign stats my-campaign adds performance metrics.