Help Center
Docs

Cold Email Deliverability

How managed ramp, the campaign ramp, per-mailbox pacing, send priority, send windows, jitter and the automatic pauses work, and why Laureo does not offer warmup

Managed Ramp Explained

Volume grows gradually, set by a mailbox's connection age and recent sending.

Laureo caps what each mailbox sends in a day with a managed ramp. Each new mailbox starts small and climbs a little each day. The ramp also follows recent sending: on any day, a mailbox sends at most 1.5 times its busiest day of the last 7 days, and never less than 10. So a mailbox that was quiet for 7 days starts again at 10, whatever its age. The managed ramp is automatic for every mailbox, and you cannot skip a stage. Each campaign also has its own ramp on top of this one, described below.

FieldDescriptionDefault
Ramp scheduleA new mailbox starts at about 10 emails a day and climbs a little each day, to about 30 by day 15; from day 22 its own daily limit applies. Its recent sending still bounds it. If your own limit is lower than the ramp, your limit applies. The mailbox card shows the day and the date your own limit takes over.10 to 30 per day over 21 days
What countsEvery email the mailbox sends counts: first touches, follow-ups and test emails, from every campaign that uses it. Replies you send from your inbox never count.
How the day is countedThe count covers the current day in your workspace time zone (UTC when no workspace time zone is set by hand) and resets at midnight there. On a given day a mailbox sends between 0.9 and 1.1 times its limit. A second limit covers any 24 hours: a mailbox never sends more than 1.25 times its daily limit in 24 hours.
Per-mailbox recommendationWhen you set a mailbox's daily limit above 50, the mailbox card warns that the recommended daily limit for one mailbox is 50. It is a warning, not a block. No mailbox can send more than 2,000 a day.50/day recommended
Ramp driverConnection age and recent sending. Each day of connection moves the mailbox a little further up the ramp, until day 15. Each day it may also send at most 1.5 times its busiest day of the last 7 days, counted in whole UTC days before today, and never less than 10. Test emails do not count as recent sending. The mailbox card names the limit in force: Ramp, Daily limit or Recent sending.
Today’s targetEach mailbox’s daily count varies by up to 10 percent either way around its daily limit, so no two days look the same; a recovery after a block, a new mailbox’s handoff limit and your email provider’s own ceiling are never exceeded.
Steady volumeOnce a mailbox has a sending history, its daily volume stays at or under its busiest day of the last 30 days (at least 5) and grows by 2 a day, so when other mail from the mailbox stops, your campaigns do not jump into the space it leaves.
Unread repliesEach mailbox card shows the replies and notices that wait unread for more than 48 hours, with a link to the Cold lane, and you get one notification a day per mailbox when a reply waits more than one business hour (Monday to Friday, 9:00 to 17:00 in your workspace time zone); Laureo never reads, answers or moves the mail itself.
More mailboxes, more total volume, same per-mailbox limits
Each user can connect up to 5 sending mailboxes. Total daily reach grows with the pool, and each mailbox stays inside its own limit. A new conversation opens from the selected mailbox with the most room left under its own daily limit. When two mailboxes have the same room, the one that sent fewer emails in the last 24 hours goes first. Once a conversation starts, every follow-up goes out from that same mailbox and counts against its limit. So a thread always reads as one person writing to one person.

Campaign Ramp

Each campaign also starts slow on every mailbox it sends from.

The managed ramp limits what a mailbox sends in a day. Campaign ramp limits what one campaign sends from each of its mailboxes. On the campaign's first sending day, each of its mailboxes sends at most 5 emails for it. Each sending day after that adds 2 more, up to 25 per mailbox a day. New campaigns start with Campaign ramp on at these numbers. Campaigns created before Campaign ramp existed keep it off until you turn it on. You can change the numbers, or turn the ramp off, in the campaign's Schedule & sending settings, also while it runs. See Building Sequences for the fields.

