Launching a sequence does not always mean an email leaves in the next minute, and that is deliberate. Cold email lands better when it arrives during working hours, so every send is placed inside the send window you set on the sequence. If you launch inside that window, the first email goes out right away. If you launch outside it, the first email waits for the window to open.

Send windows run on the campaign's send zone, which is the workspace time zone unless a lead's own zone or the campaign's own zone says otherwise. Set the workspace time zone under Settings, Company, Outreach, and any campaign still on the default zone moves with it when you change it.

One campaign can run on a different clock from the rest. Under Schedule & sending on the sequence, Campaign time zone offers Workspace time zone, which keeps this campaign on the workspace clock and moves it whenever you change that, and Set for this campaign, which pins the zone you pick so this campaign stays on it whatever the workspace does.

You never have to guess which one is happening. The review panel you open before launching, and the sequence page after it, both show one plain sentence naming the exact moment the first email leaves, for example: First email goes out today at 2:15 PM (Denver time). In the review panel it is the First send line under What to expect. It is the same sentence in both places, written by the same code, so the promise you read before launching and the report you read after it can never disagree.

One more sentence sits directly beneath the first-send line, as the Opt-out and address row in the review panel and as the next line on the sequence page. It states what every email in this sequence will actually put in front of the recipient, for example: Each email adds a visible unsubscribe link, the one-click unsubscribe header, and your business address: 100 Main St, Denver, CO 80202, United States. Whatever the campaign does not add is named too, so nothing is left to inference: It does not add your business address.

When nobody has chosen any of the three for this campaign or for your organization, a second muted line says so and names the two places to change them: this campaign's Delivery & compliance step, or Cold Outreach settings. A settled default and a choice somebody made look identical in the controls, so the sentence tells you which one you are looking at. See Compliance for what each option means.

In the builder's Schedule & sending section, Start sending rests on Now, as soon as you launch. With that setting, pressing Launch enrolls your leads and queues the first step immediately. The send window still applies, which gives you the four possible outcomes below.

When follow-ups and first touches are due together, the campaign's Send priority decides which go first. By default, follow-ups go first. Inside one campaign, first emails that are due at the same time go out in the order the leads were added to the list, oldest first; the exact minute still varies with each mailbox's own spacing.

Emails to the same company are also spaced about twenty minutes apart, across all your mailboxes and all your campaigns, so nobody's mail system receives several of your messages at once. Personal mail domains such as the large free providers are excepted, since two people there are not the same company. Several leads at one company therefore go out across the day rather than together.

A follow-up wait counts sending days: the days your send window allows, minus skip dates and holidays. A follow-up set to wait 2 days goes out on the second sending day after the email before it, at about the same time of day. With the default Monday to Friday window, a follow-up set 2 days after a Friday email goes out on Tuesday, and a Monday holiday moves it to Wednesday. If the email before it went out outside your window hours, the follow-up goes out when the window opens on that day.

The override widens exactly two things: the hour and the day of the week. Everything else keeps its say. A skip date you listed is still a skip date, so a holiday never becomes a sending day. A paused mailbox, a daily limit already reached, a missing business address, an unsubscribe, and your monthly cold-send allowance all still hold their rows. It is a window override, not a compliance override.

Campaign ramp counts its days differently from the daily limits. A daily limit counts the last 24 hours and rolls forward. Campaign ramp counts calendar days in the campaign time zone: each mailbox gets a new allowance for the campaign at midnight there, and only a day the campaign sends moves the ramp forward. A campaign scheduled to start later starts at day 1 on its first sending day, and one that sends nothing for 7 days starts again at day 1. When a mailbox has used today's allowance, its lead rows read The campaign ramp reached its limit for this mailbox today. A first email then moves to another mailbox of the campaign with room, or waits for the next sending day, when the send window opens. A follow-up waits for its own mailbox. So a Friday that uses its allowance carries on on Monday with a weekday window, never on Saturday. See Deliverability for the numbers.

A send window like 9:00 AM to 5:00 PM has to be read on some clock. By default Laureo uses each recipient's own local time, which is the right choice for a spread-out list.

Laureo works out each lead's timezone in a fixed order. First, a timezone column in your import file: the headings time zone, timezone, tz and iana timezone are all accepted. Next, for United States and Canada leads, a state or province column, which is turned into a timezone once, at import, so the lead carries that value from then on. Then the lead's country. City and street address are never read.

The zone that was resolved and where it came from are shown on every lead, on the leads table and on the lead's detail panel, for example Eastern Time (ET) · from state: NY. The state and province table covers the United States and Canada only, and nine US states span more than one clock, so a state answers for about 98 percent of people rather than all of them: the zone most of that state lives in is the one used. Before you launch, the review screen's Time zones row states how many leads have a known time zone and which zone the rest will send in.

The leads the ladder cannot resolve send in the fallback zone shown right under the timezone choice, labelled When we can't tell a lead's timezone, send in:. It starts as your workspace timezone. The review screen tells you how many leads that is before you launch, so read that number and check the zone whenever it is large.

