Exact values
In short
What limits apply in Reply?
A mailbox's daily sending cap is set by your plan and always wins over a higher sequence setting. A sequence can be configured up to 10,000 emails a day across at most 100 mailboxes. The API accepts 100 requests a minute and 3,000 an hour, on top of a monthly quota set by your plan.
A mailbox's daily sending cap is set by your plan, and it always wins over a higher sequence setting. A sequence can be configured up to 10,000 emails a day across at most 100 mailboxes. The API accepts 100 requests a minute and 3,000 an hour, on top of a monthly quota set by your plan.
Limits stack across levels: the mailbox's own daily cap beats a higher sequence setting, and plan quotas ( active contacts, storage, credits) sit above both.
Where to find your limits
Several limits below depend on your plan. To see the values that apply to your account:
| Limit | Where you see it |
|---|---|
| Emails per day for a mailbox | Settings → Email Accounts → the mailbox → Safety |
| Emails per day for a sequence | The sequence's settings, next to its toggle |
| Active contacts this billing period | Billing, and on hover over a sequence toggle |
| Contact storage | Billing |
| LinkedIn actions per day | Settings → LinkedIn Accounts → the account |
| API requests this month | Billing |
Plan comparisons live on reply.io/pricing.
Email sending limits
| Limit | Value | Level |
|---|---|---|
| Emails per day per mailbox | Set by your plan. A new mailbox starts at your plan's default and can never be saved above your plan's maximum – both are plan values, and they are not the same number | Email account |
| Max number of emails per day | Configurable up to 10,000, cannot exceed the sum of account daily limits | Sequence |
| Max daily emails per contact | Default 1, can be raised (for Team Edition multi-sequence cases, 2–3) | Sequence |
| Delay between emails | Configurable from 20 seconds to 24 hours. When a maximum delay is also set, each send is placed at a random point between the minimum and the maximum | Sequence / email account |
| Email accounts per sequence | Up to 100 | Sequence |
| Bounce-rate stop | A sequence stops sending its first step once its bounce rate crosses Reply's threshold for the day, and resumes automatically the next day. A warning appears before the stop, and the sequence shows its current rate – see Bounce handling | Sequence |
| Sending window | A schedule needs a delivery window of at least 2.5–4 hours to send reliably – see Schedules | Schedule |
The Max daily emails per contact and account limits do not apply to Manual email steps.
Contact limits
| Limit | Value |
|---|---|
| Contact storage | Set by your plan; support can raise it. See reply.io/pricing |
| Active contacts | Set by your plan. Follow-ups to someone already counted this period are free |
A contact counts as active when they receive at least one outreach step (email, LinkedIn connection request, LinkedIn message, or InMail) during a billing month. The count resets on the subscription renewal date, not the calendar month. A contact reached again in a new billing month counts again.
Email account allowances
How many mailboxes are included, and how many you can add, are both set by your plan. On the volume-based plans the included mailbox count scales with your active-contact tier.
See your own allowance in Billing, and plan comparisons on reply.io/pricing.
API and integration limits
| Limit | Value |
|---|---|
| API rate limit | 100 requests per minute and 3,000 per hour (v1, v2 and v3) |
| Reporting endpoints | 500 per hour |
| API requests per month | Set by your plan |
See docs.reply.io for endpoint-level detail; it is the source of truth for the API surface.
LinkedIn automation limits
| Limit | Value |
|---|---|
| Daily cap per action type | Set by your plan, per LinkedIn account. Open Settings → LinkedIn Accounts → the account to see the caps in force on yours |
| Limit changes take effect | The next day |
AI SDR (Jason AI) source limits
| Limit | Value |
|---|---|
| Monthly contacts sourced | Set by your plan. Shared across every AI SDR contact source – Autopilot, web search and the buying-intent signals draw on one allowance, and it resets on your billing month |
| New contacts per day per sequence | Up to 500; default 10 |
| Contacts a single source returns per run | Up to 500, whatever you request |
| Contacts per company | Default 3; configurable |
| Post-engagement sources | Intake per post per day is capped |
| Competitor and post sources | Up to 10 LinkedIn addresses per source |
| ICP fit threshold | A choice, not a cap: 20, 40, 60, 80 or 100%. Generated sequences are pre-filled at 60% |
| Web-search preview | Valid for 30 minutes. If setup takes longer, the search does not start |
| Generated playbook draft | Held for 1 hour, and discarded if you leave the setup without continuing |
If you ask for more than the allowance has left, the request is quietly reduced rather than refused. See Why did a lead source add no contacts?.
Data credits
| Credit grant | Value |
|---|---|
| Credit grant | Set by your plan – see reply.io/pricing |
What each lookup costs, and whether a miss is refunded:
| Action | Credits | If nothing is found |
|---|---|---|
| Enrich from a LinkedIn profile | 1 | Charged – the credit pays for the lookup |
| Find an email address | 2 | Refunded |
| Find a phone number | 3 | Refunded |
| Enrich from an email address | 1 | Refunded if the contact could not be updated |
| Validate an email address | 1 | Charged – an undeliverable verdict is a result |
These share one balance, with one exception: email validation draws on a balance of its own. A LinkedIn step in a sequence collects profile data at no credit cost. AI SDR sourcing is not charged in credits; it draws on the monthly contact allowance above. The in-product assistant is not charged in credits either; it has a daily message allowance set by your plan.
Purchased domains and mailboxes
| Limit | Value |
|---|---|
| Mailboxes per domain | Up to 5 |
| Ready-warmed package | Exactly 1 domain and 3 mailboxes, bought and cancelled as one unit |
| Provisioning time | First mailbox usually within minutes; full completion up to 48 hours |
| Domain renewal window | From 45 days before expiry until 1 day before. No grace period afterwards |
| Ready-warmed packages | Cannot be renewed |
| Reconnecting a purchased mailbox | 7 attempts per 7 days, with a 60-minute wait between manual attempts. The on-screen message and countdown may state this incorrectly |
| Microsoft mailbox lock | 4 days after creation for a regular purchase; ready-warmed Microsoft mailboxes are not locked |
LinkedIn search import
| Limit | Value |
|---|---|
| Results per LinkedIn account per day | 2,000, counted per calendar day |
| Searches at once | One per LinkedIn account |
| Requirement | A LinkedIn account with Sales Navigator |
Which limit wins
The more restrictive of the two always wins. For volume that means the smaller number: a mailbox never exceeds its own daily cap regardless of the sequence's Max number of emails per day, and the sequence cap never exceeds the sum of its mailboxes' caps. For pacing it means the longer wait: where the mailbox and the sequence both set a delay between emails, the longer one applies. Daily capacity is snapshotted once per day at UTC midnight. See Sending schedules.
FAQ
Can I raise a mailbox's daily sending limit?
Yes, up to the maximum your plan allows: Settings → Email Accounts → the mailbox → Safety. Raise it gradually: a sudden jump in volume is what providers react to. You can also spread sending across more mailboxes, up to 100 per sequence, with round-robin distribution.
Do manual emails count against the limits?
Emails sent through Manual email steps are exempt from the Max daily emails per contact and daily sending limits. See Sequence steps.
What happens when the API limit is hit?
Requests over 100 per minute or 3,000 per hour are rejected with 429 until the window clears, and a separate monthly quota set by your plan applies on top. Batch your calls and back off on 429. See docs.reply.io.
Related
Build with Reply
- REST API: Rate limits – request quotas and error codes
- MCP: docs.reply.io/mcp – read and change account limits from an assistant