FieldDescriptionDefault
Ramp dayA ramp day is a day the campaign sends. Days with no sends, such as weekends, skip dates or a pause, do not move the ramp forward. Days are counted in the campaign time zone, from midnight to midnight, so each mailbox gets a new allowance for the campaign at midnight there.
Idle resetWhen the campaign sends nothing for 7 days, its ramp starts again at day 1 with the next send.
Restart rampOn an active or paused campaign, Restart ramp starts the ramp again at day 1 with the next send. Turning the ramp off and on again does the same. Use it after a long pause or when you add mailboxes.
With the mailbox limitsThe campaign ramp never lifts a mailbox above its own daily cap. When that cap is lower, the cap sets the number. Two campaigns on one mailbox each ramp on their own, and together they stay inside that mailbox’s cap.
When the day’s room is usedA first email moves to another mailbox of the campaign that still has room. When none has room, it waits for the next sending day, when the send window opens. A follow-up stays with its mailbox and waits the same way. Nothing is skipped.
Blocked daysA day on which your email provider blocked the campaign’s mail as possible spam is not a ramp day. The ramp stays where it was, so a block never moves the campaign to a bigger day.
Each mailbox’s own dayEach mailbox climbs the campaign ramp on the days it sent for the campaign. A mailbox added to a running campaign, or back after 7 days or more without sending for it, starts at day 1. A mailbox back from a shorter pause keeps the day it had.
Hold while replies stay lowOn by default. Once a day, Laureo reads the campaign’s last 14 days. When 2% or more of at least 50 emails bounced, or fewer than 1 in 270 of at least 300 people contacted replied, the ramp keeps its level that day instead of climbing. It never goes lower. A first email younger than 72 hours is not judged for replies yet. The switch is Hold the ramp while replies stay low, under the campaign ramp fields.On

Before launch, Review and launch warns when Campaign ramp is off. It is a warning, not a block. The send calendar and the lead rows name the campaign ramp when it sets the pace. See When Sequences Start Sending.

Per-Campaign Daily Send Limit

Cap how fast one campaign sends, on top of the per-mailbox limits.

Each campaign has an optional Daily send limit for this campaign, in the sequence settings. It caps how many emails the campaign sends in one day of your workspace time zone, across all its mailboxes. First touches and follow-ups both count. Test emails do not. The count resets at midnight in that time zone. Leave the field blank (it reads “No limit”) and the campaign has no limit of its own. It then sends as fast as its mailboxes and their ramps allow.

FieldDescription
Per-mailbox daily limitLimits one mailbox. It counts every email the mailbox sends in one day of your workspace time zone: first touches, follow-ups and test emails, from every campaign. Replies do not count. Set it on the mailbox card. The recommended limit is 30 a day.
Per-campaign daily limitPaces one campaign across all its mailboxes, first touches and follow-ups together, in one day of your workspace time zone. Test emails do not count. Blank means no campaign limit. To limit first touches only, use New leads contacted per day in the same settings.
The tightest limit sets the pace
A campaign never sends faster than its tightest limit. Every email obeys the campaign's daily limit, its campaign ramp, the mailbox's daily limit and ramp, the time between emails from one mailbox, the send window, and your monthly cold email allowance. First touches also obey New leads contacted per day. Raising one limit does not help while another one is tighter. The send calendar names the limit that sets your pace.

Because the limit is per campaign, you can run several campaigns at different paces. Give a priority campaign a higher limit and a background campaign a lower one. Campaigns that share a mailbox also share its daily limit, so two campaigns on one mailbox draw from the same allowance. Campaigns that share a mailbox take turns.

Per-Campaign Send Controls

Shape how many first touches a campaign starts, and what goes first when sends are due.

Beside the daily send limit, each campaign has four more controls. Two of them limit how many new conversations it starts. Send priority decides what goes out first when more emails are due than your limits allow right now. Add leads as sending room opens decides when the leads of a large list join the campaign.

