Help Center

Docs

Deliverability

How managed ramp, per-mailbox pacing, send windows, jitter, and bounce auto-pause keep your cold email landing, and why Laureo does not offer warmup

Managed Ramp Explained

Volume grows gradually as a mailbox's connection ages.

A brand-new sending mailbox that suddenly blasts hundreds of cold emails looks exactly like a compromised account to a mailbox provider. Laureo prevents that with a managed ramp: each mailbox starts at a conservative daily volume and steps up through a fixed schedule of three stages as its connection ages. The ramp is automatic. You do not configure it, and you cannot push a mailbox past its current stage.

FieldDescriptionDefault
Ramp scheduleA new mailbox sends up to 10 cold emails per day in its first week, 20 in its second, and 30 from its third week on. The mailbox card shows which week it is on and the date your own limit takes over.10 / 20 / 30 per day
Per-mailbox recommendationAbove 50 cold emails per day from one mailbox, Laureo warns you that deliverability suffers. It is a recommendation, not a block. The hard ceiling is the one your provider enforces, around 2,000 per day.50/day recommended
Ramp driverHow long the mailbox has been connected, and nothing else. Each completed week moves it to the next stage.
More mailboxes, more total volume, same per-mailbox limits
Because each user can connect up to 5 mailboxes, total daily reach grows with the pool while every individual mailbox stays inside its enforced per-mailbox limit. Laureo rotates sends across the pool and respects each mailbox's own pace. The rotation rule is simple: each new conversation opens from whichever selected mailbox has sent the fewest cold emails in the last 24 hours, so the pool evens out on its own. Once a conversation starts, it stays on that mailbox for every follow-up, which is what keeps a thread reading as one person writing to one person.

Per-Campaign Daily Send Limit

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

Each campaign carries its own optional Daily send limit for this campaign, set in the sequence's settings. It caps the emails that one campaign sends in any rolling 24 hours, totaled across every mailbox that campaign rotates through. Two details matter: the window is a rolling 24 hours, not a calendar day, so it does not reset at midnight, and follow-ups count against it alongside first touches. Leave it blank (the field reads “No limit”) and the campaign has no limit of its own, so it sends as fast as the mailboxes and the ramp allow.

FieldDescription
Per-mailbox daily limitProtects a single mailbox and its sending reputation. It applies to that mailbox across every campaign that sends through it, and is set on the mailbox card (recommended 30 per day).
Per-campaign daily limitPaces one campaign as a whole, first touches and follow-ups together, over a rolling 24 hours. It applies only to that campaign, across all the mailboxes it uses, and is set in the sequence settings. Blank means no campaign limit. To limit first touches only and leave follow-ups free to go out, use New leads contacted per day instead, in the same settings.
The real pace is the smallest of the three
A campaign never sends faster than the smallest of three numbers: its own daily limit, each mailbox's daily limit, and the managed ramp on each mailbox. Raising the campaign limit alone does not speed sending past what the mailboxes and the ramp allow, which is why a new campaign on fresh mailboxes still starts slow even with a high campaign limit.

Because the limit is per campaign, you can run several campaigns at different paces at once: give a priority campaign a higher limit and a background campaign a lower one. One caveat: campaigns that share a mailbox share that mailbox's daily budget, so two campaigns sending through the same mailbox draw from the same per-mailbox allowance rather than each getting a full one.

Per-Campaign Send Controls

Shape how many first-touch emails a campaign starts, and who it favors.

Alongside the daily send limit, a campaign's settings carry three controls that shape its first-touch volume and its ordering. They pace how a campaign opens new conversations without touching the follow-ups already in flight.

FieldDescription
New leads contacted per dayThe most first-touch (step 1) emails this campaign starts in a day. Follow-ups to leads it has already contacted are not counted against it. Leave it blank for no limit of this kind.
Leads per companyThe most leads at any one company this campaign enrolls, matched by their email domain so it never piles onto a single organization. Personal-email providers are never limited. Blank means no limit.
Contact new leads firstA checkbox that, when sends are due, starts first-touch emails to never-contacted leads before sending that campaign’s follow-ups.