Choose On a specific date under Start sending and pick a date and a time. The time starts at your window's opening hour and you can set any minute from there. There is no limit on how far ahead you can schedule: days, weeks, or months are all fine.

While the sequence is a draft or scheduled, these fields save as you type. There is no Save button to press and no half-saved state to worry about.

The review panel carries a Send calendar row, and it answers two different questions with two different dates, because they are not the same day. First touches done is the day the last first email goes out, after which the campaign stops taking on new leads. Follow-ups done is the day the last email of any step goes out, which is when the campaign is finished. One sentence above the grid puts both in context, for example: About 120 emails a day across 4 mailboxes. Your 1,200 leads should all be contacted by Fri 3 Oct, with follow-ups finishing Tue 21 Oct. That is 14 sending days across 20 calendar days. A single-step sequence drops the follow-up half of that sentence. Sending days and calendar days are counted separately on purpose: a campaign that sends Monday to Friday spends two days of every week not sending at all, and counting those two as progress is how a finish date ends up wrong. The calendar follows the same rules as the sender, Send priority included: the same limits, the same send window and the same order.

Four figures sit under the sentence: Emails a day, First touches done, Follow-ups done and Sending days, the last written as 14 of 20 days. Below them the calendar runs one block per month, up to three; a longer run says This run continues past the months shown above. rather than making you page through it. A day that sends carries its projected total, and its description splits that total into first touches and follow-ups. A lighter day is one that managed ramp or Campaign ramp is still holding down. A day that does not send is muted, carries no total, and gives its reason on hover and to a screen reader.

One line under the grid names the limit that is actually setting your pace, which is the one thing to change if the finish date is further out than you want.

There is no line at all when nothing was waiting to send, because that is not a limit you can raise. When your sending window is the limit, that same line also counts the skips you did not choose for this campaign inside the next 90 days, for example 3 holidays and 2 workspace skip dates are skipped in the next 90 days. And if the run would take more than a year at the current pace, no finish date is shown at all: This sequence runs past a year at the current pace, so no finish date is shown. Add a mailbox or raise a cap to finish sooner.

It is a forecast, not a promise. These five lines are printed under every calendar. Replies stop follow-ups, so real totals come in lower and the finish date arrives earlier. This calendar follows the same rules as the sender. It assumes no replies, no paused mailboxes, no new campaigns on these mailboxes, no other user running out of monthly sends and room in your plan for more active leads. A day can shift by one because send times vary by a few minutes. Managed ramp raises a new mailbox from 10 to 20 to 30 sends a day over its first weeks, so early days are lighter. If this sequence has a per company limit, fewer leads enroll than the count above shows. Campaigns that share a mailbox take turns. One more line is always on screen, either last in that list or under the emails that are waiting on you: Emails waiting on you are not on the calendar.

After launch, open Send calendar on the campaign page. It sits in the header row beside View analytics and Recipients on a scheduled, running or paused campaign, and an ended campaign keeps it beside its status. A draft has no Send calendar. A link to the campaign page that ends in “?calendar=1” opens it straight away, and the bell described below uses that link.

Two dates sit at the top: Last first email and Last follow-up, each an estimate, for example about Tue 21 Oct. A one-step sequence has no follow-ups, so it shows only Last first email. When a date has moved, a muted line under it shows the earlier one, for example Was Fri 17 Oct. A run that would take more than a year reads More than a year.

What changed comes next: today's live entry first, then the last 5 daily entries, and Show all for the rest. Each entry says in plain words why the dates moved. Another campaign on a mailbox this campaign uses, a paused mailbox, a changed limit, replies that freed sends and a day that sent fewer emails than planned all get a line. Another campaign by the same creator is named; any other campaign reads Another campaign. For example:

One line under What changed gives the campaign's state when it is not simply running. A scheduled campaign reads Starts Mon 17 Mar. A paused campaign shows what happens if you resume it now: This campaign is paused. The calendar shows what happens if you resume it now. A campaign with everything sent reads All emails have gone out. The last one went out on Fri 31 Oct. An ended campaign reads This campaign has ended. and keeps its past days and its What changed history.

The grid below works like the one in the review panel. A filled day has already sent and carries the real number of emails, and its description splits that number into first emails and follow-ups. Today shows what has gone out and what is still to come, for example 12 sent, 18 to go. An outlined day is still projected: Filled days have already sent. Outlined days are still projected. The By day table under the grid gives the same numbers in rows, in the columns Date, First emails, Follow-ups, Total and State. State reads Sent, Today or Projected.

The calendar is worked out when you open it, and at that moment what you see is never more than a minute old. While the panel stays open, it refreshes every 5 minutes, and the line at the bottom, for example Updated 3:42 PM, gives the time it was worked out on your own clock. What changed keeps one entry a day for 5 weeks. Send history goes back 90 days, and a campaign that has run longer says so: Days older than 90 days are no longer kept.

When the last follow-up of a running campaign moves more than 3 sending days later, the campaign's creator gets a bell. It says the campaign now finishes later, gives the old and the new date, and opens the Send calendar. It comes at most once a day for each campaign, in the app only, never by email. A paused or scheduled campaign gets no bell.

