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.

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.

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.

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.

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 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.

After a campaign starts, the send calendar keeps working. Open Review changes on a running campaign and the same grid shows the days that have already sent as filled squares carrying the real number, and the days still to come as outlined squares carrying the projected one: Filled days have already sent. Outlined days are still projected. A day that sent more than expected keeps its own number, so the grid never quietly agrees with a forecast the campaign has already beaten. Days that are skipped explain themselves exactly as they did before you launched. Sending history is kept for 90 days, so a campaign that has been running longer than that says so in a line under the grid: Days older than 90 days are no longer kept.

It is a forecast, not a promise. These four lines are printed under every calendar. Replies stop follow-ups, so real totals come in lower and the finish date arrives earlier. Sending caps count a rolling 24 hours, so a day by day grid is close but not exact. 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.

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.

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 on the same clock as the start, 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.

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.

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. A scheduled sequence shows its start date and the number of leads attached instead, because nothing is queued yet.

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.