FieldDescriptionDefault
New leads contacted per dayThe most first touches (step 1) this campaign starts in any rolling 24 hours. Follow-ups do not count against it. Leave it blank for no limit of this kind.
Leads per companyThe most leads at any one company, matched by their email domain so a campaign never piles onto a single organization. Each campaign sets what the limit counts. With the switch "Count leads from every campaign" off, it counts only the leads this campaign enrolls. With it on, it also counts the leads at that company who are active or paused in your other campaigns. New campaigns start with the switch off. Personal-email providers are never limited. Blank means no limit.
Send priorityDecides what goes first when follow-ups and first emails are due at the same time. Follow-ups first: On each mailbox, due follow-ups go out before first emails to new leads. Conversations you started stay on time. New leads first: On each mailbox, first emails to new leads go out first. A follow-up more than 3 days past its due time still goes first. Follow-ups first is the default.Follow-ups first
Add leads as sending room opensThe switch reads "Add leads as sending room opens (recommended for large lists)". On, the campaign takes on leads as its mailboxes make room. About two weeks of first emails wait in line at a time, so a new lead gets its first email within about two weeks of joining. Off, every lead joins at launch. New campaigns start with it on.On for new campaigns

A follow-up becomes due when its wait ends. The wait counts sending days: the days your send window allows, minus skip dates and holidays. It counts from the moment the previous email went out, and the follow-up goes out 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. If the email before it went out outside your window hours, the follow-up goes out when the window opens on that day. It always goes out from the same mailbox as the first email, inside that mailbox's limits.

When more emails are due than your limits allow, the rest wait. Emails that wait for sending room keep their place and go out when room opens. Nothing is stopped for waiting. If something needs you, such as a mailbox to reconnect, an address to add or a subject to fill in, the emails wait and we tell you.

The Send calendar follows these same rules: the same limits, the same send window and the same Send priority. So it shows the order the sender will really use. It cannot know who will reply. A reply stops that person's follow-ups, so real totals come in lower and the campaign finishes earlier. After launch, the Send calendar on the campaign page shows what has already gone out and what changed. See When Sequences Start Sending for how to read the calendar.

Send Windows and Jitter

Cold email sends during business hours, with human-like spacing.

By default, a campaign sends Monday to Friday, 9:00 AM to 5:00 PM, in each recipient's own time zone. When Laureo cannot tell a recipient's zone, it uses the campaign's fallback zone. You can change the days, the hours and the zone in the sequence settings. Inside the window, Laureo adds jitter, a random gap between sends, so a mailbox never sends a burst of messages on a fixed beat. The result reads like a person sending one email at a time.

The spacing is stated, not hidden. Under Mailboxes in Cold Outreach settings you will find the exact band. By default, emails from one mailbox are never closer than 9 to 15 minutes apart, a gap drawn at random each time, so your sending never settles into a fixed cadence. Under that sits a floor of 90 to 140 seconds, which no mailbox sends inside even when an older campaign carries a shorter gap. A campaign can also set its own minimum time between emails from the same mailbox, in whole minutes, from 2 to 30 minutes. New campaigns set none, so they use the default band. A minimum you set is not a fixed cadence: Laureo adds a random extra of up to half again on top of every wait, and nothing sends inside that floor.

All of this is measured per mailbox. Different mailboxes send independently of each other, so two of your mailboxes can send in the same minute. Each mailbox draws its random wait once for each gap between two of its emails, so your mailboxes do not fall into a shared beat.

Each mailbox also spreads its emails across its send window: when it has only a few left to send today, it waits longer between them, and each wait varies by up to 30 percent either way. So a mailbox with 10 emails to send in an 8-hour window spreads them across the day instead of sending them all in the first two hours. Emails from different mailboxes that are due in the same minute leave a few seconds apart, never together, with a random wait of up to 6 seconds between two of them, and a mailbox that already sent that day and comes back after a pause or a hold starts again at a random point instead of sending at once. The minimum gap stays a minimum: the spread only adds wait, and the daily limits stay the same.

A launched sequence tells you in words when its first email leaves, and why it waits when it waits. See When Sequences Start Sending for the send window, the fallback time zone, scheduling a start date, and the reason shown on a held lead.

Skip Dates

