Email Campaign Bit
Email flows en nieuwsbrieven die openen.
Bouwt email-flows (welkom, nurture, win-back) en nieuwsbrieven met onderwerpregel-varianten en preview-text.
See what changes for you
Describe your situation and see how this Bit fits your operation. Nothing is stored or sent — this runs entirely in your browser.
Live in three steps
- 01
Install into your workspace
Email Campaign Bit is added to your workspace from the Bit Store. No integration project, no implementation partner. It runs across a team workspace, so multiple operators share one queue, one memory and one audit trail.
- 02
Point it at your own context
You give it the context it needs for the work it does — starting with welkom-flow. It reads your workspace memory, so it does not ask twice.
- 03
Let it run and review the output
Every run costs 4 credits and lands in your workspace with the reasoning attached. You approve, adjust or reject — the Bit never ships anything irreversible on its own.
What this Bit takes over
- Welkom-flow
- Nurture-flow
- Win-back
- Subject-varianten
- Preview-text
Questions before you install
What does one run of Email Campaign Bit cost?
Each run costs 4 credits. Credits come with your plan, so there is no separate licence and no per-seat fee for this Bit.
Which plan do I need for this Bit?
Email Campaign Bit sits in the Scale OS layer. It runs across a team workspace, so multiple operators share one queue, one memory and one audit trail.
What does it actually deliver?
Bouwt email-flows (welkom, nurture, win-back) en nieuwsbrieven met onderwerpregel-varianten en preview-text. In practice that means a publishing and campaign rhythm that does not depend on your calendar.
Can it act without me approving first?
No. Anything irreversible — sending, publishing, paying, contracting — requires an explicit confirmation from you. The Bit prepares the work and shows its reasoning; you decide whether it ships.
Where does my data live?
Inside your own workspace. The Bit reads the workspace memory you give it access to, writes its output back there, and every run is logged in the audit trail. Your data is never used to train a shared model.
What can I ask it on day one?
Start with the work it already knows: Welkom-flow; Nurture-flow; Win-back.
Install your first operator
Start with one Bit, one function, one measurable result. Add layers when it proves itself.
