Chapter 09 · Campaign architecture
Channel orchestration

Multi-channel orchestration — email + LinkedIn + phone in coordinated sequence.

A campaign on one channel reaches that channel's cumulative response ceiling and stops. A campaign across email, LinkedIn, and phone in a coordinated sequence reaches a curve meaningfully higher than the sum of per-channel ceilings — provided the orchestration is coordinated rather than parallel, and provided the operator stops at three channels rather than a fourth.

The premise

A single-channel campaign — email-only, LinkedIn-only, or phone-only — converges on a cumulative reply rate between 2% and 4%, depending on segment, copy, and infrastructure. Above that ceiling, additional same-channel touches produce diminishing returns and rising complaint rates. The recipient who has not responded to five well-written emails over five weeks is not, in our observation, going to respond to the sixth.

What the recipient may respond to is a touch on a different channel. A cold email that produced no reply sits in an archived inbox; a connection request two days later, referencing the prior message, lands against a recipient who has already partially registered the sender's name. Single-channel campaigns leave 30 to 60% of the addressable response rate on the table.

The empirical lift across channels

The cumulative reply-rate curve as a function of channel count holds an approximate shape stable across ICP segments:

  • One channel — 2-4% cumulative. Email-only at five to seven touches, LinkedIn-only at three to five, phone-only at four to six attempts. Exact rate depends on copy and segment; the ceiling is structural.
  • Two channels — 4-7% cumulative. Email plus LinkedIn is the most common pairing; lift over email-only is roughly 60 to 90%. Email plus phone produces a similar lift in enterprise IT; LinkedIn plus phone underperforms email-anchored pairings.
  • Three channels — 6-9% cumulative. Email plus LinkedIn plus phone, coordinated. Lift over the best two-channel pairing is roughly 30 to 50%, smaller in absolute terms than the one-to-two jump, but consistent across segments.
  • Four-plus channels — declining. Adding a fourth channel (SMS, video, postal mail, ad retargeting) produces no measurable lift and, above six total touches per recipient across channels, a measurable spike in complaint and unsubscribe rates. This is the channel-noise cliff.

The curve flattens because the recipient's tolerance for cross-channel persistence is bounded. The first two cross-channel touches read as professionalism; the fifth reads as harassment, and the recipient's next action is to flag, block, or warn their team.

The orchestration question — coordinated vs parallel

The choice that determines whether multi-channel produces the cumulative lift above, or merely the sum of independent single-channel campaigns, is whether channels are coordinated or parallel.

A parallel campaign runs the same recipient through an email sequence and, independently, through LinkedIn and phone sequences — email on day 1, connect on day 1, phone on day 1, repeating. Cumulative reply rate is only marginally higher than the best single-channel campaign in the mix — typically a 10 to 20% lift, not the 60 to 90% of coordinated orchestration.

A coordinated campaign runs the recipient through a single sequence in which each touch is on a different channel and explicitly references prior touches — email on day 1, connect on day 3, email on day 6 following up the first, LinkedIn message on day 9 referencing the email, phone on day 12. The empirical cumulative-response advantage of the coordinated pattern is the central return on multi-channel orchestration.

The per-channel sequencing template

A seven-touch coordinated sequence over roughly four weeks consistently produces the 6-9% cumulative reply rate across mid-market and enterprise segments:

TouchChannelDayPurpose
1EmailDay 0Primary value-prop, light CTA
2LinkedIn connectDay 3Connection request, brief note, no pitch
3EmailDay 6Follow-up referencing email 1, new frame
4LinkedIn messageDay 10Post-accept message referencing email 1 explicitly
5PhoneDay 14Single attempt, business-hours local timezone, voicemail optional
6EmailDay 18Short check-in, named-question CTA
7LinkedIn noteDay 24Final touch, explicit close-the-loop frame

