Skip to main content
Existing limits in Reply

Learn more about active contacts, import, daily emails per account, or sequence limits

Reply Team avatar
Written by Reply Team
Updated over 3 months ago

Limits in Reply can be separated into a few groups. In this article, we will cover all the groups and will see what limits influence the sending most:

  • email-related

  • contact-related

  • integration-related

  • feature-related

Email-related limits

The first limit that influences the sending is the Total number of emails. The maximum value sent daily from one email account is 400 emails for the paid plans, 200 for the trial accounts, and 1 for the Freemium.


The other limit is the Max number of emails per day that is managed inside the sequence. It cannot exceed the limit of emails per email account a day.


If you want to send multiple emails to one contact daily, the Max daily emails per contact limit is what you need. The default value is set to 1 but you may increase it.


💡 Important: The above limits do not apply to emails sent within the Manual email step. Team Edition lets you push the same prospect to several sequences of different team members. In this case, you can change the default value to 2 or 3.

Every new Reply user has 2 email accounts included in the Trial period. Paid Sales Engagement plans include:

  • unlimited mailboxes on the Email Volume plans;

  • 5 email accounts on the monthly Multichannel plan and 10 mailboxes on the annual plan;

  • unlimited mailboxes on the Agency plans;

You can also connect as many additional mailboxes as you need for $29/month each.

Contact-related limits

The default Prospects limit in the Reply account is 100,000 on all Business and Agency plans. If you cannot upload more contacts, our Support team can raise the limit upon your request:


The Active Contacts limit is the number of unique recipients who receive at least one email from you within a given month. Here’s how it works:

  • One Contact = One Count: If a contact receives even a single email (whether it’s Step 1 or Step 10, part of the same sequence, or a new one), they are counted as an Active Contact for that month. This limit resets with your subscription renewal date, not at the beginning of the calendar month.

  • If a follow-up email is sent to a contact in a different month, they will count as an Active Contact again for that new month. For example, if you sent an email to Contact A during January's billing cycle, they would count toward January's limit.

    If their follow-up email is sent during February's billing cycle, they will also count toward February's limit.

The limit varies based on your subscription plan:

  • Email Volume Plans: These plans offer flexible limits starting at 1,000 active contacts and scaling up to 5,000, 10,000, 25,000, 50,000, 100,000, or more, depending on your chosen plan.

  • The Multichannel Plan comes with unlimited active contacts.

  • During the trial, it's set to 300, so you can email 300 unique contacts. Follow-up emails are not used in the count.

Integration-related limits

  • 15,000 requests a month for API requests.

  • 10 seconds limit between API calls.

  • The limit for syncing contacts = the limit for prospects.

Feature-related limits

As a new user, you get 200 Data credits to explore Reply's database. This limit differs for each plan, so here is what you can get after the upgrade:

  • Email Volume Plans: 1,000 Data credits per month for both monthly and annual plans.

  • Multichannel Plans: 1,000 Data credits per month for the monthly plan & 10,000 Data credits per month for the annual plan.

AI and Live Data credits can be used for generating personalized emails, icebreakers, and searching for contacts in Live Data. Our subscription plans cover:

  • 50 AI and Live data credits per month for both monthly and annual plans in Email Volume and Multichannel plans.

If you want to use LinkedIn automation in your campaigns, you need to set up LinkedIn limits.

Each interaction is limited to 30 but our Support team can increase it if requested.

Did this answer your question?