Keep cold email from sending on holidays and other blackout days.

Some days you would rather not land in a cold inbox at all, such as public holidays. Under Cold Outreach settings, the Skip dates card holds an org-wide list of days cold outreach should not send. A send that would otherwise fall on a skip date is deferred to the next day inside its send window, evaluated in the recipient's time zone, so the message waits for the next legal opening instead of going out on the blackout day. Until it sends, the row stays pending and makes no forward progress.

Each campaign can override the org list. In the sequence builder's schedule, the Skip dates field starts empty, which inherits your organization's list; add a date there and this campaign uses its own list of blackout days instead, leaving every other campaign on the org default.

Per-Root-Domain Pacing

Emails to the same company are spaced apart.

Laureo also paces by recipient root domain. Emails to the same company leave 20 to 30 minutes apart, a gap drawn at random each time, and two mailboxes on one of your sending domains do not send in the same minute while the day leaves room for it. The company spacing counts across all your mailboxes and all your campaigns. 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, not together.

Provider-Matched Sending

When it can, Laureo sends from a mailbox on the recipient's own email provider.

Mail often lands more reliably when the sending mailbox and the recipient sit on the same email provider. When capacity allows, Laureo prefers a first-touch send from one of your mailboxes hosted on the recipient's own provider. This is automatic, with nothing to configure, and it never holds a send: when no matching mailbox has room, or the recipient's provider cannot be determined, sending falls back to the normal rotation across your pool. It only ever changes which mailbox inside its budget sends the email, never whether the email goes out.

Laureo learns a lead's provider from the mail server of the lead's domain, when the lead is imported or checked. The builder shows how many of a campaign's leads have a mailbox of the same provider. See Building Sequences.

Bounce-Rate Auto-Pause

A mailbox whose hard bounce rate passes the threshold is paused for new cold sends.

Laureo watches each mailbox's hard bounces over the last 7 days. Once a mailbox has made at least 50 sends in that time and more than 2% of them hard bounced, it is paused for new cold sends. An email a provider blocked counts as neither a send nor a bounce here, because it is not a bounce. While the mailbox is paused this way, your replies from it are held too, until you resume it.

This pause does not end on its own. You resolve the cause (usually a stale slice of your list, or addresses that were never accurate) and resume, and Resume asks you to confirm the cause first. See Troubleshooting for the resume flow.

Provider Block Pause

When a mailbox provider blocks your mail, the mailbox rests and starts again on its own.

Sometimes your email provider blocks the emails a mailbox sends because they look like spam. Laureo pauses that mailbox for new cold emails after 1 blocked email when the provider's report about it passes every check Laureo makes, including the provider's own authentication of the report. Otherwise Laureo pauses the mailbox when blocks hit emails to 2 or more different recipients within 60 minutes. The card says why and how long is left, for example Paused: provider blocked 1 message · resumes in 23 h. The pause ends on its own at that time, and the mailbox sends again without you. For the first 60 minutes of the pause, the card also counts the refusals so far, because your email provider can deliver more reports up to 50 minutes late. The first pause lasts 24 hours. When the system paused the mailbox in the 7 days before, it lasts 48 hours. First emails that were due from the mailbox move to another mailbox of the campaign with room; follow-ups wait for it.

A blocked email is not a bounce. The recipient's address is not suppressed, and the email counts in neither side of the bounce rate. You can resume the mailbox early: Resume shows the cause and asks you to confirm it. Reconnecting the mailbox does not end the pause. See Sending Accounts for the card and the dialog.

Your email provider can also refuse mail that a mailbox sends outside Laureo, or stop the mailbox from sending for a while when it reaches a sending limit. Laureo reads these notices in the mailbox and tells the mailbox owner and your admins once a day for each mailbox and each kind of notice. Your email provider counts every message your account sends, from any tool. Mail that a warm-up tool or another app sends from a mailbox counts toward its limits too. A refusal of mail that Laureo did not send does not pause the mailbox.

