The campaign settings
They open from station 05 of the guide (Define settings, later Show settings), from Campaign details (Edit campaign), and from the campaign’s menu on Campaigns (Settings, once a profile is linked).1
Profile & automation
The campaign’s profile is already there, linked in the guide. Decide how far a run goes on its
own. Every run always personalizes; these three switches decide what follows.
For a first campaign, switch the review gate on.
2
Batches
Group the people from your list into batches: let
split them for you, or press Add batch and pick them yourself. This step also holds the
: the moment your preview images and animations start
from. Leave it unset and the system picks a window around the personal moments.
3
Channels
Tick the channels you will send on, such as email, LinkedIn or WhatsApp. This writes the matching
outreach copy for each recipient. It does not send anything.
4
Review
Check the summary and save. Saving activates the campaign and locks its profile.
Batches, and why they are small
A is a group of people produced together. It references rows in your list rather than copying them, so your list stays the single source of truth. A batch holds up to 50 recipients. That is a deliberate limit, not a performance ceiling: it keeps any single mistake small and reviewable. Auto batches splits a larger list for you; run the first batch before you commit to the rest. When you pick people, two guards run:- Duplicates inside your selection are collapsed.
- Overlap warnings appear when someone is already in another batch of this campaign, or another campaign on the same profile. Overlap is allowed, since re-running someone can be intentional, but it should never happen by accident. Each membership produces and costs separately.
Running a batch
Press Run. Every person moves through up to four , and the batch card shows one progress bar for each.A batch is only complete when the last preview image is built, not the last video. Ready means
sendable. Hold your send until the whole card is green.
The presenter master
A presenter’s first batch starts with one more bar, above the four: Master. Each presenter’s shared scenes are produced once, as their , and every recipient of theirs derives from it. The bar fills as that work completes: the voice first, then each clip. The line beside it names the presenter, what is happening (voicing the scenes, rendering proxies) and the time so far against what a build of this profile usually takes:2:40 of ~6 min. Past the usual time it says taking longer than usual: nothing is wrong, it is
still working. The recipients start when the bar is full. The toast after Run says the same at
the moment you press it. Later batches of the same presenter show the bar full and ready at once.

A presenter's first batch: the Master bar fills as the voice and each clip complete, with the time so far against the usual build time.

Campaign details with a completed batch: the profile and automation along the top, then one card per batch with its four phase bars.
Controls
When a batch will not start
The most common reason is consent. A batch whose presenters have not all consented tells you so before it runs: it names each presenter who is blocking, counts the recipients affected, and offers a direct route to the cast to chase them. Re-check once they have acted.Reading a failure
Failure is a visible state rather than a mystery. The batch card counts failures per phase and shows the most recent reason. Inside the batch, each failed person carries their own reason. “Waiting for presenter master” under the bars is not a failure: those recipients start when the Master bar above them is full. Each presenter’s shared scenes are produced once and then reused for all of their recipients, so the first person of a presenter takes longer and the rest are quick. That is the system saving you time and money. When a master itself fails, the card says so with the reason; its recipients fail with it, and a new batch retries the build once you have fixed the cause.Next
Auto batches
Split a long list into batches in one go.
Reviewing before you send
Read every script before anything is rendered.
The manifest and sending
Collect the results and get them into your sending tool.

