Test and send

Before messaging your full list:

Test

1. Open the campaign and choose Send test.
2. Enter your email (or a teammate’s).
3. Check subject, links, images, and the unsubscribe link.

There is a limit of one test per minute per account — that protects sending reputation.

Send

1. Confirm the audience and your plan quota.
2. If you see today’s limit, you can: narrow by tags, schedule for tomorrow, or choose send only today’s remaining (partial sample).
3. With a partial sample (recommended):
   • Prioritize engagers — people who opened or clicked recently go first in today’s slice.
   • Everyone left out gets an automatic tag (e.g. “Partial #123 — outside sample”). You can open those contacts in Contacts from the send detail link. Optionally pick an existing tag instead of creating a new one.
   • Optional: schedule the remainder at a time (default: tomorrow at the same hour). If more people remain than the daily limit, the next send is also partial and chains on its own — up to a platform day limit.
   • On the send detail you can download a CSV of excluded contacts or cancel the whole partial chain.
4. Optional: interval between emails (1 email every N seconds) and a deadline (promotions — after the date, the remainder is paused).
5. Send now or schedule in the account timezone.
6. The send enters the queue; track status under Sends (Partial / Continuation badges).

Do not delete the excluded tag before scheduling the remainder — the panel blocks that so you do not lose the shortcut.

When the account requires approval

Sends prepared by editors show as Pending approval. An owner or approver reviews content and audience before release.

In the approval box you see who requested the send and whether it goes out now or at a scheduled time.

If the send is rejected, the approver can use a quick reason plus a note. Open the detail to read the team guidance, adjust the campaign, and prepare a new send.

Smaller sends (up to about 5 thousand recipients) go out before very large ones. If several large customers send at once, sends progress together — nobody waits for the other to finish. If the platform’s capacity for the day runs out, the remainder continues on its own later (possibly the next day); you do not need to send again.

If the send pauses

The platform may slow or pause if it detects reputation risk (many hard bounces, for example). Fix the list and try again — see deliverability basics.

If the pause is due to a deadline, the promotion ended: what already went out stays in the metrics; the rest does not go out.

On the send detail, if you see a today’s capacity notice, just wait — the rest of the list continues automatically.