Orchestrating across channels: one plan, many executors
AI-assisted research. This note was prepared with the assistance of AI tools. It may contain errors and is not professional advice. See our Legal Disclosures.
Agentic marketing programs tend to grow along the lines of the org chart. An email agent arrives first, then one for social, then one for paid media, each owned by the team that already runs that channel.
Each of those agents can work well on its own. The trouble is that customers do not experience channels separately. They see an ad, open an email, visit the site, and talk to a sales rep, sometimes in the same afternoon. If each channel's agent works from a different understanding of the campaign, the customer gets a different story in each place.
Cross-channel orchestration is our name for the fix: one plan, many executors.
How channels drift apart
Drift rarely starts with a big mistake. It starts with small, reasonable edits made in one place.
A paid media owner shortens an offer line to fit a character limit and drops the exclusion. An email agent pulls a launch date from last week's brief. A sales follow-up quotes the original price after a promotion was extended.
Each edit is defensible inside its own channel. Together, they produce a campaign where the ad, the email, and the landing page disagree. Agents speed this up, because they produce channel variations far faster than a person can compare them. They also copy a stale fact into every variation with the same speed they copy a correct one.
The shared plan
At the center of the fix is a single campaign plan that every channel agent reads and none of them edits. We suggest it hold at least these elements.
- Goal and success measures: what the campaign is for and how you will judge it.
- Audience definitions: identical across channels, stored once.
- Core message: the main point and its supporting points.
- Approved facts and offers: exact prices, dates, terms, and exclusions.
- Channel roles: what each channel is responsible for.
- Timing: sequencing and key dates across all channels.
When something changes, such as an offer being extended or a segment being excluded, it changes in the plan. Every channel agent picks up the change from there, instead of waiting for someone to tell it.
Channel roles
Different channels play different parts in a customer's path to a decision. A plan should state those parts explicitly, so each agent knows what it is for and what it is not for. A typical split might look like this.
- Ads: create awareness and drive first visits.
- Email: nurture known contacts with depth.
- Social: build familiarity and reach.
- Sales: follow up on high-intent accounts.
- Website: answer questions and convert.
Channel agents work within their role rather than each trying to do everything. An email agent that starts writing awareness copy for cold audiences is a sign the roles were never written down.
Coordination mechanisms
A shared plan is necessary but not enough on its own. Four mechanisms keep the channels aligned once work is moving.
- Shared audience state: when a contact converts in one channel, the others know quickly, so the customer stops receiving acquisition messages.
- Cross-channel frequency limits: cap total touches per person across all channels, not just per channel.
- Consistency review: review assets from all channels together before launch, where mismatched dates and offers are easy to spot.
- Single source for changes: changes go into the plan, never directly into one channel agent's instructions.
Shared audience state is the hardest of the four, because it depends on knowing that the person who clicked an ad is the same person on your email list. Our post on identity resolution covers what that requires.
The consistency review is the easiest to start. Agents can produce channel assets in parallel, but the review should look at them side by side, which is the hybrid shape we describe in parallel vs sequential orchestration.
The hub's role
In our Agentic Hub architecture, the hub holds the shared plan and audience definitions, routes work to channel agents, and runs the consistency check before anything moves forward. Channel agents handle the specifics of their channel, such as formats, platform rules, and scheduling. They never redefine the campaign.
That division keeps channel expertise where it belongs. The paid media agent still knows how to write within an ad platform's limits. It simply draws the offer, the dates, and the audience from the same record as everyone else.
A worked example
Consider a hypothetical software company launching a new integration with a free trial extension for existing customers. The plan names four channels: paid social for awareness among prospects, email for existing customers, the website for details, and sales for accounts already in active deals.
Midway through the first week, the product team learns the integration will not be available in one region until later. A person updates the plan with the regional exclusion. The email agent drafts a short note for affected customers, the website agent adds a line to the details page, and the paid social agent removes that region from targeting. The sales agent adds the exclusion to its talking points for open deals.
The consistency review then compares all four channels against the updated plan and finds one older ad variation still running without the exclusion. A person pauses it. Without a shared plan, the same change becomes four separate requests to four owners, and the likeliest outcome is that one channel never hears about it. Our week-by-week holiday plan applies the same discipline to a season of fast-changing offers.
What to measure
Cross-channel work needs measures that look across channels, not within them. We recommend starting with these.
- Consistency defects: mismatched offers, dates, or claims found in review or reported by customers.
- Plan-to-channel lag: time from a plan change to every affected channel reflecting it.
- Total touches per person: contacts per customer across all channels in a week, against your cap.
- Post-conversion messages: acquisition messages sent to people who already converted.
The last measure is a good test of shared audience state. If it stays high, the channels are not hearing about conversions fast enough.
Open questions
We are studying how much freedom channel agents should have to adapt the core message. Some adaptation is the point of having channel specialists.
Too much, and the story fragments again. We expect the answer to involve a small set of fixed elements that never change across channels. Around them sits a wider set of expression choices that each agent controls, and we are testing where that line should sit.
How to apply this: for your next multi-channel campaign, create one plan that every channel agent and person works from, with offers, dates, and audiences stored once. Review all channel assets together before launch, checking dates, offers, and claims side by side.
Related research
State machines for campaign orchestration: making approvals impossible to skip
Campaigns move through predictable states: draft, review, approved, live, paused, complete. Modeling them explicitly makes agent orchestration predictable.
Supervisor agents and the limits of agents managing agents: judgment stays with people
Supervisor agents can coordinate and check other agents. They work best deciding what people should look at, and worst when they replace the looking.
Holiday campaign orchestration: a week-by-week agent plan
Holiday campaigns pack channels, offers, and deadlines into a short window. A week-by-week plan shows where agents help and where people stay in charge.
Put this research to work
Marketix turns these patterns into software: agents, automated workflows, and a hub that keeps people in control. Sign up for early access.
