Messaging frameworks agents write from
A sequence is a framework, not message copy. Writing a purpose an agent can generate against, and the edit that silently changes every live enrollment.
Product walkthrough
See it in RevTech
See an agent use account and contact context with approved messaging standards to prepare a sequence for human review.
Frameworks, not copy
A messaging sequence is a reusable framework: why the sequence exists, which artifacts the agent may reference, how many steps it runs, what each step should accomplish, and the overall style. It is not message copy, and the detail view shows you the framework rather than any one account's generated message.
The agent writes the actual message later — per account and per contact — when the sequence runs. That separation is what makes a sequence worth authoring once: you are encoding the shape of a motion, and the specificity comes from the record it runs against.
Purpose does most of the work
Purpose is the instruction the agent generates against, which makes it the single field worth spending time on. Write it as an outcome. "Re-engage a dormant executive sponsor" gives the agent something to aim at; "follow up" gives it a genre.
Style attributes set tone, and there is an optional guidance box for more tone. It is not for message copy. Putting a draft sentence there produces a framework that generates one sentence well and everything around it generically.
Steps
Set the number of steps, then give each one a purpose and a message type. Steps run in the order shown, and one purpose per step is the discipline that keeps the sequence coherent. A step asked to do two things produces a message that does neither cleanly.
Reducing the step count asks before discarding a step you have already written, so the destructive edit is not silent.
- Reference artifacts scope what the agent may draw on — narrow them deliberately rather than including everything
- Save as Paused stores an editable framework that cannot be enrolled
- Saving active makes it enrollable; neither action enrols anyone or generates a message on its own
The edit worth being careful about
Sequences are not versioned. Saving replaces the step set in place, and the new framework applies to every enrollment, including ones already running. A contact halfway through a five-step sequence will receive the rest of the new one.
The panel warns before that happens. For anything more than a wording change, pause the sequence first, make the change, and re-activate. This is the one place in messaging where a routine-feeling save reaches live contacts.
Reading the portfolio
The list gives total and active sequences plus contacts enrolled across the workspace, one row per framework with step count, status, owner and enrollment. Filters by status and owner live in the URL, so a filtered list is a link you can send to whoever owns it.
Cards without a data source say so explicitly rather than showing a zero. That distinction matters: a zero you can act on and an absence you cannot look identical unless the product refuses to fake one.
What to take away
- You author the framework. The agent writes the message, per account and per contact, when the sequence runs.
- Write purpose as an outcome. "Re-engage a dormant executive sponsor" beats "follow up".
- One purpose per step, and steps run in the order shown.
- Sequences are not versioned. Saving replaces the step set in place, including for enrollments already running, so pause first for substantial changes.
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo