How Many Cold Emails Can You Send Per Day?
There is no universal number of cold emails you can send per day without affecting deliverability. In Unify, new managed mailboxes default to 25 sends per day, new connected work mailboxes default to 150, and the documented standard maximum is 150 per 24 hours. These are product settings—not guarantees of inbox placement or recommended volumes for every sender.
Your operating limit must account for current mailbox readiness, provider requirements, recipient quality, other sending activity, and the follow-ups already in the queue. Check the actual mailbox setting rather than relying on a remembered default or a domain-age formula.
What do the current Unify limits mean?
The sending limits documentation describes the current behavior. All sequences using a mailbox share its capacity. The sequence schedule controls when eligible messages may send, and follow-ups consume capacity alongside first touches.
| Setting or state | Documented behavior | Planning implication |
|---|---|---|
| New Unify-managed mailbox | Default of 25 sends per day | Check warmup, ramp state, and the actual setting |
| New connected work mailbox | Default of 150 sends per day | Account for direct sending and other tools as well |
| Standard maximum | 150 sends per 24 hours | A ceiling is not a deliverability recommendation |
| Warmup | Allow about three weeks; inspect the estimated completion date | Provisioning a mailbox does not make it immediately ready |
| Ramp-up, where enabled | Capacity increases by five sends per day toward the limit | Today's available capacity can be below the configured maximum |
| Shared mailbox usage | All sequences share the mailbox's capacity | Do not allocate the full limit separately to each sequence |
Existing mailboxes can have different settings. Administrators control limits, and user-adjustable limits are bounded by the administrator's configuration. Increasing the maximum can restart ramp-up. Inspect the current daily capacity when it is shown.
The managed mailbox guide explains the provisioning path. The connected mailbox guide covers existing work accounts. They have different setup and ownership considerations, even when both appear in the same outbound workflow.
Is a provider allowance a safe cold-email target?
No. A mailbox provider's technical allowance, a platform's configured limit, and the volume appropriate for a particular audience are different constraints. The most restrictive applicable condition may determine what can be sent, but being below a technical ceiling does not prove the campaign is healthy.
Google's sender guidelines and Yahoo's sender best practices describe requirements for their services. Apply the conditions relevant to your sender category and message type. Do not turn a threshold in those policies into a universal cold-email recommendation.
Authentication, complaint handling, recipient expectations, and list quality still matter below a published threshold. Adding mailboxes or domains does not eliminate those requirements. Nor does a successful API response establish that a message reached the inbox.
Review domain configuration and inspect a real authorized test message. Confirm the sender identity and reply path as well as authentication. A correct DNS record is necessary setup evidence, not a forecast of recipient response.
Does domain age determine a safe daily volume?
Age alone is not enough. A long-established domain can have poor sending practices, and a recently provisioned mailbox needs more than elapsed time to become suitable for a campaign. Evaluate actual sending history, current state, authentication, audience quality, and recent results.
Warmup is an operating process, not an inbox-placement certificate. Unify's documentation distinguishes Warming, Ramping, and Warm states. Even a warm mailbox remains subject to limits and schedules, and its campaign can still perform poorly with an inappropriate audience.
Avoid formulas that assign a guaranteed safe volume solely from the age of the domain. If a guide presents a range, inspect the population and evidence behind it. A platform default should be labeled as a default rather than converted into a universal best-practice benchmark.
How do you calculate available first-touch capacity?
Choose a planning window that matches the mailbox's actual limit behavior. At the snapshot, inspect current available capacity, due follow-ups, other scheduled messages, and any operating reserve. Keep warming, paused, or unauthorized senders out of the available pool.
A useful scheduling identity is:
Available first-touch slots = current approved capacity − due follow-ups − other scheduled campaign messages − reserved capacity.
Treat a negative result as zero available first touches and resolve the excess workload. This equation allocates capacity; it does not predict deliverability. For connected work mailboxes, review direct email and other-tool activity as an additional constraint even when it is outside the sequencer's queue.
Use mailbox groups to understand how new enrollments are distributed. Distribution does not create extra capacity within a mailbox. Send schedules can further restrict the usable sending window.
| Capacity worksheet field | Value at the planning snapshot |
|---|---|
| Mailbox and current state | |
| Configured maximum and current ramp capacity | |
| Capacity already consumed in the applicable window | |
| Due follow-ups and other scheduled messages | |
| Relevant sending outside this tool | |
| Operating reserve | |
| Eligible first-touch recipients | |
| Owner available to handle replies |
Do not fill unused capacity with lower-quality recipients just to reach a target. The sustainable prospecting guide connects sender capacity with audience and response-handling capacity.
Why are messages queued even below the limit?
A message must satisfy the preceding steps and delays, the allowed send window, and available mailbox capacity. Some work also requires a manual action or approval. The configured maximum alone does not explain the whole queue.
Inspect sequence enrollments for the actual status, upcoming step, sender, and warning. A blocked enrollment is different from one waiting for a schedule. Correct the diagnosed condition rather than increasing the limit as a generic remedy.
The sending-limits documentation also describes the Email backlog dashboard for comparing queued work and capacity. Use that view with record-level inspection. A summary can show a bottleneck without explaining why a specific person's message is waiting.
If a mailbox loses authorization or develops persistent problems, read mailbox operations before disconnecting or reconnecting it. Those actions can affect routing and enrollments. Recovery should preserve what already sent and avoid duplicate attempts.
What should you monitor as volume changes?
Monitor confirmed delivery failures, complaints where available, opt-outs, classified human responses, and the team's ability to act. Separate recipient and message counts. A person who receives several messages should not be counted as several distinct prospects in a person-level response measure.
For a hard-bounce proportion, define the population as attempted campaign messages in a stated window and count confirmed hard bounces as the numerator. Preserve pending outcomes and the reporting cutoff. For positive responses, use distinct contacted people as the denominator and distinct people with a classified positive human reply by the cutoff as the numerator. Keep unclassified replies separate. A zero denominator is not applicable in either measure.
Use sequence results to inspect execution and sequence replies to review the actual conversations. Open events can be affected by automated activity and should not be treated as proof that a person read the message.
There is no single bounce percentage that certifies every campaign as safe. Apply provider requirements, your defined operating rules, the seriousness of the event, and changes from an appropriate baseline.
When should you pause or reduce sending?
Pause the affected work when authentication fails, restrictions are breached, sender identity is wrong, replies lose ownership, or recipient outcomes materially deteriorate. A complaint or opt-out requires the appropriate handling even when total campaign metrics appear acceptable.
Review sequence exclusions before resuming. Remove invalid or ineligible recipients through the correct process and preserve the reason. Do not replace a rejected address with another route to the same person simply to continue an unwanted pitch.
Resume with a bounded cohort after the cause is repaired and the required checks pass. Change one major variable at a time where practical. If you alter the audience, message, mailbox pool, and schedule together, it becomes difficult to know which change mattered.
The cold-email launch guide provides the broader readiness checklist. For an established program, apply the same principle to each expansion: current capacity and recipient outcomes determine the next step, not the desire to maximize a send counter.
Frequently asked questions
How many cold emails can I safely send each day?
There is no universal safe number. Check provider requirements, current mailbox settings and readiness, audience quality, other sending, follow-ups, and recipient outcomes. A technical limit is not an inbox-placement guarantee.
What are Unify's current default mailbox limits?
The documentation lists 25 sends per day for new Unify-managed mailboxes and 150 for new connected work mailboxes, with a standard maximum of 150 per 24 hours. Existing settings and ramp capacity can differ.
Do follow-ups count toward the mailbox limit?
Yes. All sequences using the mailbox share its capacity, and follow-up emails consume capacity alongside first touches. Plan the combined queue rather than allocating the full limit to every sequence.
Does completing warmup mean I can immediately use the maximum?
No. Current ramp capacity, mailbox settings, schedules, provider requirements, and actual campaign conditions still apply. Warm status is not proof that the maximum is appropriate for your audience.

