Batched invite emails
When you invite crew and guests in bulk, 1pm does not fire the whole list off the instant you click send. It gathers the invites into a batch and holds them for a short while first. That pause is a safety buffer: a last chance to catch a mistake before anything leaves the building. If you realize you picked the wrong event, the wrong list, or simply changed your mind, you can cancel the batch and not a single email goes out.
This article explains how the buffer works, how long it lasts, and how to cancel a batch you did not mean to send.
Where batched emails live
Open Account from the user menu, then the "Batched emails" card, or go straight to Account, Batched emails. The page shows your queued invite batch: how many invites it holds, which event they are for, and roughly when it will send. While a batch is sitting here, nothing has been sent yet. There is no draft to finish and nothing for you to do unless you want to stop it.
If you have no batch waiting, the page simply says so.
How long the buffer lasts
The delay before a batch sends depends on your plan:
- Paid subscription: about 60 minutes. Long enough to catch a wrong-recipient mistake, short enough that the invites still feel prompt.
- Free trial and other accounts: about 12 hours. A longer brake while an account is new.
Share links and RSVP invites are not time-sensitive to the minute, so a generous buffer costs you nothing and buys you a real undo. The countdown shown on the Batched emails page tells you roughly how long is left.
Cancelling a batch
To stop a queued batch, open Account, Batched emails and select Cancel batch. You will be asked to confirm, because cancelling stops every invite in the batch, not just one. Confirm and the whole batch is discarded: nothing is sent, and you are free to build and queue a fresh batch straight away once you have the right recipients.
Cancellation is all-or-nothing by design. The buffer exists to catch the "wrong list entirely" mistake, which is the one that matters, so the control matches: stop the blast, fix the list, queue again.
Single invites are not batched
The buffer applies to bulk sends. When you email one crew member their link from a single crew row, that goes out right away, the way you would expect, and you will see its delivery status update live on the row within a few seconds. Batching only kicks in when you invite a group at once, which is the situation where an accidental blast would actually do damage.
How many recipients a batch can hold
A single batch is capped at 100 recipients. That is comfortably more than a typical event's crew plus a guest list, while keeping an accidental send from reaching a very large audience before the cancel window is up. If you need to invite more than 100 people, send them in more than one batch.
Batched invites still count toward your allowance
Holding a batch does not make it free. When the buffer expires and the batch sends, each invite draws down your monthly email allowance exactly as an individual send would. Cancelled batches cost you nothing, because nothing was sent. For how the monthly allowance works and what counts against it, see "Your monthly email allowance."
What happens when a batch sends
Once the buffer expires, the invites go out and 1pm begins tracking each one: delivered, bounced, or delayed, just like any other invite-style email. You can watch the results on the crew rows and on each contact's Emails tab. See "Tracking guest & crew emails" for reading those delivery states and fixing an address that bounces.