Write · Templates

One place to author the graph, because two places disagree

A template is the sequence definition. Ordered steps, a channel per step, the wait between them, branch conditions and parallel tracts. One per campaign. There is deliberately no second sequence-definition object, because two places to author the same graph is exactly how six code paths came to each re-derive today's chain and then disagree.

Talk to sales See pricing

GTM

MWMy workspaceworkspace

DemandSearch/14,208

Cross-channel default5 steps · 1 branch

EmailDay 0

Opening message, written from the trigger

LinkedIn+4 hours

Like the latest post. No follow

LinkedIn+5 min

Connection request with a fresh note

LinkedInOn accept, +24–30h

First message, written from their profile

EmailDay 6

New angle, never a bump

Any reply on either channel skips every pending step

What is actually going on

Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.

The default chain ships as an editable template

A workspace that never opens the builder behaves exactly as it does today. Opening it does not mean starting from nothing.

Goal belongs to the campaign, not the template

A webinar has a date. Book a call and get them to the webinar are different motions over the same copy. The template's goal degrades to an authoring default.

The gate runs against your step, not around it

Authoring a step does not author a way past compliance. The pre-send gate evaluates whatever the graph produced, with the same verdict requirement.

The ramp holds across a parallel tract

Two branches running at once is still one sending account. Pacing is enforced where the sender is picked, which is one place, so a fan-out cannot outrun it.

Step by step

How templates runs

1
Author
Steps in order, each with a channel and a wait.
2
Branch
Conditions on what happened. Accepted, replied, opened, nothing.
3
Attach
One template per campaign, alongside its audiences and senders.
4
Run
Each contact's run through the graph is a sequence, visible as rows the runtime actually wrote.

The numbers

Facts, not adjectives

Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.

WriteTemplates

Objects: template_steps, template_blocks
Per campaign: Exactly one template
Parallel: parallel_group on each queued step
Where it lives: /demand/templates
Review mode: Set on the campaign, not the template

Templates, honestly

What is the difference between a template and a sequence?

A template is the definition. A sequence is one contact's run through it. The sequences view is a read of what the runtime wrote, not a second copy of the graph.

Where did templates live before?

Four clicks down the settings rail, which filed the copy away from the work it governs. They moved to the demand section and the old path redirects.

Write

What to say, in a voice that is yours

Every feature

AI copywritingWritten from the evidence that made the lead warm, in your voiceOpen CampaignsAudiences × one template × senders, plus the rule that starts itOpen

Keep reading

All features

SequencesSequencesEmail first, then LinkedIn the same day. One entry, one chainRead more CampaignsCampaignsAudiences × one template × senders, plus the rule that starts itRead more CopyAI copywritingWritten from the evidence that made the lead warm, in your voiceRead more

Templates is one part of it. The rest runs too.

Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.