The sequence respects per-channel constraints from earlier chapters — the email cadence (Chapter 7), post-accept timing on LinkedIn, single-attempt-per-recipient phone discipline (Chapter 8) — while interleaving channels to compound rather than compete.

Per-channel timing

Email touches sit 3 to 6 days apart, weighted slightly longer in the back half to avoid escalating-persistence perception. LinkedIn touches sit relative to platform events — connect 2 to 3 days after the first email, message 1 to 4 days after acceptance, final note roughly two weeks after the message. Phone attempts are scheduled during business hours of the recipient's timezone, not the sender's; 11am eastern to a recipient in San Francisco is an 8am attempt to that recipient.

The total sequence horizon sits at roughly 24 days. Compressing below 14 days produces the same complaint-rate spike as single-channel over-cadence; extending beyond 35 days produces sequence abandonment, where touches 6 and 7 land against a recipient with no memory of touches 1 through 4.

The cross-channel reference

The empirical conversion lift of multi-channel orchestration is concentrated in the touches that explicitly referenceprior touches on other channels. A LinkedIn message at touch 4 with a generic introduction performs at roughly the same rate as a LinkedIn message in a LinkedIn-only campaign. A LinkedIn message that opens with one line referencing the email of day 1 by topic — "sent a note last week about [the specific subject], wanted to follow up here" — produces a reply rate roughly two to three times higher.

The mechanism is recipient cognitive load. The cross-channel reference primes the recipient's memory and signals a coherent process rather than parallel attempts. It is the single highest-leverage line in a coordinated sequence.

Reply handling across channels

The instant a recipient replies on any channel, every other channel pauses. A LinkedIn reply at touch 4 stops the email at touch 6 and the phone attempt at touch 5. The operational pattern is a single sequence-state machine that consumes events from all channels and writes a unified per-recipient sequence position.

The failure mode is channel-siloed reply detection — the email platform sees no reply on its channel and continues the sequence, while the LinkedIn conversation has been in progress for a week. The recipient receives email touch 6 in the middle of a productive LinkedIn thread, registers the disconnect, and disengages from both channels. Cumulative reply rate of a campaign with channel-siloed reply detection converges on the parallel-campaign ceiling — meaningfully below coordinated.

The attribution problem

When a recipient books a meeting after touches on three channels, which channel gets credit. The empirical answer is that clean attribution is not possible. The recipient who clicks the meeting link in email touch 6 may have been primed by the LinkedIn message at touch 4 and warmed by the phone voicemail at touch 5; the recipient who books from the LinkedIn thread may have read three emails first.

Single-channel ROI calculations on a multi-channel campaign are systematically misleading. Crediting the booking entirely to the channel that produced the click overstates that channel's contribution; fractional credit requires a model the operator does not have data to fit. The correct posture is to measure campaigns at the campaign level — cumulative bookings per 100 recipients — and make channel-mix decisions on segment-level experiments rather than per-channel attribution.

The channel-noise cliff

Adding a fourth channel — SMS, postal mail, video message, retargeting ads — produces no measurable lift in cumulative reply rate and a measurable spike in unsubscribe and complaint rates. The threshold where channel-multiplication becomes channel-noise sits between channel three and channel four for B2B outbound.

The mechanism is recipient pattern-recognition of spam-like persistence. Three channels read as a professional sales process; four or more reads as a sender who has lost discipline. The downside risk of the fourth channel is asymmetrically larger than the marginal upside.

The per-segment channel mix

Optimal channel mix is segment-dependent. A few stable patterns:

  • Technical buyers (engineers, ML researchers, ICs). Email-heavy, LinkedIn-light, no phone. Cumulative reply rate is highest on email, LinkedIn touches produce a modest lift, phone attempts produce zero connects and a measurable spike in complaint rate. The sequence collapses to five email touches with two LinkedIn touches interleaved.
  • Enterprise IT (directors, VPs of infrastructure, security). Email plus LinkedIn plus phone, full sequence. The 6-9% cumulative figure is most reliably achievable here. Phone produces a 5 to 15% connect rate on the first attempt; voicemail performs neutrally.
  • C-suite (CEO, COO, CRO). LinkedIn-heavy and phone, light email. Cumulative email reply rate at this seniority sits below 2%; the same recipient is meaningfully more likely to engage on LinkedIn, and phone connects (typically to an EA, occasionally direct) produce the highest-conversion path. The sequence inverts — LinkedIn at touch 1, email at touch 2, phone at touch 3.

