Run cold email, LinkedIn, WhatsApp and Instagram from one campaign

A multichannel campaign in WarmySender is one sequence with steps on different channels — an email, then a connection request, then a WhatsApp message or an Instagram DM — and one scheduler paces all of them. That is the whole idea, and it has one consequence worth stating before anything else: adding a channel adds reach, never speed. Two channels each running at their own safe volume reach more people than one channel pushed past its ceiling. That is the reason to add a channel — reach, not more volume on one.

Which channels can be in one sequence?

Four channels can appear as steps in the same sequence, and two more things run alongside them:

Email warmup runs underneath the whole thing. It is not a step you add — it works quietly in the background on every connected mailbox, building and protecting sender reputation so the email steps land in the inbox instead of the spam folder. See how email warmup works.

Real-time email verification sits in the same place. Addresses are checked before a campaign sends to them, so a bad address is caught rather than bounced — bounces are what wreck a domain's reputation and pull the good mail down with them. See the email verifier, and the built-in lead database if you still need the contacts.

One prospect list can hold an email address, a LinkedIn profile, a phone number and an Instagram handle at once, so the same audience powers every step. Anyone missing the detail a step needs is simply skipped for that step — nothing errors, and the rest of the sequence carries on for them.

What does a multichannel sequence actually look like?

A sequence is an ordered list of steps with waits between them. Each step names its channel, and each wait is however long you want it to be. A typical one reads like this:

  1. Day 1 — Email. A short, specific first email.
  2. Day 3 — LinkedIn connection request. Sent only to people whose profile you have.
  3. Day 5 — Wait for a reply. A wait step that simply gives the person room.
  4. Day 6 — Branch. If they accepted the connection, send a LinkedIn message. If they did not, send a second email instead.
  5. Day 10 — WhatsApp or Instagram. A last, gentle touch on whichever channel you have an identifier for.

The pieces you build with:

Steps
One action on one channel. A step can carry merge fields, A/B variants, and attachments where the channel supports them. WhatsApp messages can run up to 4,096 characters, Instagram DMs up to 1,000, and Instagram comments up to 1,250 — though on every channel the short ones get the replies.
Delays
The wait between one step and the next, in days or hours. Delays are a minimum, not a promise: if the channel's pacing says the next action is not due yet, the step waits longer rather than pushing.
Conditional branches
An if in the sequence. The common ones are if they accepted the connection, if they opened, and if they replied — each sending the person down a different path from that point on.
Wait-for-reply
A step that pauses the sequence for a set window and only continues if nobody has answered. It is how you avoid following up on a conversation that already started.

A campaign runs exactly the way you built it. WarmySender does not add steps, skip branches, or "helpfully" advance someone on a signal you did not configure. The one thing it will do on its own is wait — when a step is due but the account's safe pace says not yet, the step defers rather than sending.

What happens when a prospect replies on any channel?

Everything else stops. Stop-on-reply works across every channel at once, not per channel: an email reply stops the queued LinkedIn message, a LinkedIn reply stops the queued email, and a WhatsApp or Instagram reply stops both. The person drops out of the automated sequence and the conversation becomes yours.

That is the single most important reason to run the channels from one campaign rather than from separate tools. Four tools that cannot see each other will each keep following up after somebody has already answered one of them — which is the fastest way to sound automated to the one person who was interested.

Every reply, from every channel, lands in one unified inbox, so there is a single place to read and answer. The mechanics of what counts as a reply, and what happens to the rest of the sequence, are written up in how stop-on-reply works across channels.

Do the channels share a sending allowance?

No. The channels share no allowance at all. Every connected mailbox, LinkedIn account, WhatsApp number and Instagram account keeps its own independent daily and hourly ceiling and its own ramp, and nothing pools between them. Adding a channel never adds headroom to another one, and no setting, plan or support request raises a single account past its ceiling.

This is worth being blunt about, because the opposite assumption is what gets accounts restricted. Running LinkedIn does not buy you extra email volume. Adding WhatsApp does not raise your Instagram ceiling. Each account is paced on its own, against its own budget, on its own ramp.

What you actually gain is reach. Two channels each running at their own safe volume reach more people than one channel pushed past its ceiling. That is the reason to add a channel — reach, not more volume on one.

The per-account ceilings

Per-account ceilings and pacing by channel. Each is a ceiling that a ramp or your own setting may only lower — nothing raises one.
Channel Per-account ceiling Pacing Ramp
Cold email 200 a day for a new sending domain, 2,000 once it is established, up to 10,000 for a high-volume domain — shared by every mailbox on that domain Spread across your sending window rather than dumped in one burst, with an hourly ceiling underneath the daily one Warmup runs underneath and the domain moves up a tier only on a clean record
LinkedIn Up to 200 connection requests a week and 100 messages a day per account, at the very top of the ramp Actions spaced out through the day, never fired back to back 8 weeks for an account coming back from a restriction, 6 for a new one, 2 for a veteran account
WhatsApp 60 messages a day per number, of which at most 20 may be first messages to someone new — a strict slice of the 60, never an extra allowance, leaving 40 for follow-ups. No more than 8 in any rolling hour One at a time, 45 to 120 seconds apart, randomized so it is never a machine-regular beat A brand-new number starts at 5 first messages and 20 messages a day and builds up over several weeks
Instagram 100 actions a day and 10 an hour per account — ONE combined budget shared across follows, profile views, likes, comments and DMs, not 100 of each. Replies you send to inbound DMs never count One action at a time, 60 to 105 seconds apart, randomized A freshly connected account eases in and builds up over several weeks

