Describe the outcome. The agent figures out the conversation.
You do not script a dialog tree. You write an initiative, a brief with an objective and the questions worth asking, and the agent navigates the conversation itself. Around it, a visual journey builder decides who gets reached and when: triggers, sends, delays, branches, and exits. One layer for the talk, one layer for the path.
Outcomes on the inside, structure on the outside
Initiatives carry the intent. Journeys carry the orchestration. Together they replace the flowchart with something that bends instead of breaking.
- 01
Initiatives are an outcome brief
An objective, the guiding questions worth covering, and natural-language conditions for when to flag a conversation. The agent reads the brief and navigates the dialog on its own. No flowcharts, no if-X-then-Y scripts.
- 02
Journeys are a visual builder
A node canvas for the path around the conversation: triggers from a segment, a CDP event, or a manual start, send an approved message, run a conversation block, delay, branch on a decision, dispatch an event, or exit.
- 03
One agent, full thread history
A single agent carries the whole conversation and prioritizes the objectives in the brief. It does not forget what was said three messages ago, and it weighs what matters most right now.
- 04
Enrollment caps and control
Frequency caps keep a customer from being enrolled into too much at once, so automation never turns into a barrage. You decide the path and the limits; the agent decides the words.
No flowcharts. A brief the agent reads and runs.
Write what a good outcome looks like, the objective, the questions worth asking, and the conditions that should flag a conversation for a person. The agent takes it from there, navigating the actual dialog in the customer language, adapting to whatever they say. You train a worker, not maintain a script.
- Objective plus guiding questions, in plain language
- Natural-language flag conditions, not branching logic
- The agent designs the conversation, not you
Initiative: Win back paused subscribers
Understand why subscribers paused and bring back the ones we can.
- What made you pause your subscription?
- What would bring you back?
- Did anything about the price feel off?
Draw the path and the timing in a visual builder
Journeys are a node canvas for the path around the conversation. A trigger starts it, from a segment, a CDP event, or a manual kickoff. From there: send an approved message, run a conversation block, wait, branch, dispatch, or exit. You own the orchestration; the agent owns the dialog.
A bot builder makes you draw the conversation. Boom makes you describe the outcome.
Where the workflow builder differs from scripting a chatbot or hiring it out to an agency.
| A bot builder | An agency build | Boom workflow builder | |
|---|---|---|---|
| Who designs the dialog | You, every branch | They do, then bill changes | The agent, from your brief |
| Off-script messages | Fall through or break | A change request | The agent adapts |
| Who runs the timing | You wire it | They wire it | You, in the visual builder |
| How it improves | You rebuild flows | New statement of work | Learns from your team feedback |
Questions about the builder
See the builder on a workflow that matters to you
Book a 15-minute walkthrough and we will write an initiative and wire the journey around it on a real case.