Scheduling, recurring sends and A/B tests
Send later, repeat on a schedule, compare message variants and track link clicks.
Scheduling a send#
In step 3 of the composer, pick a date and time in Nairobi time. Leave it blank to start as soon as approvals and quiet-hours checks allow. Quiet hours (21:00 to 07:00 by default) always apply to promotional messages.
Recurring sends#
To repeat a message on a schedule, open a send you have already sent and choose Repeat this send.
| Option | Example |
|---|---|
| Daily | Every morning at 08:00 |
| Weekly | Mondays and Thursdays at 18:00 |
| Monthly | The 1st of every month |
| Custom | A cron expression; the minimum interval is one hour |
Set the first occurrence and, optionally, an end date. Each occurrence becomes a fresh send with its own approval, suppression, quiet-hours and wallet checks, so a person who opted out last week is never reached by this week's occurrence. Pause, edit or stop a schedule from the Recurring sends list; skipped occurrences are recorded with the reason.
A/B tests#
Use an A/B test to find the message that works best.
- In step 2, choose Run a deterministic A/B split.
- Set 2 to 5 groups with percentages totalling 100, and pick a template for each group.
- Optionally set a holdout percentage. People in the holdout receive nothing, so you can measure the effect of messaging at all.
Each person is assigned to a group by a fixed rule, so the same person stays in the same group on retry.
Results appear in Reports under A/B results: sent, delivered, replies, clicks and opt-outs per group, with the lift compared to the control group and the holdout. Sauti marks a difference as clear only at 95% confidence. Groups below ten are masked.
Link tracking#
Choose Shorten public links and count clicks in step 2. Every recipient gets a private short code. Clicks are counted per send and per A/B group; Sauti does not store the clicker's IP address. Message part counts use the shortened link length.