Sending limit pause. When your email provider says a mailbox reached its sending limit, or refuses a send because of that limit, Laureo pauses the mailbox for new cold emails. The pause lasts 24 hours, or 48 hours when the system paused the mailbox in the 7 days before. When your email provider names a later time to try again, the pause lasts until then, up to 72 hours. It ends on its own. The mailbox owner and your admins get one alert for the pause. An email your email provider did not send because of the limit is not a bounce: the address is not suppressed, and the email waits to go out later.

After a pause. When a provider block pause or a sending limit pause ends, the mailbox does not go straight back to its full daily cap. For 48 hours it sends half its daily cap, and never fewer than 5 a day unless its cap is lower. Then its cap rises by 3 each day until it is back in full. The badge on the card reads Recovering while this lasts. The card also keeps one line about the block until the 7-day repeat window closes, with the date before which another block pauses it for 48 hours. The alert about the pause stays in your notifications, unread until you read it, so a pause that ended overnight is not missed.

Automatic Campaign Pause

A campaign pauses itself when its hard bounce rate climbs, or when several mailboxes stop at once.

Laureo also watches each campaign, and pauses it on its own in two cases. The first is a bounce rate that climbs: over the last 7 days the campaign made at least 100 sends, and more than 3% of them hard bounced. Emails a provider blocked are left out of this count too. The second is several mailboxes that stop at once: the system paused 3 or more of your mailboxes within 60 minutes, and the campaign had bounces or blocks on them.

The person who created the campaign and your admins get Campaign paused after bounces or mailbox pauses, which names the cause. Clean the list, or check the paused mailboxes, before you resume. Only someone with access to every campaign can resume a campaign the system paused, and they confirm the cause first. A campaign you paused yourself resumes as before.

Refused Emails and Step Holds

What happens to an email your email provider refused, and to the emails after it.

Follow-ups wait for a refused first email. When your email provider refuses the first email to a lead, the lead's follow-ups do not go out, so nobody gets a reply to an email they never received. The lead row reads Waiting on you: the first email to this lead was refused by your email provider. Resend it, or stop the lead. The follow-ups go once the first email is sent again, by you or by the automatic resend below.

The copy or the mailbox. Laureo decides what caused a refusal. When 2 or more of the campaign's mailboxes had the same copy of a step refused within 24 hours, the copy is the cause: no mailbox sends it for 24 hours, and the campaign's creator and your admins get Campaign step on hold. Editing the step lifts the hold at once, and Release on the campaign page ends it early. When one mailbox had the refusal, the mailbox is the cause: no step is held, the step keeps sending from the campaign's other mailboxes, and editing the step changes nothing. The campaign page says which of the two it is.

The automatic resend. A refusal from one mailbox is sent again about a day later. A held step's refused emails are sent again after the hold ends, once the step's copy has changed. Each lead and step is sent again automatically once at most. The resend a day later skips a refusal for a failed sender authentication check (status 5.7.26 or 5.7.515). Fix your DNS records, then press Resend on the campaign page. A held step is the one automatic exception: when its hold ends after a copy change, these refusals are sent again with the step's other refused emails. A 5.7.515 refusal pauses the mailbox. A 5.7.26 refusal pauses it when the DNS check fails. Nothing goes out from a paused mailbox until you resume it. Laureo never re-sends from a mailbox that is paused, that the system paused in the last 7 days, or that is still at its lower cap after a pause, and never while the campaign is paused. A refused email, a first email or a follow-up, stays with the mailbox that sent it and waits for that mailbox. What is still waiting shows on the campaign page, for example 3 sends refused by the provider, not yet re-sent, with Resend. A refused email that is sent again, by you or automatically, goes after the campaign's new first emails of the day, and its lead row reads Resend: after the new emails.

A refusal by the recipient's server. Sometimes the recipient's own mail server refuses the email, not your email provider. Then the lead stops, and its later steps do not go out. The lead reads Stopped: the recipient's mail server refused the email. The address is not suppressed, and the refusal does not count as a bounce. When mail servers at 3 or more recipient domains refuse email from one mailbox within 7 days, its card says so.