Send Windows and Jitter

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

Sends are placed inside each recipient's business hours, computed from their timezone, so your email arrives when a person is actually at their desk rather than at 3 a.m. their time. Within the window, Laureo adds jitter, randomized spacing between sends, so a mailbox never fires a burst of identical-looking messages on a fixed cadence. The result reads like a person sending one email at a time, not a machine.

The spacing is stated, not hidden. Under Mailboxes in Cold Outreach settings you will find the exact band: Emails from one mailbox go out 90 to 140 seconds apart, at random, so your sending never settles into a fixed cadence. That band is the floor, and 90 seconds is the lowest value anything can ask for: a campaign can only make a mailbox slower, never faster. Each campaign carries its own minimum time between emails from the same mailbox, anywhere from 90 seconds to 30 minutes, and new campaigns start at 2 minutes. The number you set is a minimum, not a fixed cadence: Laureo adds a random extra of up to half again on top of every wait.

All of this is measured per mailbox. Different mailboxes send independently of each other, because each one carries its own sender reputation and is judged on its own sending pattern, so two of your mailboxes can send at the same moment without either of them looking rushed.

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 timezone, 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 timezone, 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

Protecting the recipient's domain as well as your own.

Laureo also paces by recipient root domain. Sending too many messages too quickly to the same company domain looks like an attack to that company's mail server, so volume to any single root domain is spaced out. A higher-volume threshold (around 5,000 messages per day to one root domain) applies to large consumer domains. This keeps you from tripping a recipient organization's own rate defenses.

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.

Bounce-Rate Auto-Pause

A mailbox that starts bouncing is paused before it gets blacklisted.

Laureo watches each mailbox's rolling bounce rate. If it climbs above 2%, the mailbox is automatically paused for new cold sends. A high bounce rate is the fastest way to get a domain blacklisted, and pausing early protects the mailbox. Replies still send while a mailbox is paused; only new cold steps hold. You resolve the cause (usually a stale slice of your list, or addresses that were never accurate) and resume. See Troubleshooting for the resume flow.

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, and which host that is depends on your setup. Today there is no standard tracking host, and the flow for adding a tracking domain of your own is not switched on either, so open and click tracking cannot be turned on for a sequence and the two switches on the sequence stay inert. Once a tracking domain you own is verified, tracked links and the unsubscribe header run on it. The Custom tracking domain card, at the top of Cold Outreach settings, always states which of these 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 first.

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.
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 one is verified, the unsubscribe address in your emails is built on your Laureo app domain, 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 timezone. 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.

Spread Mailboxes Across Domains

A few mailboxes on each of several domains beats many on one.

As you scale up, how you arrange mailboxes across domains matters as much as the raw count. Best practice is 2 to 3 mailboxes per domain, spread across several sending domains, rather than piling many mailboxes onto one domain. If a single domain picks up a reputation problem, only the mailboxes on that domain are affected and your other domains keep sending. It also keeps the volume on any one domain modest, which is how real senders look. See Domain Setup for authenticating each sending domain.

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 mailbox providers are getting better at detecting. Gmail and Microsoft increasingly recognize warmup-network traffic and discount or penalize it. A tactic built on deceiving the filter ages badly as the filter improves.
  • 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.
  • The honest path works. A gradual managed ramp on an authenticated domain, sent to a list you built carefully and within enforced per-mailbox limits, builds a genuine clean-sending reputation. That is slower than a warmup shortcut, and it is real.
The Laureo posture
Instead of warmup, Laureo gives you a managed ramp, per-mailbox pacing, enforced caps, recipient-timezone send windows, jitter, per-domain pacing, and bounce-rate auto-pause. The framing is deliberate: real deliverability comes from sending mail people want, not from gaming the filter.