The channel-substitution pattern

A frequently-observed substitution failure: the operator runs a LinkedIn-first sequence, sending the connect and message before any email touch. Cumulative reply rate underperforms an email-first-then-LinkedIn sequence with the same total touch count, often by 30 to 50%, despite intuition suggesting LinkedIn is a softer first touch.

The mechanism is that the email touch primes recipient recognition such that the LinkedIn connect arrives against a name already seen. A LinkedIn connect from a sender with zero prior context, no mutual connections, and no email exposure has a meaningfully lower acceptance rate than the same connect arriving three days after a well-written cold email. The connect-rate differential propagates through the rest of the sequence.

The orchestration tooling question

The operational cost of coordinated multi-channel is meaningfully higher than three independent per-channel campaigns. Coordination requires a state machine that knows, per recipient, which channels have been touched, when, with what content, and whether any channel has produced a reply. Per-channel campaigns require only three independent schedulers.

Per-platform integration maturity is uneven. Email APIs are mature; LinkedIn APIs are restricted and require browser-automation infrastructure for full sequence orchestration; phone requires a dialer or a manual queue handed to a human caller. The operator who assembles coordinated orchestration from per-channel point tools typically ends up with a parallel campaign masquerading as coordinated — separate state per channel, no cross-channel reply detection, no shared opt-out.

Reply routing across channels

Replies on all three channels — email reply, LinkedIn DM, returned phone call — route to a single inbox or shared Slack channel regardless of source. The operator sees a unified per-recipient conversation history rather than three independent threads in three independent tools.

The failure mode of channel-siloed routing is degraded response time — a LinkedIn message at 9am that requires the SDR to log into a separate tool, ten minutes after handling email replies, drops the recipient out of the engagement window. The cumulative effect is a campaign that produces inbound interest and converts it at a meaningfully lower rate than unified routing would.

Opt-out handling across channels

A recipient who unsubscribes via email must not receive a LinkedIn follow-up, a phone call, or a future email on any campaign. The operational requirement is a per-recipient opt-out flag honored across every channel and every campaign, indefinitely.

