Best fit
Repeatable routing, intake, reminder and data-update processes whose conditions and fallback paths can be written explicitly.
Published flows can react to supported conversation, message, comment, no-reply, AI-handoff, lifecycle, manual and campaign events, then run the steps and conditions you configure.
Connect messages, waits, questions, buttons, branches and A/B splits with assignment, labels, status, deal, inquiry and order creation, WhatsApp template and email sends, and teammate notifications. HTTP, webhook and Google Sheets steps are there when technical setup is needed.
Start on a conversation, message, comment, no-reply, AI-handoff, lifecycle, deal, order, inquiry, manual or campaign event, then narrow it with conditions such as channel, keyword, business hours, order status or saved contact data.
One active conversational flow drives a thread at a time, while instant background rules may run alongside it. Re-enrolment and reply-waiting guards reduce duplicate execution.
Choose one supported trigger, then add channel, keyword, hours, lifecycle or other conditions where applicable.
Connect the required messages, waits, questions, branches and workspace or integration actions on the canvas.
Run the simulator with scripted customer replies to see the branch each run takes, then publish and test one real conversation.
Check the visible start/end events, enrollment state and affected records; inspect application logs for external-step failures.
Repeatable routing, intake, reminder and data-update processes whose conditions and fallback paths can be written explicitly.
Common message, wait, question, branch, assignment, label, status and deal steps use the visual builder. Webhook, HTTP and Google Sheets steps may need technical credentials, schemas and security review.
Conversation created or opened, contact created, message or comment received, no reply, conversation assigned or resolved, AI escalated, lifecycle changed, deal created, moved, won, lost or stuck, order created or changed, inquiry created or changed, manual and campaign. Keywords, channel and hours are conditions rather than standalone triggers.
Yes. An AI step can generate a draft for later steps without sending, or send and assign the conversation to that agent. Its intent outlets, maximum turns, actions, knowledge, credits and escalation path still need testing.
Workflows that start when a conversation is created decide first; the default AI agent then takes the chat only as its rule allows. Settings → Routing lists every step in order, with a live preview of who would get a new chat on each channel.
Each capability supports a different part of the customer workflow.
An AI teammate
Answers from maintained knowledge in a configured language, runs enabled actions, and hands the conversation to a human under your rules.
Sell and fulfil in chat
Keep a catalogue with stock, let an AI agent or your team take the order in the conversation, then move it from new to delivered and message the customer at each step.
CRM & pipeline
Run deals on weighted pipelines with their contacts, company, products, quotes and next step, and see why you win and lose.
Campaign outreach and replies
Send approved WhatsApp templates to filtered audiences, then handle campaign replies in the shared inbox.
Insight, not guesswork
Review conversation volume, response and resolution times, team workload and the report filters available to your plan.
Lead capture and follow-up
Keep enquiries from connected channels with the contact record, then use configured AI, routing, deals and tasks to manage the next step.
Organised for busy periods
Use ownership, team routing, statuses and workload reporting to keep peak-hour conversations visible and accountable.
Sign-in and access controls
Use encrypted connections, optional two-factor sign-in and passkeys, roles, phone masking and private-file checks as part of your security process.
Start your free 14-day trial today — no credit card required.