Bulk email timing depends on queue order, workflow behavior and sending limits; Close documents three checks to make before scheduling a send.
Key takeaways
- Check your tool's ordering rules before scheduling related messages.
- Estimate the sending time from your recipient count and minimum delay.
- Review recent sending activity before choosing the next send time.
- Check the connected email provider's limits before committing to the schedule.
Why timing matters for coaching sends
If you run a weekly coaching rhythm, your calendar probably has a shape. On Monday you send the team a reminder about pipeline reviews. On Tuesday morning a batch of follow-ups goes to leads who went quiet last week. On Thursday a workflow starts nudging new leads through a short sequence. Most of your attention goes to the words in each message. Very little goes to the clock, and that is where a lot of surprises come from.
You might assume that an email scheduled for a given time goes out at that time. For bulk and workflow sends, the sending tool is managing a queue, the queue is bound by limits, and those limits are a large part of the reason your messages arrive when they do. The rules are written down in vendor help pages. They are not hard to read, but they are easy to skip when you are busy building the list.
This post covers three timing facts from official documentation, a few related points about how email providers treat new recipients, and a practical way to plan a weekly send around all of it. It does not tell you what your own account limits are. Those depend on your tool, your email provider, and your plan, so check your own settings and your provider's documentation. What you will get here is a way to think about timing, so the next send does not catch you off guard.
Fact 1: Close bulk sends may leave in a different order
This is the fact that surprises people most. Close's help center explains that a bulk email initiated at 9:00 AM could send after a bulk email initiated at 3:00 PM. Starting something first does not guarantee it goes out first. ( Close, "Email Sending Limits")
Here is what that looks like on a real Monday. Suppose you start a team reminder at 9 AM and a lead follow-up at 3 PM. You might assume the reminder lands first. The documentation says you cannot count on that. If the reminder mentions a deadline and the follow-up contradicts it, you have a sequencing problem created entirely by the clock, and nobody did anything wrong on purpose.
The fix is not to fight the queue. Plan so that the order does not matter. Make each bulk email self-contained, so it makes sense whether a reader sees it before or after the other one. Put dates and deadlines inside the message itself, not in a line such as "as mentioned in the email from earlier," because that earlier email may not have reached the reader yet. If two sends must happen in a specific order, check Close's documented Workflow behavior below. The next section explains why.
Also be careful about sending a second bulk message to fix the first. If the original has not gone out yet, the correction can reach people before the message it was meant to correct. That is a common way to make a small mess worse. If you find an error in a queued send, look at what your tool allows you to do with that queued action before you start a new one.
Think about the effect on your team, too. A coaching reminder and a lead outreach often go to different people, so a reader who is on both lists may get them in either order. Write your reminder as though it will be read first, and your outreach as though it might be read before the reminder. Either way, each message should hold up alone.
Fact 2: Close Workflow steps keep their order
The same Close page says the order for Workflow email steps is not affected, and that Step 2 will never be sent before Step 1. ( Close, "Email Sending Limits")
That is a real guarantee, and it is worth building on. If your lead sequence has an introduction, a follow-up, and a short final check, check how your tool handles the timing between them. For a sales manager, this is the difference between a sequence you can rely on and a set of separate blasts you have to hope line up.
What the guarantee does not cover is the gap between steps. Check your tool's documentation for how a delayed start affects later steps. So when you plan a sequence, think about the date each step is likely to reach a lead, not only the delay you typed into the settings. A step that you expected on Tuesday might arrive on Wednesday; check whether that could also delay later steps.
A few habits make multi-step sequences easier to live with:
- Write each step so it stands alone. A lead who misses step one should still understand step two.
- Do not put a deadline in step two that assumes step one was read. Put the deadline in the message itself.
- Leave room at the end. If step three is meant to land before a Friday call, check whether your start day still gets it there with a margin.
- Keep the number of steps modest. Every extra step is another point where the calendar can drift.
Do not use a bulk send to imitate a sequence. If the second message depends on the first, check the chosen tool's step-order guarantee before relying on it. For related timing checks, see sequence step timing.
Fact 3: Close measures recent Workflow and bulk sending
The third fact is about how limits are measured, and it changes how you should read a schedule. Close says the limits apply to Workflow and bulk emails sent within the past 24 hours at that time. ( Close, "Email Sending Limits") So a limit is not a bucket that refills at midnight. It is a rolling window, and each time the tool checks, it looks back at what went out recently.
For a sales manager, a rolling window means a heavy day can affect a later day. A large send on Monday evening may still be counting against the limit on Tuesday morning, depending on when it ran. Two sends that look independent on your calendar may not be independent to the tool. A clean-looking calendar does not tell you how much sending is still inside the window.
The same Close page gives a concrete example. It says that if your minimum delay between emails is set to 60 seconds, and you send an email to 1,440 leads, your bulk email action will be processing for at least 24 hours straight. ( Close, "Email Sending Limits") The arithmetic is simple: 1,440 emails at one minute apart is 1,440 minutes, which is 24 hours. The lesson is that a large list at a set delay is not a quick job. It is a full-day process, and it can run into the next day.
When you plan your week, run this check before you commit. Take the number of recipients, multiply by the minimum delay between emails, and see how long the send will run. If the result is longer than you expected, you have a few options. You can split the list into smaller runs, you can review the delay setting if your account allows it, or you can accept a longer run and move the next time-sensitive message to a later day.
HubSpot's help documentation describes a similar pattern from a different vendor. In an article about creating and sending SMS messages, it says recipients will be sent the email on a staggered basis over 24 hours. ( HubSpot, "Create and send SMS messages in HubSpot") Check the sending feature and its documentation before applying that timing to your own schedule.
Illustrative example: Estimate a bulk run
For an illustrative list of 60 recipients with a minimum delay of 60 seconds, the planning calculation gives 60 minutes. Treat that as an estimate, then check the queue and account limits before scheduling a time-sensitive follow-up.
What the limits are for
It is easy to see sending limits as an obstacle. Close's documentation frames them differently. It says email sending limits are designed to prevent your email accounts from exceeding the sending thresholds set by your email providers. It also says that these limits not only safeguard your accounts from potential disconnection from Close and interrupting your email sending, but also help maintain your sender reputation and avoid spam-related issues. ( Close, "Email Sending Limits")
That changes how you should think about the wait. The delay you see is not the tool being slow for no reason. It is the tool keeping your mailbox inside a threshold that your email provider set. If an account gets disconnected, your email sending can be interrupted, and a send that was halfway through a list may not finish as planned. A send that runs slowly and finishes is better than a send that runs quickly and stops partway.
Follow your provider's documented sending guidance. For a team that runs the same rhythm every week, consistency is part of what makes the sending work. Your recipients also learn when to expect messages from you. Erratic bursts are harder to predict than a steady pattern, and you are the one who decides which pattern you show.
Keep in mind that these protections exist on both sides. Your provider wants to keep spam out of inboxes, and your tool wants to keep your account connected. Respecting the limits is not just about avoiding an error message. It is about keeping the channel you depend on in good shape for next week, next month, and next quarter.
Who counts as a new recipient
Not every recipient is the same to an email provider. Microsoft's help page on sending limits in Outlook.com defines a "non-relationship recipient" as someone you have never sent email to before. ( Microsoft, "Sending limits in Outlook.com")
Why does that matter for a coaching send? Because a weekly send often mixes two groups. One group is people you already email regularly, such as your own team. The other is people you have never written to, such as a fresh batch of leads from a new source. Microsoft's definition draws a line between these groups, and that line is a useful one for you to draw too. Before a send, separate recipients by whether you have ever sent them email. Then decide whether the new-recipient group should go out as its own run, rather than being blended into a large team send.
Keep the split simple and honest. A lead who replied to a message last month is not a new recipient, even if your list export puts them in the same column as everyone else. For an address from a purchased or scraped list, check your sending history rather than classifying it by its source. Sorting your list this way costs a few minutes and gives you a clearer picture of where the sending risk sits.
Microsoft's page also notes that the sending limits of any third party connected accounts depend upon the service provider. ( Microsoft, "Sending limits in Outlook.com") This matters if your tool sends through an account you connected from another provider. The limits you need to know are then the provider's limits, not only the tool's. Look them up before you plan a send through that account, and do not assume that a limit you learned about in one place applies everywhere.
Planning a weekly coaching send
Here is a simple way to put these pieces together. Build the week around three questions.
First, what must happen in a particular order? For Close, use the documented Workflow behavior described above; for another tool, check its ordering guarantee first. If the order matters to the lead's experience, make the tool enforce it.
Second, what can arrive in any order? Those messages can go out as bulk sends, as long as each one is written to stand alone. Put the deadline inside the message, and do not refer to something that a reader might not have seen yet.
Third, how long will each bulk send take, and what else is still inside the 24-hour window when it runs? Estimate the run time from the number of recipients and the minimum delay. Then look at the other sends you have planned for the next day and check for overlap.
Here is an example of how this might look over a week. On Monday, you send a pipeline reminder as a single bulk email to your existing team. A small list should finish quickly, but check the delay against the recipient count anyway. On Tuesday, a lead re-engagement workflow starts for leads who went quiet. In this example, you use Close's documented Workflow ordering behavior. On Thursday, you send a larger bulk email to a lead list. You estimate from the recipient count and delay that it will take most of a day. So you do not schedule anything time-sensitive for Friday morning, because the bulk send may still be running and the 24-hour window has not cleared.
The example is only a pattern. Your list sizes, delays, and tools will be different. The point is that each message gets a slot that fits its job, and that the slots are checked against the rules rather than against the clock on your wall.
Consider writing this plan down once and reusing it. A stable weekly rhythm is easier to check than a series of one-off decisions. When something changes, such as a new lead source or a bigger team, update the plan and run the checks again. Use your recurring sales practice plan to connect the send schedule to the coaching rhythm.
A checklist before you hit send
Use this list before any weekly coaching send. Each item maps to one of the points above.
- Confirm which account is sending, and look up that provider's limits, not only your tool's.
- Split the list into people you have emailed before and people you have not.
- Multiply the number of recipients by the minimum delay to estimate the run time.
- Check whether the run will overlap with another bulk send from the last 24 hours.
- Make sure no bulk message depends on being read after another one.
- Check the workflow's documented ordering behavior before moving a sequence into it.
- Put deadlines inside the message, not in a reference to an earlier email.
- Expect the last recipient to get the message much later than the first, and plan the content so that is fine.
If you cannot tick off an item, change the plan before the send, not after. A send you can explain is far easier to manage than one you have to apologize for.
Your next step today
Choose the next weekly coaching send and write down its recipient count, minimum delay and estimated run time. Check recent sending activity before giving it a slot on the calendar.
Questions about bulk email timing
Does starting a bulk send first guarantee it leaves first?
No, Close documents possible reordering between bulk sends. Make related messages self-contained rather than relying on their start times.
What should I check before using a workflow?
Check the chosen tool's documented step-order behavior and how it handles delays. Use those details when deciding whether a sequence fits your schedule.
How should I plan the next send?
Estimate the run time and review recent sending activity before scheduling it. Leave room for the queue rather than assuming every recipient receives the message together.