The failure mode of channel-siloed opt-outs: the recipient unsubscribes via email, receives a LinkedIn message three days later, and either flags it as spam (damaging the LinkedIn account's sender reputation), responds with a public complaint, or — in regulated jurisdictions — files a privacy complaint. CASL, GDPR, and CAN-SPAM all impose a unified opt-out obligation that channel-siloed tooling structurally cannot meet. The compliance posture is to honor opt-out across every channel by default, with the opt-out list as an organization-wide asset, not a per-tool configuration.

The meeting-booking link

The same calendar booking link can be shared across all channels, or a channel-specific link can be used per touch. The empirical signal: the channel-specific approach surfaces attribution data — which channel produced the click that booked — but cumulative booking rate is not measurably different.

The lighter-weight pattern is a single calendar link with UTM parameters that vary by channel. Data flows into the same campaign-level attribution model, the operator does not maintain per-channel landing pages, and recipient experience is identical across touches. Channel-specific links are justifiable when the booking flow itself differs by channel; as an attribution mechanism alone, they produce low marginal return.

Campaign vs individual outreach

The multi-channel architecture above applies to campaigns — high-volume, sequenced, templated-with-personalization. Named-account, manually-composed outreach to a specific high-value recipient operates on a different model: no sequence template, each touch composed individually, channel choice conditional on prior responses.

The decision boundary sits at the top of the funnel — campaigns for the broader ICP, individual outreach for the named-account list. A pipeline that runs campaigns only loses the highest-value 1 to 5% of accounts to undifferentiated sequencing; a pipeline that runs individual outreach only converges on operator capacity. The operator who runs both, with explicit promotion criteria from campaign sequence to named-account treatment, produces the highest pipeline volume per SDR-week.

Common operator failures observed in production

  • The same message on multiple channels. The recipient receives an email, a LinkedIn message that is the same copy paraphrased, and a voicemail with the same script. Cross-channel reference degenerates into cross-channel redundancy; cumulative response underperforms the single-channel ceiling.
  • No cross-channel reply detection. The recipient replies on LinkedIn, the email sequence continues, the recipient disengages. The campaign produces inbound interest and immediately destroys it.
  • No opt-out propagation. The recipient unsubscribes via email and is added to a phone queue the following week. Compliance exposure is asymmetric — the marginal call has near-zero expected value, the public complaint has open-ended downside.
  • Four-plus channels per recipient. The operator adds SMS or retargeting ads to a three-channel sequence in pursuit of marginal lift, observes a complaint-rate spike, and conflates it with poor copy rather than channel-count saturation.
  • Channel-siloed measurement. The operator measures per-channel reply rates as independent metrics, attributes meetings to whichever channel produced the final click, and makes channel-mix decisions on data that systematically overstates the click-attributable channel.
  • Parallel masquerading as coordinated. The operator assembles three independent per-channel tools, runs the same list through all three, and reports a multi-channel campaign. Cumulative reply rate is roughly the single-channel ceiling plus a small overlap; the lift relative to coordinated is meaningfully foregone.

Pre-deployment multi-channel checklist

  • A unified per-recipient sequence state machine consuming events from email, LinkedIn, and phone, with a single sequence position
  • Cross-channel reply detection that pauses every channel within 60 minutes of any reply
  • A single opt-out list honored across every channel and campaign, indefinitely, with compliance posture documented
  • A unified inbox or shared Slack channel for reply routing across all three channels
  • A three-channel ceiling per recipient, enforced at the campaign-configuration layer
  • Per-segment channel-mix decisions documented and revisited quarterly against cumulative-response data
  • A campaign-level attribution model, with explicit acknowledgement that single-channel credit is misleading
  • A documented promotion criterion from campaign sequence to named-account individual outreach for the top 1 to 5% of recipients
  • Per-channel timing aligned to recipient timezone (phone), platform-event triggers (LinkedIn), and 3 to 6 day email cadence
  • A cross-channel reference line in touches 3, 4, and beyond explicitly citing prior channel and content

Where multi-channel orchestration fits

The coordinated multi-channel campaign is where the entire upstream infrastructure realizes its return. The email cluster — provisioned domains, configured authentication, warmed inboxes, monitored deliverability — produces a substrate on which email touches actually arrive at the inbox. The LinkedIn cluster produces a substrate on which connects are accepted and messages are read. The copy cluster — subject lines, opening lines, value propositions, CTAs, personalization, sequencing — produces message content that converts. Multi-channel orchestration ties these together into the campaign the operator actually runs.

Coherent orchestration over correctly configured infrastructure with disciplined copy produces a cumulative reply rate of 6 to 9% and a meeting-booking rate of 1 to 3%, sustained week over week. The same campaign on parallel per-channel point tools, with siloed reply detection and channel-specific opt-out lists, produces a reply rate of 1 to 3% and a complaint trajectory converging on deliverability collapse within a quarter.

The infrastructure is the precondition. The copy is the leverage point. Orchestration is the multiplier that turns nine chapters of discipline into a coherent campaign.

Skip the setup

Allston Labs operates the full sending estate as a service.

We provision domains, configure the entire authentication record set, run warmup, and monitor reputation across providers. The stack lives under your entity. The engineer on call lives in your Slack.