Initiatives: an outcome brief
Write an objective and guiding questions; the agent runs the dialog without a flowchart.
Describe the outcome. The agent figures out the conversation.
Write a brief with the objective and key questions, and the agent runs the conversation. A visual journey builder decides who gets reached and when.
What it does
Outcomes on the inside, structure on the outside
Initiatives set what the agent should achieve. Journeys set who it reaches and when.
Journeys: a visual builder
Drag nodes to set when customers get contacted, what they receive, and when they exit.
One agent, full history
One agent keeps the whole thread in memory and works the brief objectives in priority order.
Enrollment caps and control
Frequency caps stop a customer from being enrolled in too much at once.
Initiative: Win back paused subscribers
Objective
Understand why subscribers paused and bring back the ones we can.
Guiding questions
- What made you pause your subscription?
- What would bring you back?
- Did anything about the price feel off?
Flag conditions
Flag if they mention priceFlag if churn risk
Boom navigates the conversation from this brief
The inside layer
No flowcharts. A brief the agent reads and runs.
Write the objective, the questions to ask, and when to flag a person. The agent runs the dialog in the customer language and adapts to whatever they say.
- Objective and questions in plain language
- Flag conditions, not branching logic
- The agent writes the conversation
TriggerSegment: past_due
SendWhatsApp template
ConversationAgent runs it
DelayWait 2 days
DecisionReplied?
On the decision
replied
DispatchEvent: reactivated
no reply
ExitLeave journey
you draw the path, the agent runs each conversationenrollment cap: 1 / 30d
The outside layer
Draw the path and the timing in a visual builder
Start a journey from a segment, a CDP event, or by hand. Then send an approved message, run a conversation, wait, branch, or exit.
FAQ
Questions about the builder
So there is no flowchart for the conversation?
Right. You write an initiative with an objective, guiding questions, and flag conditions, and the agent runs the dialog. Journeys only set triggers, sends, delays, and branches.
What can trigger a journey?
A customer entering a segment, a CDP event, or a manual start. The journey can then send, run a conversation, wait, branch, dispatch an event, or exit.
How does the agent get better?
It keeps the full thread history, prioritizes the brief objectives, and improves from your team feedback over time.
Can I control how often a customer is contacted?
Yes. Enrollment frequency caps stop a customer from being pulled into too much at once. You set the limits in the journey.
See what the builder connects to
See the builder on a workflow that matters to you
In 15 minutes we build an initiative and its journey on your real case.