Turn on a holiday calendar and Laureo holds sends on those dates. A send that lands on one moves to the next day inside your window, in each recipient's time zone, exactly the way your own skip dates already work. Holidays are chosen by calendar rather than typed as dates, so the dates are worked out again each year and the list never goes stale. There are four calendars.

A workspace in the United States that has never answered this question skips the United States federal holidays by default, with the calendar ticked for you in settings so you can see it and untick it. Answer it once, either way, and your answer is what holds from then on.

Set the workspace default under Settings, Company, Cold outreach, in the Skip dates and holidays card. That card is where every source of a skip is listed together: the calendars you ticked, how many dates they come to over the next 12 months, the calendar Laureo recommends and the reason it was recommended, and the dates you typed by hand. Typed dates sit under the calendars and are added to them, never a replacement for them, which is the escape hatch for a company holiday, a conference or a shutdown week no public calendar knows about. These calendars and dates apply to every campaign that has not chosen its own. Any campaign can pick its own list instead, in the Skip holidays field of the builder's send window block, and changing the workspace list moves every campaign that has not. Editing needs the cold outreach edit permission; everyone else sees the whole setting read-only, ticks included.

Laureo suggests one calendar and names where the suggestion came from: your workspace address first, then your workspace time zone, then your sending domains. It is only a suggestion. It is pre-selected on a new campaign and never on one you already have, the field says it is a recommendation and why, and if it guesses wrong Not this one clears it in a click. When Laureo cannot tell, no calendar is suggested at all. In settings the same suggestion reads Recommended for you: United States, from your workspace address. and it is never ticked for you there.

A holiday calendar is your calendar, not each lead's. The dates you pick are skipped for every recipient of the campaign, wherever they are. Skipping each lead's own national holidays is a separate thing we have not built yet.

Holiday calendars apply to cold sequences. Follow-ups on your normal email are not affected.

No quiet day on the calendar is left unexplained. Hold the pointer over a day that does not send, or reach it with a screen reader, and it gives the reason in a few words. A holiday names itself and the calendar it came from: Holiday: Christmas Day (United States calendar). When that calendar was the one Laureo suggested rather than one you ticked, the reason says so as well: Holiday: Christmas Day (United States calendar, recommended from your workspace address). A date an admin set for the whole workspace reads Skip date from your workspace settings. A weekend reads Weekend (outside your sending days), and any other day outside your hours or your sending days reads Waiting for the send window. A date you set on this campaign reads Skip date you set, the one reason that needs no explanation because you chose it here. All of them hold the send rather than dropping it: it goes out on the next allowed day. Anything held for a reason you did not choose for this campaign says so on the day, on the recipient's row and in the Recipients list, so you never have to guess why a day is empty.

Stop sending after takes an optional date. It means the whole of that day, read in the Campaign time zone, so a send at 4:55 PM on the last day still goes out and nothing leaves afterwards, even if some leads have follow-up steps still to come. Leave it empty and the sequence runs until every lead finishes their steps. It is most useful for a campaign tied to an event or an offer with an expiry.

While a campaign is active or paused you can set, move or clear the stop date. Setting one, or moving it earlier, asks you to confirm first. A date that has already passed is refused. The confirm is headed Stop sending on this date? and says that leads who have not received every step by the end of that date get no more emails from this campaign. A passed date stays on screen with This stop date has already passed. Pick a later date, or clear it. and is not saved. A later date, or an empty one, saves at once.

A saved stop keeps its moment. If the Campaign time zone of a live campaign changes later, the stop can fall inside a day on the new clock, not at its end, and the field then gives the time sending stops. For example, a stop at the end of November 30 in New York, after a change to London, reads Sending stops at 4:59 AM on Tuesday, December 1 (London time), not at the end of that day. To move the stop to the end of that day, pick the same date again.

If the end date would leave some leads without a first email, the review panel says how many, for example 35 leads will not get a first email before the end date Fri 31 Oct. Launch then asks you to tick Launch with this end date first. The assistant asks the same before it launches.

A send can be held for reasons other than the window: a missing business address, a mailbox that has hit its daily pace, a skip date you listed. On the leads table, the Sequence column says why in plain words for any lead whose next email is being held, and shows a small dot when nothing is holding it. A waiting send is normal pacing, not a failure.

A phrase that begins Waiting on you means the emails wait for a person to fix something. They keep their place until you do, and Laureo tells you what to fix.

On a running sequence, the header also carries a Next send line naming the earliest email still queued, for example Next send: tomorrow at 9:00 AM (Denver time). A scheduled sequence shows its start date and the number of leads attached instead, because nothing is queued yet.

A run can still stop for reasons that waiting cannot fix. When the send step cannot go ahead for a lead, the lead's row says why:

If a sequence looks like it is doing nothing, read the sentence on the sequence page first. It will either name the moment the next email leaves or point at what is holding it. See Troubleshooting for the paused-mailbox and exhausted-meter cases.