scenario_12 // multi-agent orchestration
How do multi-agent email workflows avoid stepping on each other?
Three agents now run email: one manages onboarding, one runs winback, one drafts the newsletter. Last Tuesday a new trial user received eleven emails in one day as all three agents claimed the same contact. Each agent behaved correctly in isolation; together they spammed. The team needs coordination primitives before adding a fourth agent for dunning.
Multi-agent collision is an emergent failure no single-agent test catches. Frequency caps, journey enrollment, and send priority live in shared state that independent agents cannot see unless the architecture forces them to. Governance must move from per-agent permissions to system-level orchestration.
Orchestration Engineer perspective
The engineer proposes a central send governor: every agent proposes sends into one queue carrying recipient, priority, and journey context, and the governor enforces global frequency caps, priority ordering, and mutual-exclusion rules before anything emits. Agents never call send endpoints directly; they hold propose rights only. Shared state includes per-recipient recent-send history, active journey enrollments, and suppression flags, all readable by every agent so proposals improve instead of colliding blindly. Conflicts resolve deterministically by written priority, not by whichever agent runs last.
Lifecycle Lead perspective
The lifecycle lead adds journey-aware rules: onboarding beats newsletter, dunning timing obeys billing logic rather than marketing priority, and winback never fires while onboarding is active. A contact belongs to exactly one primary journey at a time with explicit handoff events between them. The lead also caps total touches per recipient per week across all agents, forcing tradeoffs into the open: if the newsletter wants the slot onboarding needs, humans decide, not racing schedulers. Weekly cross-agent send calendars make the contention visible before recipients feel it.
Founder perspective
The founder questions whether three agents are needed at all, suspecting Conway's-law sprawl where each hire built their own automation. Consolidating overlapping agents into fewer, better-supervised ones with clear portfolios often beats building coordination infrastructure for a crowd. If multiple agents survive the cull, each gets a written charter naming its audience, its capped send budget, and its escalation owner, reviewed monthly. Headcount discipline applies to machines too.
takeaway // apply monday
Practical takeaway
Route all agent proposals through one send governor enforcing global frequency caps, journey exclusivity, and written priority order; give agents propose-only rights with shared recipient state; publish a weekly cross-agent calendar; and charter every agent with audience, budget, and owner. Consolidate agents before orchestrating crowds.
Evaluate journey orchestration and automation-run costs in our 15-tool agentic email comparison, the pricing index, and the Resend pricing guide.