AI outbound sales: one motion across every channel

Email alone used to be enough. Inboxes were less crowded, spam filters were cruder, and a well written subject line carried a campaign a long way on its own.

That stopped working for three separate reasons at once, not one big reason. Filters got better at spotting sequenced sends, so a five-touch email cadence increasingly lands in a folder nobody checks. Buyers moved a chunk of their attention to LinkedIn, where a message from a stranger reads as more personal than the fortieth cold email of the week. And phone numbers got harder to buy in bulk and easier to screen, which killed the spray-and-pray dialling lists that used to fill a pipeline on volume alone.

The result is a familiar pattern: reply rates on email-only sequences drift down every year, while teams that added a second or third channel report the opposite. That is not because any one channel got worse in isolation. It is because a prospect who ignores an email might answer a LinkedIn message the same week, and a prospect who ignores both might pick up a call that references something specific about their company. Channels do not compete for the same attention. They catch it at different moments.

The catch is that adding channels by hand multiplies the admin rather than the results. A rep juggling an email tool, a LinkedIn tab and a spreadsheet of call notes loses the thread fast, and the two most common failures are a duplicate touch that annoys a prospect and a reply that gets missed because it landed somewhere nobody was watching.

Here is what one step-through of an email and LinkedIn sequence looks like when the wait logic, the timezone handling and the stop conditions are all enforced by the system rather than remembered by a person, with a phone task queued alongside it. The numbers below are illustrative, taken from an example campaign, not an average across customers.

Two things about that table matter more than the specific days. First, the wait between step 2 and step 3 is a real three days, not a re-check every few minutes that happens to land on day three; the difference matters because a system that can send early will eventually send early, usually on a day when timing was the whole point. Second, the sequence stops the second a reply lands anywhere in it. If Priya replies to the day 1 email on day 3, the LinkedIn note scheduled for day 2 either never goes if it has not fired yet, or the day 5 follow-up and the day 8 call task are cancelled outright. A skipped or blocked step should always show why: address failed verification, daily cap reached, do-not-call match, or a reply already received. A sequence that fails silently is a sequence you cannot trust with real volume.

LinkedIn earns its place in the sequence because a message there reads as more personal, and because it reaches people who have quietly turned email into background noise.

What works: a connection note that references the same specific detail as the earlier email rather than restating a generic pitch, an InMail reserved for accounts where a connection request alone has gone nowhere, and messages spaced out through the working day rather than fired in a burst at 9am.

What gets you restricted: sending the same invite text to everyone, running a daily cap at its ceiling every single day with no variation, and stacking multiple LinkedIn actions on the same contact inside a short window. Widely reported limits put a personal account at roughly 100 connection invites a week in 2026, with newer accounts held to something tighter, and LinkedIn does not publish an exact figure or explain exactly how it enforces it. Ariel's own control is a daily cap, set at campaign and account level with the lower always binding; there is no separate weekly ceiling, so staying under that figure means choosing a sensible daily number and holding it. Software that spreads activity across working hours and respects that daily ceiling stays inside the limit more reliably than a human clicking as fast as they can, but no vendor, including us, can promise an account will never be restricted. That risk sits with the person whose name is on the account, always.

None of the channel level advice above matters if the sending infrastructure behind it is thin. A sequence with perfect copy and a burned domain produces nothing.

Four pieces of infrastructure carry the weight. Multiple inboxes sharing the load, so no single mailbox sends a volume that looks abnormal on its own; our multi-inbox sending page covers the mechanics. Pacing that treats a newly connected inbox differently to one that has been sending cleanly for months, ramping volume gently instead of firing at full capacity on day one. Bounces converted into suppressions automatically, within minutes rather than sitting in a queue, because a bounce that sits unresolved for a week is a bounce that keeps happening. And an opt-out list that nothing can override, not a CSV import, not a new campaign, not a change of segment.

A quick way to test any platform's infrastructure claims: ask what happens when someone who unsubscribed six months ago gets uploaded again in a fresh list. If the honest answer is "it depends on the import settings," that is a gap that will eventually cost a complaint nobody can argue their way out of.

The mistake most teams make is measuring each channel on its own metrics: email open rate, LinkedIn acceptance rate, call connect rate. Those numbers matter individually, but they hide the thing that predicts pipeline best.

Track the sequence as one unit instead. Meetings booked per hundred contacts entering the sequence is the number that survives contact with a finance team, because it already accounts for every channel's contribution rather than crediting whichever channel happened to get the last touch. Positive reply rate across all channels combined, classified at the point of arrival, tells you whether the angle is working before volume tells you anything. Complaint and unsubscribe rate, watched weekly rather than monthly, is the earliest warning that a sequence is running too hot on one channel even if the others look fine. And cost per booked meeting, calculated across the whole sequence including any per-contact data spend, is the only number worth comparing against the cost of a hired rep doing the same work by hand.

One number worth watching specifically because it is easy to miss: the share of contacts that exit the sequence with a skipped or blocked status rather than a completed one. A rising skip rate on the LinkedIn step, for example, usually means a daily cap is being hit consistently, which is a sign to either widen the pool of inboxes or slow the pace, not to ignore the warning. Silence deserves its own bucket too: a contact that never replies for ninety days is tagged Gone quiet automatically, so it reads as its own group rather than blending into everyone still mid-sequence.

Automation should carry the volume, not the judgment. Three moments in a multichannel sequence consistently need a human, and pretending otherwise is where accounts get into trouble.

The first reply that reads as a real question rather than a scheduling logistic. "How does this work for a team our size" needs a person who can answer it with specifics, not a templated response that dodges the question.

Any account where the buying committee looks unusually large or unusually senior. A sequence that works well on a single decision maker can read as tone deaf sent unedited to a chief financial officer, and someone should look at that message before it goes.

And any moment the sequence itself flags something unusual: a spike in bounces on one inbox, an unusually high skip rate on a channel, a complaint. Those are the signals worth stopping the automation for entirely until a person has looked at what changed.