lexisOS
Setting things up…
Setting things up…
Loading features…
Every campaign carries its own workflow underneath — the campaign builder is the workflow builder.
A Campaign row always carries a workflow underneath it — there’s no parallel campaign engine duplicating what workflows already do. That means a campaign can branch, delay, and combine steps around its email send, not just fire one template at a list.
Branching, delays, and any of the 30 step types.
Its own status, list, and send-health tracking on top.
With subject-line A/B testing and tracking built in.
| Status | What it means |
|---|---|
| Draft | Being built — nothing sends |
| Active (sending) | Currently dispatching to its list |
| Paused | Sending is stopped; can resume from where it left off |
| Sent / Completed | Finished dispatching |
| Archived | Retired — kept for history and the health snapshot |
The parts specific to a bulk send, not shared with a one-to-one workflow.
Deterministic hashing means the same contact lands in the same variant on a resend — not a new coin flip each time.
A real tracking pixel for opens and a redirect for clicks, not an estimate.
Contacts on a suppression list are skipped automatically, org-wide.
Duplicate a campaign to start the next send from a known-good baseline.
A rolling send-health snapshot, kept for 90 days.
Send yourself a real copy before it goes out to the list.
A campaign’s send step carries the same approval setting as any other workflow step: send automatically, or hold every message as a Draft until a person approves it. Left alone, an email send step sends automatically — the same default as a standalone workflow, not a stricter one just because it’s a bulk send. Turn on approval for the step and the campaign pauses until someone signs off.
This step sends automatically as soon as it runs.
Start free and build your first campaign — the workflow builder is the campaign builder. Turn on approval before you publish if you want a human checkpoint.