Domains That Cannot Receive Mail

A bounce that says a whole domain is dead stops the leads there.

Some bounces say the recipient's domain cannot take mail at all: its mail server refuses to accept mail for it, or the domain has no mail server that can be found. Laureo treats that bounce like one for an address that does not exist. The lead is marked bounced, its address joins your suppression list, and its campaigns stop for it. One such bounce stops that lead only. When a second one arrives from the same domain soon after, or a check of the domain at that moment finds no working mail server, the other leads at that domain are held back too. They read Domain cannot receive mail, and Include anyway never releases them.

Open Tracking Is Off by Default

For cold, track replies, not opens.

Open tracking is off by default on every cold sequence, and for cold outbound we recommend leaving it off. Open tracking adds a tracking pixel to each email, and two things work against it. The numbers are unreliable, because image-blocking and automated link-and-image scanning fire opens that no human ever made. And the extra tracking can itself weigh on deliverability. The signal that actually predicts pipeline is the reply, so track replies and let opens stay off. See Analytics for why reply rate is the headline metric.

Where Tracked Links Point

The tracking-domain card states which host your links are on today.

Tracking needs a host to put the links on. Today tracked links, the unsubscribe link and the one-click unsubscribe header run on Laureo's standard tracking host, which all Laureo workspaces share. The flow for adding a tracking domain of your own is not switched on yet. The Custom tracking domain card, at the top of Cold Outreach settings, always states which state you are in rather than leaving you to infer it from a form. It shows one of five states, and today every organization is in the fourth.

FieldDescription
Not available yetThe card reads "Custom tracking domains are not available yet. Nothing to set up on your side; the setup flow appears here when custom tracking domains are switched on." There is no field and no button, because this state has nothing for them to reach. Nothing is broken, and the switch is not one your organization holds.
None set up yetThe add flow: a field for a subdomain you control (for example track.yourdomain.com, never your root domain), an Add tracking domain button, and the note that tracking opens and clicks stays off per sequence until a domain is verified. Per-mailbox pacing and enforced caps are unaffected either way.
VerifiedYour own domain is live: "Tracked links and the unsubscribe header use your own tracking domain." A muted Last checked line underneath shows the most recent re-verification, which runs on its own.
A standard host is carrying your linksWhen a shared tracking host is available and you have not added your own, the card says "Tracked links use our standard tracking host. Add your own tracking domain to put them on a domain your recipients recognize." Your own domain is then a branding upgrade, not a precondition. The setup flow is not switched on yet, so the card shows no field and no button.
Verification failedThe status reads Not verified, with "Publish the CNAME below, allow time for DNS to propagate, then verify again." Where a standard host exists, links keep working on it in the meantime: "Verification failed. Links use the standard tracking host until it verifies."

Only a teammate with organization-wide outreach access can add, verify, retire, or replace a tracking domain. Everyone else sees the same card, read-only, with a line saying so. See Domain Setup for the CNAME steps and for retiring or replacing a domain.

Unsubscribe links live on the same host
The tracking domain is not only about opens and clicks. Until a domain of your own is verified, the unsubscribe address in your emails is built on the standard tracking host, which is a different domain from the one you send from, and recipients can see the two differ. The sequence page says so plainly when that is the case.

Cold Outreach Settings, Section by Section

One page of organization-wide controls, edited in place.

Cold Outreach settings open from the gear on the Marketing hub, and mirror at Settings under your company's outreach page. Everything here applies to your whole organization, not just to you, and every control saves in place as you change it. There is no Save button at the bottom of the page. Seven sections, in order:

