Sending Accounts
Connect the mailboxes that send cold email, set the name and the daily limit recipients feel, and read pool health
A sending account is a real mailbox, on Google Workspace or Microsoft 365, that Laureo connects and then uses to send cold-sequence steps and receive the replies. Cold sequences send only from these mailboxes, never from your Laureo inbox. They live on the Mailboxes tab, one card each.
A larger pool syncs the same way a small one does. Every mailbox keeps its own connection, its own daily cap and its own reply sync.
Connect mailbox opens a short explainer before it sends you anywhere. It opens with one sentence: cold outreach sends from a work mailbox that you connect here. Under that sit three named parts.
| Field | Description |
|---|---|
| What you’ll need | The two things that decide whether the sign-in can succeed: a work email account on a business domain (free personal accounts cannot send cold outreach), and a mailbox that is not already connected to Laureo as an everyday inbox or a support mailbox. |
| Choose your provider | Two buttons, Google Workspace and Microsoft 365. Either one takes you to your provider to sign in and grant access, then brings you back to the Mailboxes tab. The line underneath says exactly that. |
| Good to know | The three things worth knowing before you decide: access is mail-only, to send and read replies, with no calendar, no contacts, and no files; sending starts on a managed ramp with daily caps so volume grows gradually; and a mailbox that you already use every day can send cold email, as long as it is not your Laureo inbox. |
That is the first-connect version. Once you have one mailbox the control reads Add mailbox, the explainer is titled Add a sending mailbox, and everything except the lede and the provider choice folds behind a closed What you'll need toggle. Open it if you want the detail again; otherwise a repeat connect is two clicks.
Connecting a sending mailbox is not tied to being an admin. Any role can do it, provided the person holds an owner or power seat. Collaborator and viewer seats are fenced out, and a connect attempt from one comes back to the Mailboxes tab with a message rather than completing. If your organization is on a plan without Cold Outreach, or sending has been suspended on the account, the connect is refused the same way.
Microsoft 365 adds one step for some tenants: a tenant administrator has to approve Laureo once, for the whole tenant. In that case Microsoft shows its own page during the sign-in that says administrator approval is needed. Ask your administrator to approve Laureo for the tenant. After your administrator approves, connect again and it goes through. When Microsoft sends the missing approval back to Laureo, the Mailboxes tab also says so and gives you the approval link to pass on.
The status is a coloured dot and a short label. There are four, and they are derived from the mailbox itself, so nothing has to be refreshed by hand.
| Field | Description |
|---|---|
| Sending | Connected, authenticated, and sending inside its current daily cap. The normal state. When a sending mailbox needs your attention, the status names why in the warning colour and the mailbox keeps sending: "Sending, provider refused mail", "Sending, blocked recently", "Sending, recipient servers refused mail" or "Sending, replies delayed". When more than one applies, the status shows the first of these, and the lines under the card header give the detail. "Sending, replies delayed" means the provider connection that delivers replies has lapsed or could not be set up, so new replies arrive late. A line under the status says so. Laureo retries that connection on its own. Reconnect to re-register on the card sends you back through the provider sign-in and restores live sync now. To pause that mailbox, open the card's more actions menu and choose Pause sending. |
| Paused | Sending is held. Either you pressed Pause sending, or Laureo paused it: its bounce rate crossed the safety threshold, a mailbox provider blocked its mail, or your email provider limited its sending. A pause you set holds only new cold steps, and your replies still send. A pause Laureo sets also holds your replies from that mailbox until it resumes. A line under the card header names the cause and what ends it, for example "Paused: bounce rate 4% · acknowledge to resume", "Paused: provider blocked 2 messages · resumes in 23 h" or "Paused by you". A teammate who looks at your mailbox reads "Paused by its owner". When Laureo pauses a mailbox for its bounce rate, a sender restriction, a failed sender authentication check or a blocked domain, it keeps reading the mailbox's replies and opt-out requests for 30 days after its last send. Sending stays off. A line on the card gives the date this reading ends. After that date, or when the mailbox's sign-in stops working, the line reads "Laureo no longer reads this mailbox. Read its inbox for replies and opt-out requests." |
| Setup required | The mailbox is connected but not ready: its domain authentication has not passed. Re-check now re-runs the DNS lookup and nothing else. |
| Disconnected | No longer sending. It stays on the grid so you can reconnect it or take it off the pool for good. A mailbox the system paused for a sender restriction, a failed authentication check or a blocked domain also shows here, and Laureo still reads its replies for 30 days after its last send. A mailbox you disconnect yourself is not read at all. |
Laureo also reads the notices your email provider sends about a mailbox, on Google Workspace and on Microsoft 365: a sending limit, or a refusal of its mail. The card counts them in one line. A sending limit pauses the mailbox, and a refusal reads "Sending, provider refused mail". Laureo alerts you about a sending limit, and about a refusal of mail that another tool sent from the mailbox.
When a provider gives a reason a mailbox stopped, the card states it above the numbers, together with the fix. Two other notices can appear there: a warning when the mailbox is on your primary company domain (email providers track sending volume and feedback per domain, so cold email from it shares one record with your company email), and the managed-ramp badge described below.
After a provider block pause ends, the card keeps one muted line about the block until the 7-day repeat window closes, for example Your email provider blocked mail from this mailbox on November 5, 2026. Sending resumed automatically. Another block before November 12, 2026 pauses it for 48 hours. Under the bounce trend, Refused by provider (14d) counts the emails your email provider refused in the last 14 days that were not sent again. A refusal is not a bounce. When mail servers at 3 or more recipient domains refused email from the mailbox in the last 7 days, one more line says so and asks you to review its content and sending domain.
Each card shows a From name row: the sender name that appears next to your subject line in the recipient's inbox. Edit opens Mailbox settings, where From name is the first field. It holds up to 120 characters and its note reads Shown to recipients as the sender name. Defaults to your profile name.
- Leave it blank and your profile name is used. The card then says Taken from your profile name. Recipients see it next to the subject line. Change your profile name and the sender name follows it.
- Type a name and that name is used instead, for this mailbox only. The card drops to Recipients see this next to the subject line.
- With neither, recipients see the bare address. The row reads Not set and the note names the consequence in full: Recipients see you@yourdomain.com with no name next to the subject line.
Each sending mailbox can carry its own signature. On the mailbox card, open Mailbox settings and fill in Signature. It is plain text by default; Use formatting opens the editor for bold, italic and a link. The note under it says: Sent after a -- line, in this mailbox's own emails. Leave it empty to send none. No images and no {{fields}}: it is the same in every email. One website link at most. A mailbox signature always sends after the -- line, in the plain text and the formatted version of the email alike.
Replies go to, in the same dialog, sets where a reply goes. Leave it empty to receive replies in this mailbox. With an address in it, every cold email from this mailbox names that address as the one to reply to.
A mailbox with no signature of its own can use one of your inbox signatures. Open Email settings (the gear in the inbox toolbar, or Settings > My preferences > Email inbox), go to Composing, and find Signature by inbox under Dashes above your signature. It lists each of your sending mailboxes by address, and each one offers No signature, the default, or one of your signatures. The rules below are for these inbox signatures.
- Cold emails get a plain version. The row says it: Cold emails get a plain version: your words and links, no images or layout. Your words and links stay, and so does bold, italic or underlined text, whether you added it with the signature toolbar or it came in a signature you pasted or imported. Pictures, colors, fonts and spacing are left out.
- Designed signatures stay out of cold emails. A signature with a designed layout is not offered here, because cold emails keep to plain markup. If one you picked becomes designed later, that mailbox sends without a signature and the row reads This signature has a designed layout, so cold emails go out without it. Pick a plain one.
- It sits between your message and the opt-out footer, which still closes the email when your footer style has one. With Dashes above your signature on, a
--line sits above it. A plain-text-only sequence sends the text version, with each web link's address written out. - Its links are treated like the links in your message. With click tracking on, a link in the signature is tracked the same way.
- It is not personalized. Personalization fields are not filled in inside a signature.
- Your off switch wins. If signatures are turned off in your email settings, a mailbox with no signature of its own sends none either. A mailbox signature is not affected.
- A mailbox uses its owner's choice, from that person's own signatures. Nobody else's setting or signature applies to it.
The Daily limit row sits under the From name, and its Edit opens the same Mailbox settings dialog. An unset limit reads 30 per day (default). Clear the field to go back to the default at any time.
- Above 50 per day from one mailbox, Laureo warns you. It is a recommendation, not a block.
- Your provider enforces its own hard ceiling, around 2,000 per day. You cannot set a limit above it.
- A new mailbox is still ramping, and a quiet mailbox restarts low, so a raised limit does not take effect immediately. The real cap today is whichever is smaller.
Every mailbox carries a ramp badge. A 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. The ramp lasts the same 3 weeks it has always had (about 10, 20, 30 per day at the start of each week). The badge reads Ramp · day 10 of 21 · 23 per day while that is happening, and its info affordance states the rule that set the cap plus the date your own limit takes over. Once the ramp finishes the badge names the limit in force: Daily limit · 30 per day when your own limit sets the cap, Recent sending · 15 per day when recent sending holds it lower, or Provider limit when the provider's own ceiling is the one in force. After a provider block pause ends, the badge reads Recovering while the mailbox sends at a lower cap: half its daily cap for 48 hours, then 3 more each day until the cap is back in full. The line under the daily limit row says the same.
The ramp is driven by the connection age and 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. You cannot configure it or push a mailbox past its current stage. Sent today just below the ramp badge is the live count against the cap in force. It counts the current day in your workspace time zone (UTC when no workspace time zone is set by hand). Bounce trend (14d) below it is the signal to watch before raising anything.
Under that count, a strip of 24 slots shows when the mailbox sent in the last 24 hours: one slot for each hour of the day in your workspace's time zone, which is named beside the strip. The line under it gives the newest send, for example "Last send 23:41", with its day when it is older than 24 hours. A mailbox that never sent reads "No sends yet". A spread-out day fills many slots; a burst fills two or three.
This is the mailbox's own ramp. Each campaign adds its own Campaign ramp on top, which you set per campaign. See Deliverability.
In a campaign, three daily limits apply to each mailbox together. The first is the mailbox's own Daily limit. The second is that campaign's Campaign ramp for the day. The third is Recent sending. It allows at most 1.5 times the busiest day of the last 7 completed days. Sends from today do not count. It never goes below 10 a day. Each day the smallest of the three applies. A bigger ramp step cannot lift a mailbox past its Recent sending limit. For a new mailbox, the managed ramp above can be lower still.
Emails a mailbox sends outside Laureo count too, because your email provider counts every email the mailbox sends. Laureo reads the mailbox's Sent folder and counts what it sent in the last 24 hours that no campaign sent: a manual send, a reply, or another app's email. They count against the mailbox's Daily limit, so campaigns send only what is left of it. The card shows the count, and the badge reads Outside sending when it sets the cap. When a mailbox has not synced for a while, the count is what its last sync saw. A mailbox you just connected or reconnected can wait for its first sync, so its count is known before campaigns send from it.
Laureo also reads each mailbox's own sending record from its Sent folder, every app counted: when you connect it, then once a day. A mailbox that sent 10 or more emails on fewer than 7 of the last 30 days starts slowly by itself: each day at most 1.5 times its busiest recent day, never below 10. With no record, that is up to 10, 15, 23, 35 a day in its first week. The badge reads Sending record while the record sets the cap. A mailbox with a steady record keeps its own daily limit once its first sent mail is at least 14 days old. The card's Sending record line shows what the read found.
When you connect a mailbox, on Google Workspace or Microsoft 365, Laureo also counts what its Sent folder holds from before it connected: the emails it sent on each of the 14 days before, and whether it sent anything 15 to 30 or 31 to 90 days before. Laureo counts messages only. It never reads or stores a message, subject or address. The card then reads, for example, "Before it connected, 120 sent on 12 of 14 days." Until the count is done, the card reads "Laureo has not yet counted what this mailbox sent before it connected." A mailbox Laureo cannot read shows "Laureo cannot see how this mailbox sent before it connected." A mailbox you connected earlier is counted once, within a few syncs. Mail deleted from the Sent folder before you connected is not counted.
The card also says how long ago the mailbox connected, for example "Connected 10 days ago." Its days of sending are those days plus the days it sent in the 14 days before it connected. While that is fewer than 14 days, the line adds, for example, "This mailbox has 10 days of sending that Laureo can see. Most sending tools wait 14 days of gradual sending before a first campaign. Keep Campaign ramp on and start low." Launch review and the mailbox picker show the same advisory. It never blocks a launch and never changes a cap. When the new-account hold is on, an account starts no new conversation for 14 days after its first sent mail, or after it connected if it had sent no mail before. Its card names the date. Follow-ups to people the mailbox already wrote to keep going. To start a mailbox's managed ramp again, open the card's more actions menu and choose Restart ramp: the ramp starts again from today, at its first stage. It takes no date, so it can only lower what the mailbox sends while it climbs. Laureo records who restarted it. While your workspace's managed ramp is off, a restart does not change how much the mailbox sends.
Each 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. The badge reads Today’s target when the day's number differs from the cap. Once 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. The badge reads Steady volume when that bound sets the cap.
Each 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.
Each domain heading on the Mailboxes tab shows what that sending domain sent in the last 24 hours. The total counts the emails Laureo sent from every mailbox on the domain, plus the emails those mailboxes sent outside Laureo. It counts a rolling 24 hours, not the calendar day.
Your email provider tracks volume for each domain as well as for each mailbox. At 80 or more a day, the heading adds an amber line: keep one sending domain under 100 a day. This is advice, not a block. Laureo's limits stay per mailbox.
A mailbox's daily limit counts every campaign that sends from it. When two campaigns use the same mailbox, each one sends less each day. The launch review says so before you launch, and names the mailboxes and the other campaigns. Use separate mailboxes for each campaign. This does not block launch.
Pause sending holds new cold steps from that mailbox and leaves everything else alone. Disconnect mailbox lives in the row menu and asks first: Sequences using this mailbox will redistribute new sends to your other mailboxes. Threads it already started keep their history but can no longer be replied to from Laureo. Laureo no longer reads this mailbox. Read its inbox for replies and opt-out requests. A mailbox that is already disconnected offers Remove from pool instead, which takes the card off the grid.
Disconnecting a Microsoft 365 mailbox in Laureo does not remove Laureo's approval at Microsoft. To remove it, sign in to My Apps at myapplications.microsoft.com with that mailbox. Select the more options button (...) on Laureo, choose Manage your application, then Revoke Permissions. When your administrator approved Laureo for the whole tenant, only an administrator can remove that approval.
Follow-ups in a conversation that a disconnected mailbox started wait for that mailbox, and they send after you reconnect it. First emails go out from the campaign's other mailboxes when it has any. When it has none, they wait until a mailbox is available. The lead rows say so either way. Reconnect it to resume. At your mailbox limit, disconnect another mailbox first: a disconnected mailbox counts again when it comes back. A mailbox that Laureo paused for its bounce rate is the exception. After a disconnect its card reads Disconnected, and the reconnect brings it back paused for its bounce rate until you resume it, so it reconnects even at your limit. To resume it at your limit, disconnect another mailbox first. The ramp picks up from where the connection age and recent sending put it, not from week one.
Two rules keep a system pause in place. Pause sending on a mailbox the system already paused changes nothing: the system pause and its cause stay, so Resume still asks you to confirm the cause. And a reconnect during a provider block pause keeps the pause until it ends or you resume the mailbox. After you resume it, a reconnect does not pause it again. See Deliverability.