Skip to content
GuideMessagingIntermediate

Messaging frameworks agents write from

A sequence is a framework, not message copy. Writing a purpose an agent can generate against, how versions are pinned, and what approving a draft does.

RDRevTech DeliveryAgent delivery team 3 minUpdated

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.

See an agent use account and contact context with approved messaging standards to prepare a sequence for human review.
Part 1 of 6

Frameworks, not copy

A messaging sequence is a reusable framework: why the sequence exists, which artifacts the agent may reference, how many steps it has, 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 contact, when someone generates a step for them. 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.

RevTech: The real message-review editor contains an illustrative, user-authored renewal follow-up for review before saving. No message was sent.
The real message-review editor contains an illustrative, user-authored renewal follow-up for review before saving. No message was sent. Captured from the current application with illustrative sample data. Screenshot of the RevTech application; sample data.
The real message-review editor contains an illustrative, user-authored renewal follow-up for review before saving. No message was sent.
Part 2 of 6

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.

Part 3 of 6

Steps

Set the number of steps, up to twelve, then give each one a purpose and a message type: Email, LinkedIn Message, Voice Call Task or Other Task. Steps are ordered, 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, up to ten, scope what the agent may draw on — narrow them deliberately rather than including everything
  • Save Draft stores an editable framework without publishing it
  • Create & Publish makes it a live version that contacts can be enrolled in; neither action enrols anyone or generates a message on its own
Part 4 of 6

Editing a live sequence

Edits change the framework's draft until you publish again. Save & Publish then adds a new immutable version and makes it the live one. Contacts already enrolled stay pinned to the version they started on, and the sequence detail lists every published version and which version recent enrolments are on.

So a change reaches new enrolments, not the ones already in flight. That is the safe default, and it means a wording fix will not reach a contact who is already part-way through.

Part 5 of 6

From draft to sent

Drafts are generated from a record. AI Message on a contact, or Message beside a contact on an account, opens a dialog that shows the sequence, the step it will write and a box for guidance about this one contact. Generate Drafts writes the draft, and the review panel opens when it is ready.

The panel offers Save changes, Approve draft and Discard draft, with the revision history beneath. Approval is a decision about the content: nothing is sent or scheduled. Copy approved email (or Copy approved LinkedIn message) puts it on your clipboard, you send it from your own email or LinkedIn, and Mark step completed records the progress on the enrolment.

Part 6 of 6

Reading the portfolio

The list gives total and active sequences plus contacts enrolled across the workspace, one row per framework with its step count, status and enrolments. Contacts Enrolled counts enrolments, so a contact enrolled twice counts twice. 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, Open Pipeline and Revenue today, 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 drafts the message per contact when someone generates a step; a person approves it and sends it.
  • Write purpose as an outcome. "Re-engage a dormant executive sponsor" beats "follow up".
  • One purpose and one message type per step.
  • Publishing creates a new version. Enrolments stay pinned to the version they started on.
  • Approving a draft is a decision about content. RevTech does not send or schedule the message.
Demo

See how the work gets done.

Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.

Explore the demo