Chatbots that actually branch,
not just auto-reply.
Convic's chain builder turns WhatsApp into a real conversation graph — buttons, lists, WhatsApp Flows, date and number validation, and live calls to your own APIs, all wired together with drag-free simplicity. Build a qualification flow, a support triage bot, or a booking assistant without writing a line of code.
Pick the shape that matches the conversation.
Not every automated message needs a decision tree. Convic gives you both a straight line and a graph — use whichever one the moment calls for.
Legacy chains
A simple list of messages that fire one after another with timed delays. No branching, no waiting for a reply — perfect for onboarding drips, reminder sequences, or a welcome series that just needs to go out in order.
- Triggers on a keyword or a brand-new conversation
- Each step is a template or a plain text message
- Configurable delay between every step
- Best for: announcements, drip sequences, reminders
Query management chains
Every stage waits for the customer's reply, validates it, and jumps to whichever stage that answer points to. This is how you build menus, qualification flows, bookings, and support triage that actually adapts to what someone says.
- Each stage is a node; stage[0] is always the entry point
- Branch per-option, or by date / number / text / regex
- Sessions expire and can restart after inactivity
- Best for: menus, forms, triage, bookings, lead qualification
Every stage is one of three shapes.
You never pick a "type" from a dropdown — the shape follows naturally from what you fill in. Set a Flow ID and it opens a form. Add a list of messages and it becomes a sequence. Leave both empty and it's a single message with optional buttons.
The number of options decides the UI.
You don't choose "buttons" or "a list" from a menu — you just add options, and WhatsApp's own rules take over.
Plain text
Just the message body — nothing to tap.
CTA button
A single button that opens option.url directly.
Reply buttons
Tappable chips. option.label is all that matters.
List message
A scrollable menu — needs option.description + listButtonText.
Each answer is a fork in the road.
For options-based stages, every button carries its own nextStageId. Leave it empty and picking that option simply ends the chat — with its own custom closing message.
Non-option stages branch differently — a date, numeric, string, or regex reply always advances via the stage's own single nextStageId, since there's no per-option choice to branch on.
Every stage remembers what came before it.
Reference an earlier reply or a known contact field directly inside a message body — never in a header.
One rule keeps the graph sane: a stage can only reference a stage that comes before it. The first stage can't reference anything at all.
A stage can call your own API.
Attach an API credential to any stage and its response feeds straight into later messages — a real balance check, not a canned reply.
user_inputwhatever the customer just typedstage_responsea captured reply from an earlier stagecontacta field on the contact recordstatica fixed value you set onceWhat teams actually automate.
Lead qualification
Ask budget, timeline, and intent, then route hot leads straight to a rep — cold ones to a nurture sequence.
Appointment booking
Offer available slots as a list message, confirm with a date-validated reply, sync to your calendar via API.
Support triage
Route by issue type, collect an order ID with regex validation, and escalate to a human with full context.
Order & delivery status
Pull live status from your logistics API and hand it back inside the same thread the customer is already in.
Feedback & NPS
A numeric-validated rating stage branches into a thank-you path or a recovery path automatically.
Event RSVP
Multi-message invites with a list of sessions, capacity checks via API, and an automatic waitlist branch.
Or skip the builder — describe the flow to your AI agent.
Convic's MCP server lets Claude read and write chains directly. Say "build me a 3-step booking flow with a fallback to a human" and watch it appear in your dashboard.
Your first flow takes ten minutes.
Start from a blank canvas or one of our templates — lead capture, support triage, or booking — and publish straight to your WhatsApp number.