FieldDescription
Custom tracking domainThe five states above. A subdomain you control, used to track opens and clicks on a host that is yours. Campaign links and the unsubscribe header use it too once it is verified.
Unsubscribe & opt-outHow recipients opt out of your cold outreach, and the deliverability signals that ship with every send. The CAN-SPAM postal address itself is not edited here: the card carries the one link out to the company settings that own it.
Country rulesHow outreach treats leads by country. Advisory markets are flagged for review but are still sent, and sending caps and per-mailbox pacing always apply. Read-only by design.
Blocked domainsDomains cold outreach must never contact. Matching applies to every address at a domain and its subdomains.
Skip datesDays cold outreach should not send, such as holidays. A send scheduled on a skip date moves to the next day inside its send window, read in the recipient’s time zone. Each campaign can override this list.
Promoting a leadWhether promoting a cold lead into the CRM also opens an opportunity for the new contact.
MailboxesNot edited here either. A Manage mailboxes link out to the Mailboxes tab, because connection and the daily cap belong to each mailbox, plus the read-only send-spacing line quoted above.

Opt-out defaults. If your workspace has no saved Cold Outreach settings, each cold email ends with one line: "If this isn't relevant, reply and I'll stop." It has no unsubscribe link and no one-click unsubscribe header, like a message you write in your own mail app. A workspace with saved settings keeps the opt-out switches it has. Each campaign can turn the link or the header on in its Delivery & compliance section.

Mailboxes and Domains

Sending volume and feedback are tracked per domain.

Email providers track sending volume and feedback per domain, so every mailbox on one domain shares that record. See Domain Setup for authenticating each sending domain.

Sending Checklist

What Campaign ramp, send spacing, the bounce pauses and the address checks do, and what a provider block pause means.

These controls are on for a new campaign, and the list is yours to check. Each row says what the control does and what is left for you.

FieldDescriptionDefault
Start slow with Campaign rampNew campaigns start with Campaign ramp on. On its first sending day, each mailbox sends up to 5 emails for the campaign. It adds 2 more each sending day, up to 25 a day. Keep it on for a new list or a quiet mailbox.On for new campaigns
Space the emailsBy default, emails from one mailbox are never closer than 9 to 15 minutes apart, at random, and each mailbox spreads its day’s emails across its send window. Keep this spacing for cold email, or set a longer gap.
Keep bounces lowKeep your hard bounce rate low. A mailbox pauses above 2%, and a campaign above 3%. A higher rate tells providers that your list is old or unchecked.
Check addresses before you importEvery import checks that each new lead’s domain has a mail server. If your workspace has address checking, Laureo also checks each new address after the import. If it does not, run your list through an email verification service first, remove the addresses it marks invalid, and leave out the ones it cannot confirm.
Provider block pauseSometimes a mailbox provider blocks your emails because they look like spam. Laureo then pauses that mailbox for new cold emails, and the mailbox card says why. The pause ends on its own, and the mailbox starts sending again without you, at half its daily cap at first. Provider Block Pause, above, has the detail.

Why Laureo Does Not Offer Warmup

An honest take on a popular but dishonest tactic.

Many cold-email tools advertise automated “warmup”: networks of mailboxes that email each other and auto-reply to fake an engaged sending history and trick spam filters into trusting a new mailbox. Laureo deliberately does not offer warmup, and here is the honest reasoning.

  • Warmup fakes a signal, and industry guidance advises against it. The sender guidance of M3AAWG, the industry's anti-abuse working group, says that “artificial warming practices are not recommended and may be illegal” (M3AAWG Sender Best Common Practices). Email providers' usage policies also forbid using their service to evade spam filtering. A tactic built on deceiving the filter puts the mailbox at risk.
  • It manufactures engagement you did not earn. Warmup replies are bots talking to bots. The only durable way to earn inbox placement is to send wanted email that real people actually reply to, which is what a well-targeted, honest sequence does.
  • Laureo sends real mail only. Each mailbox sends your own emails, from an authenticated domain, to the list you built, inside its managed ramp and its enforced per-mailbox limits. Its sending history is then made of real mail. That is slower than a warmup shortcut, and it is real.
The Laureo posture
Laureo does not offer warmup. It sends your real mail with these controls: a managed ramp that raises each mailbox's daily limit step by step, a campaign ramp, per-mailbox and per-domain pacing, enforced caps, send windows in each recipient's time zone, jitter, and automatic pauses for bounces and provider blocks.