# Multichannel strategy

> Why layered channels outperform any single one — attention recapture, identity signals, and the orchestration rules that keep touches from colliding.

**Channels compound because each covers a different weakness — email scales, LinkedIn adds a face and shared context, calls add urgency. Switching channels recaptures attention a prospect stopped giving the previous one. Orchestration rules prevent overlap — the same ask never lands on two channels in one day.**

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

## What it is

Multichannel strategy runs one conversation across several channels — typically email,
LinkedIn, and phone — inside a single [sequence](/learn/sequence-design). Each channel
keeps its own strengths: email reaches anyone at scale, LinkedIn attaches a face, a
title, and mutual context to your name, and a call adds an immediacy nothing
asynchronous matches.

## Why it works this way

Channels compound because their weaknesses do not overlap. Email is easy to ignore in
bulk; a profile view or connection request is personal and hard to batch-delete; a call
interrupts. Switching channels also recaptures attention: a prospect who has tuned out
your emails still notices a new channel, and the earlier email touches make your name
familiar when they do. Recognition earned on one channel transfers to the next.

## How it behaves in practice

- **A typical pattern.** Email → LinkedIn profile view → connection request → email follow-up → call. Soft touches build familiarity before the direct ask.
- **Orchestration rules prevent collisions.** The same ask on two channels in one day reads as pressure, not persistence — spacing applies across channels, not per channel.
- **LinkedIn carries platform limits.** Connection requests and messages are rate-capped, so LinkedIn touches are spent on the highest-value moments.
- **Channels report differently.** Email gives delivery and reply signals, LinkedIn shows acceptance, calls give live resolution — reading them together is the point.

## Common misconceptions

| Belief | Reality |
| --- | --- |
| "More channels means more volume" | It means the same conversation on more surfaces — volume rules still apply per channel |
| "Repeat the message everywhere" | Repetition across channels on the same day reads as pressure; each touch should add something |
| "LinkedIn replaces email" | LinkedIn is rate-capped and identity-bound; email still carries the scale |
| "Calls are obsolete" | A call converts warmed attention into a decision faster than any written channel |

## How Reply implements this

Reply's [multichannel capability](/capabilities/multichannel-outreach) puts every
channel into one sequence: email, [LinkedIn](/capabilities/linkedin-outreach) — both
automated steps (connection requests, messages, InMails, profile views, post likes)
and manual tasks — Cloud Calls made directly from the platform, SMS, WhatsApp as
semi-automated tasks, and a Zapier step that triggers an action in an outside app.
LinkedIn automated steps run inside per-account safety limits: default dynamic ranges
of 25-35 actions per day for most action types, 35-50 for messages, and a maximum of
100 per action. Reply handling applies at the sequence level, so a detected reply
(email or LinkedIn) stops the remaining steps on every channel unless the sequence is
set to continue. A Channel Efficiency dashboard compares touches, replies, and booked
meetings across automatic and manual email, calls, LinkedIn, SMS, and WhatsApp — the
cross-channel reading described above. The end-to-end setup is documented in
[run multichannel outreach](/workflows/run-multichannel-outreach).

## Where this breaks down

Compounding requires presence: prospects who are not active on LinkedIn or never answer
unknown numbers collapse the strategy back to email. Orchestration overhead is real —
misconfigured timing produces the same-day collisions it exists to prevent. And each
channel has its own compliance rules; adding channels multiplies obligations as well as
reach.

## Related

- [Sequence design](/learn/sequence-design)
- [Email deliverability](/learn/email-deliverability)
- [Multichannel outreach in Reply](/capabilities/multichannel-outreach)
- [LinkedIn outreach in Reply](/capabilities/linkedin-outreach)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) — sequence and channel step operations
- MCP: [agents.reply.io/mcp](https://agents.reply.io/mcp) — LinkedIn account and sequence operations