Act on it together

Coordinated Multi-Party Sequencing

Run the right sequence on every contact, in sync.

Coordinated sequencing runs ordered, timed multi-touch plays across a target list — and keeps your whole team from stepping on each other. Every contact gets the right touch at the right interval; no duplicate outreach, no missed steps. Built for sales cadences, customer success plays, and structured outreach programmes where the sequence is the product.

Shape

Operational dimensions

Human co-pilot

Person and system work side-by-side.

Scheduled

Fires on a clock.

Medium data gravity

Holds working state that compounds over runs.

Two-way integration

Reads from and writes to external systems.

Inputs

sequence definition (ordered steps, intervals, exit conditions)
target list with segmentation metadata
actor pool (who executes which touch types)
per-target response events (replied, booked, opted-out)

Outputs

scheduled next touch per actor per target
de-conflicted assignment list (no duplicate outreach)
per-target sequence position and status
exit/pause verdicts triggered by response events

Mechanism

Executes an ordered, cadenced series of multi-party touches against a population of targets — managing per-target progress through the sequence and de-conflicting across actors.

Why this is a primitive

Cannot be decomposed: the cadence engine (ordered steps × time intervals × per-target progress × cross-actor de-conflict) is a single operation — orchestrate-cadence-against-population. It is not a state machine over one object (that's stateful-lifecycle) and not a gating decision (that's workflow-routing); it is the rhythmic execution of a pre-defined sequence across many targets simultaneously.

Where it shows up

B2B sales cadence — SDR team runs a 12-step outreach sequence across 500 leads; system assigns each touch to the owning rep, prevents colleagues from emailing the same contact, and exits the target on reply

Customer success onboarding play — CSM team runs a structured 6-week check-in sequence for every new account; each milestone touch is assigned on schedule, skipped if the client responds early

Debt collection outreach — collections team runs regulatory-compliant multi-channel contact sequences; system enforces mandatory cooling-off intervals and de-duplicates across agent teams

Clinical trial participant follow-up — study coordinators run scheduled assessment-touch sequences across the participant cohort; system prevents duplicate contact and tracks per-participant position

Related primitives

Composes with

Stateful Object Lifecycle →Multi-Role Live Operational Surface →Classificatory Inference →Workflow Routing & Gating →

Alternative to

Workflow Routing & Gating →Stateful Object Lifecycle →