The LinkedIn ramps

A connected LinkedIn account starts on a ramp chosen for how old and how healthy it is, and climbs to full pace over several weeks:

LinkedIn ramp schedules. The first figure is week one; the second is full pace at the end of the ramp.
Ramp Applies to Length Connection requests Messages
New account an account less than six months old 6 weeks 25 → 150 connection requests a week 12 → 75 messages a day
Established an account six to twelve months old 4 weeks 45 → 175 connection requests a week 21 → 85 messages a day
Veteran an account over a year old 2 weeks 100 → 200 connection requests a week 50 → 100 messages a day
Recovery an account coming back from a restriction 8 weeks 12 → 100 connection requests a week 6 → 50 messages a day

The cold-email domain tiers

Cold email is measured per sending domain, and the ceiling is shared by every mailbox on that domain — adding mailboxes to a domain splits the same budget rather than multiplying it:

Your plan also sets a monthly email allowance, paced across the month. Both apply: the lower of the two is what actually binds on any given day. See pricing for the plan allowances.

So the honest way to send more email is more warmed sending domains and mailboxes — and the honest way to reach more people overall is another channel, at its own safe pace.

What do I need connected before I start?

Only the channels you actually want to use. A multichannel campaign is happy with two of them, and one is a perfectly good place to start.

Verify the email addresses before you launch. It costs a fraction of what a bounce costs your domain.

Can an AI agent build and run a multichannel campaign?

Yes. Claude, ChatGPT, Cursor, Codex, OpenClaw or Hermes Agent — or any agent that speaks MCP — can create a campaign on any channel, launch it, pause and resume it, enroll prospects in it, verify email addresses, and configure warmup and read its stats, all in plain language. You describe the sequence you want; the agent builds it.

What an agent cannot do matters just as much. It never sends a message, DM or invite directly, and it can never raise a limit. Creating or launching a campaign only writes it and hands it to WarmySender's scheduler, which paces every email, LinkedIn, WhatsApp and Instagram action inside the same safe caps and the same gradual ramp no matter who or what set it running. Connecting and disconnecting accounts stays in the app deliberately — it is the one thing that is not an agent tool.

Claude, ChatGPT, Cursor, Codex, OpenClaw, and Hermes Agent all connect in one paste. See AI agents and the MCP server.

What does it cost?

Cold email and email warmup come with the plan, from $14.99/month. The other three channels are per-seat add-ons on any plan, and you only pay for the ones you run:

Email verification runs on the same account: a plan from Pro upward carries a monthly allowance, and one-time credits can be bought on their own. Full detail on the pricing page.

Adding a seat is also the only way to increase a channel's total volume — each account carries its own independent budget, and no setting anywhere raises a single account's ceiling.

Frequently asked questions

Which channels can be in one multichannel sequence?

Cold email, LinkedIn, WhatsApp and Instagram steps can all appear in the same sequence, in any order, with whatever waits you want between them. Email warmup runs underneath on every connected mailbox rather than as a step, and real-time email verification checks addresses before a campaign sends to them.

Do the channels share a sending allowance?

No. The channels share no allowance at all. Every connected mailbox, LinkedIn account, WhatsApp number and Instagram account keeps its own independent daily and hourly ceiling and its own ramp, and nothing pools between them. Adding a channel never adds headroom to another one, and no setting, plan or support request raises a single account past its ceiling.

Why add a channel at all, then?

Two channels each running at their own safe volume reach more people than one channel pushed past its ceiling. That is the reason to add a channel — reach, not more volume on one. A prospect who ignores email may answer a LinkedIn message; a prospect with no email address may still have a handle. You are widening the door, not opening it faster.

What happens when someone replies on one channel?

Every other channel stops for that person. Stop-on-reply is campaign-wide, not per channel: a reply by email, LinkedIn, WhatsApp or Instagram takes them out of the automated sequence entirely, and the conversation lands in one unified inbox where you answer it yourself.

Can a sequence branch on what a prospect does?

Yes. Steps can branch on whether a connection request was accepted, whether an email was opened, and whether the person replied, and a wait-for-reply step pauses the sequence for a window and only continues if nobody answered. A campaign runs exactly as you configured it — nothing auto-advances on a signal you did not set up.

What do I need connected to run one?

Only the channels you want to use: a warmed mailbox for email steps, and a seat plus a connected account for LinkedIn, WhatsApp or Instagram steps. You also need an audience carrying the identifiers your steps need — anyone missing one is simply skipped for that step while the rest of the sequence continues.

Can an AI agent build and run a multichannel campaign for me?

Yes. Claude, ChatGPT, Cursor, Codex, OpenClaw or Hermes Agent — or any agent that speaks MCP — can create, launch, pause, resume and enroll people in campaigns on every channel, verify emails and tune warmup, in plain language. The agent never sends a message itself and can never raise a limit: it hands the campaign to WarmySender's scheduler, which paces every action inside safe caps and the ramp regardless of who triggered it. Connecting and disconnecting accounts stays in the app.

What does multichannel outreach cost?

Cold email and email warmup are included with a plan from $14.99/month. LinkedIn is $15/seat/month, WhatsApp $15/seat/month and Instagram $20/seat/month, one seat per connected account, on any plan. You only pay for the channels you actually run.

Ready to build one?

Start with the channel you already have, add the second when the first is running clean, and let the scheduler keep both inside their own safe pace.