Legacy Batching
Journeys & scheduled On Demand sends created before 28 October 2026 use our legacy batching logic and will continue to run on it until they finish. Your sends will still reach all your users within t…
How legacy batching works
Legacy batching sends the same number of users in each hourly batch, every sending day, with a minimum of one user per batch. It works out how many users to send per hour so that everyone is reached before the end date, then sends at that steady rate until all users have received their send.
Because it sends at a steady rate of at least one user per hour, sending may complete ahead of the end date. Smaller groups in particular may be sent within the first few days, giving you results sooner.
Spreading sends over a longer period
If you’d like sends spread over more of the journey, you can shorten the sending window. Fewer hourly batches each day means fewer sends per day, so sending runs closer to the end date.
For example, reducing a window by an hour gives one fewer batch each day, which spreads the same users over more days.
Want the new batching?
New journeys use the improved batching logic automatically. It spreads sends evenly right up to the end date. See How journey batching works for details.
If you want to update your existing Journey, or scheduled On Demand Sends, these would need to be cancelled and reapplied.
If you do need any assistance with this, please contact your Customer Success Manager, or send in your query to our Support Team at support@boxphish.com
How did we do?
