Visual Flow Builder
Design visual, deterministic pathways to capture leads, qualify prospects, coordinate bookings, and process payments automatically. When structured conversations finish, our hybrid orchestrator shifts control to AI knowledge-base fallbacks.
Interactive Flow Simulation
Click through the stages below to understand how the Flow Engine processes an incoming conversation step-by-step:
Simulation Steps
User sends: 'Hello'
An incoming conversation activates the Flow
Building Blocks (Node Types)
A flow is composed of sequential steps called **Nodes**. Each node type is optimized for a specific interaction. Click on the tabs below to explore detail specs:
Message Node
The fundamental delivery node. Sends static or variable-interpolated text to a user across active channels.
Key Options:
- Text Content:The text message body. Supports variable inserts like
{{contact_name}}. - Quick Replies:Tappable quick-select buttons that appear in chat. Selecting one sends the text back and moves to the next node.
- Postback Buttons:URL buttons or actions (Facebook Messenger / WhatsApp specific) to link out of the chat.
{
"type": "message",
"content": {
"text": "Hi {{contact_name}}! Welcome to ReplyBase. How can we help you today?",
"quick_replies": [
{ "label": "Book a Demo", "value": "demo" },
{ "label": "See Pricing", "value": "pricing" }
]
}
}Advanced Actions & Automations
ReplyBase provides custom action scripts tailored for lead-generation and conversion funnels:
1. Booking Action
Automates appointment setting. When invoked, it compiles collected values, logs a demo request in the activity pipeline, tags the user, and emails notification alerts directly to the administrators.
variableName as contact_email in a preceding input node so the booking engine has a target email.2. Checkout Action
Dynamically generates checkout pages using your Stripe integration:
- Checks if the tenant is active or currently running a trial.
- Constructs personalized Stripe URL, embedding the
tenantIdasclient_reference_id. - Prefills customer email on the Stripe Checkout page if
contact_emailwas collected.
3. Call Flow (Sub-Flows Stack)
For maximum reusability, you can split large workflows into smaller flows (e.g. separate flows for booking, pricing, and demo scheduling).
When a call_flow action triggers, the engine pushes the parent flow pointer to a session stack. When the sub-flow executes an End Flow action, the parent flow session is popped from the stack and resumes execution on the exact next step.
Beginner's Step-by-Step Blueprint
New to chatbot building? Follow this layout blueprint to deploy your very first Lead Qualification & Demo Booking flow:
| Order | Node Type | Settings Content | Outcome |
|---|---|---|---|
| 1 | Message | Text: "Hi there! Welcome. Ready to boost your team's support capacity?"Quick Replies: "Yes, let's go!", "Tell me more" | Welcomes user with buttons. Pauses execution. |
| 2 | Input | Variable: contact_nameType: Text | Captures response, cleans greetings, stores name. |
| 3 | Input | Variable: contact_emailType: EmailValidation Msg: "Please enter a valid email format:" | Validates format, retries if invalid, stores email. |
| 4 | Condition | Variable: contact_emailRule: contains value .gov or .edu → Order 6 (Enterprise) | Redirects high-value leads; default continues to step 5. |
| 5 | Action | Action: booking | Saves demo registration, tags lead, triggers dashboard alerts. |
| 6 | Message | Text: "Thanks {{contact_name}}! We've scheduled your slot. Check {{contact_email}} for details!" | Confirms slot and ends the structured flow session. |
Want a professional flow tailored for your CRM?
Skip the builder and have our developers create bespoke routing, booking calendars, custom Stripe checkouts, or advanced API integrations matching your business specs.