Rémi KokabiNovember 4, 20267 min readLast update: Nov 4, 2026
The Reply.io limitations to check before you scale your outbound
Reply.io is a capable sales engagement platform, and plenty of teams run good outbound on it. The friction usually shows up later, when a team adds LinkedIn profiles, turns on calling, tries WhatsApp or starts sourcing most of its leads inside the tool. That is when the packaging and the way each channel works start to shape what you can do.
This article lists the concrete limits to check before you scale on Reply.io, channel by channel, and how lemlist handles each one. It stays on operational limits. For a full product review with ratings and a verdict, read our Reply.io review. If you are already shortlisting tools, see our list of Reply.io alternatives.
How to read this list
Everything below about Reply.io comes from its public pricing page and help center as of 2026. Pricing pages change often, so check the current version before you budget. We left prices and quotas out on purpose. The point is the structure, meaning what is bundled, what is billed separately and what still needs a person or another tool.
LinkedIn automation is an add-on billed per account
On Reply.io, LinkedIn automation is sold as a paid add-on, billed per connected LinkedIn account and on top of the user seat. Every rep who runs LinkedIn steps adds a line to the invoice, so the cost grows with the number of profiles, not only with the number of users.
The connection runs through a LinkedIn session, for example with Reply.io's Chrome extension, and you set daily safety limits for each action. When LinkedIn's own weekly invitation cap is reached, Reply.io pauses connection requests while other LinkedIn actions keep running. That behavior is sensible. It also means LinkedIn volume depends on how many profiles you pay for.
How lemlist handles LinkedIn
In lemlist, LinkedIn steps are part of the Multichannel Expert and Enterprise plans, next to email, with no separate per-account LinkedIn fee. A sequence can mix profile visits, invitations, messages, InMails from a Premium sender and voice messages. If an invitation fails, lemlist skips the remaining LinkedIn steps for that lead and moves to the next channel, so the lead keeps progressing.
Calls and SMS sit in a separate add-on
Reply.io's dialer, automated SMS, call transcripts and AI voice messages come with a Calls and SMS add-on. If calling is a regular part of your cadence, plan for that add-on on every seat that dials, and check how it is counted on the current pricing page, since the wording differs between sections.
How lemlist handles calls
In lemlist, calls run from the same place as the rest of the sequence. Call steps create tasks, reps dial from the in-app dialer and log an outcome after each call. Teams can add their own call statuses and attach automations to them, so a status like Connected can trigger the next action. For batches of call tasks, Power Dialer dials each number in turn and connects the rep only on live answers. Teams already on Aircall can use the integration instead.
WhatsApp steps stay manual
Reply.io supports WhatsApp in sequences as a task. Reply.io prepares the message and creates the task, then a person opens it and sends the message from WhatsApp Web or WhatsApp Desktop. Reply.io does not connect to the WhatsApp account itself, and it does not track replies to those messages, so reps check answers in WhatsApp and update the lead by hand.
For a few high-value accounts, that works. Across a full list, the manual send and the missing reply tracking turn WhatsApp into a side process that lives outside your sequence data.
How lemlist handles WhatsApp
In lemlist, you connect your WhatsApp account and add WhatsApp chat or voice message steps to the campaign, on the Multichannel Expert and Enterprise plans. A Has WhatsApp account condition checks whether the lead's number is on WhatsApp before the step, and sends the lead to email, a call or LinkedIn when it is not. Replies come back to the lemlist inbox with the rest of the conversation.
Data credits run out before your sequences do
Every Reply.io plan includes a monthly allowance of live data credits, and extra credit packages are sold separately. That is fine for teams that bring their own lists. Teams that source most of their leads inside Reply.io usually end up buying packages, so data becomes a variable cost on top of the seats and add-ons.
How lemlist handles data
lemlist uses credits too, so model them either way. The difference is how they are spent. Email Finder and Verifier runs a waterfall across several data providers and charges only when it returns a deliverable or risky email, with nothing charged for missing results. The Multichannel Expert and Enterprise plans include monthly credits per user, and you can set a custom waterfall to choose which providers run first by country.
Signals and visitor identification sit on the AI SDR tiers
Reply.io lists lead-level website visitor reveals and signal-based account ranking with Jason AI SDR, its AI agent, which is sold as its own tier separate from the core seat plans. A team on the core plans that wants to time outreach on buying signals either moves to the AI SDR tier or adds another data tool to its stack.
How lemlist handles signals
In lemlist, signal agents watch for events such as website visits, hiring and LinkedIn activity, and you decide what happens with each match. You can review signals by hand, create tasks automatically or push matching leads straight into a campaign. Website visitor signals identify the person for US traffic and fall back to the company when no individual can be matched. Our guide to intent signals in lemlist covers each signal type.
Mailboxes and warm-up are covered, under a fair-use policy
This one is a strength more than a limit. Reply.io includes email warm-up with every mailbox and offers unlimited mailboxes under a fair usage policy. If you run many domains and mailboxes, read that policy before you plan your sending infrastructure, so you know where the line sits.
In lemlist, lemwarm handles warm-up inside the same account, and the deliverability tools sit next to your campaigns. Our guide to warming up an email account explains the schedule we recommend for a new domain.
What a fully multichannel seat adds up to
Each limit above is small on its own. Together, they decide what one rep actually costs and how many tools sit around the platform. On Reply.io, a rep who runs email, LinkedIn, calls and signal-based prospecting usually needs several separate lines.
The user seat, on the plan that matches the channels you need.
One LinkedIn add-on per profile, for every rep who runs LinkedIn steps.
The Calls and SMS add-on, for every rep who dials or texts.
Extra data packages, once the monthly credit allowance runs out.
The Jason AI SDR tier or another data tool, if you want visitor identification and signals.
On lemlist, the same rep sits on one Multichannel Expert seat that covers email, LinkedIn, WhatsApp and call steps, plus credits for enrichment and signals beyond what the plan includes. Credits are still a variable cost, so model them. The difference is that adding a channel to a sequence does not add a line to the invoice.
Example with a five-rep team
Picture five SDRs who all run LinkedIn, three of whom also make calls, and who source half their leads inside the tool. On Reply.io, that team needs five seats, five LinkedIn add-ons, three Calls and SMS add-ons and regular data packages, then the AI SDR tier or a separate tool for signals. On lemlist, the same team needs five Multichannel Expert seats and a credit budget that matches its enrichment and signal volume. Run that exercise with your own numbers before you compare quotes, because the gap comes from the structure more than from the list price.
When Reply.io's packaging still fits
None of these limits makes Reply.io a bad choice. If your team sends mostly email, runs LinkedIn from a handful of profiles and brings its own data, the add-ons stay contained. Teams that want an AI agent to run large parts of the outbound cycle on its own may also find the AI SDR tier worth it. The limits matter most for teams that want every channel automated, signals on every seat and one place to see every reply.
How to audit your stack before you decide
Before you compare quotes, answer these five questions for your own team.
LinkedIn profiles. How many reps need LinkedIn steps, today and in six months?
Channels. Which channels must run automatically, and which can stay as manual tasks?
Replies. Do you need every reply, WhatsApp included, in one inbox and in your reporting?
Data. How many leads do you source inside the tool each month, and what happens when credits run out?
Signals. Where do your buying signals come from today, and who acts on them?
If most answers point to more profiles, more automated channels and more signals, map each one to an add-on or a separate tool, then compare that full picture with a platform where those channels sit in the same sequence.
Next step
The fastest way to see the difference is to rebuild one of your current sequences with email, LinkedIn, a call task and a WhatsApp step, triggered by a signal you already care about.
Find your next outbound tool
Discover a better way to find leads and run multichannel campaigns with lemlist.