Automation without
the invoice.
Drag, drop, ship. Build triage, routing, and escalation flows visually with branches on language, intent, sentiment, order status, and anything else your customer record exposes.
- 1Incoming messageEmail or chat
- 2Classify intentAI understands the ask
- 3BranchRoute by topic
- 4Look up orderShopify
- 5Send replyOn-brand, in your tone
- 6ResolveClose the loop
If you can draw it on a whiteboard, you can build it here.
No YAML. No JSON. No Zapier tax. Branches, conditions, AI steps, and data lookups are first-class blocks you connect in minutes. Preview any branch against real past conversations before you publish.
- Drag and drop every step, condition, and action
- Preview branches against real historical conversations
- Version control with one-click rollback to any flow
- Test mode runs without touching live conversations
What teams build in the first week.
Most customers go from blank canvas to live flow in under an hour.
Order triage
Route shipping questions straight to a Shopify lookup and auto-reply. Keep humans for the edge cases.
Returns and refunds
Branch on order status, value, and days since purchase. Handle 80 % automatically; escalate with full context.
Language routing
Detect the customer's language and route to the right agent team or the right AI persona.
Sentiment escalation
Flag frustrated customers before they leave a one-star review. Set a threshold, add a step, done.
Off-hours handling
Different flows for opening hours, evenings, and weekends. No code, just a time condition block.
First-contact resolution
Chain AI, lookup, and human steps. Every handoff carries full context so customers never repeat themselves.
Flow builder questions, answered.
How is the flow builder different from the AI agent?
Flows are deterministic: same input always produces the same path. AI agents use judgment. Use flows for 'always do X when Y' rules (route VIP customers, send an after-hours message, branch on order status). Use the AI for everything that needs reading the customer's intent. They compose: a flow can route to an AI agent, and an AI agent can be configured to skip when a flow already handled a conversation.
Does the flow builder work without code?
Entirely. Drag, drop, configure with form inputs. No expressions, no scripting language. Templates use double-curly placeholders for dynamic values. If you can draw it on a whiteboard, you can build it here. No YAML, no JSON, no consultancy invoice.
Can a flow call our own API?
Yes. Add an action node, pick the custom HTTP tool, point it at any endpoint you have configured. Same tool the AI agent uses. Useful for refund APIs, inventory checks, internal admin actions, anything you can hit with HTTPS and JSON.
Can we test a flow before it goes live?
Yes. Save the flow as a draft (drafts do not run on real conversations). Trigger a real test conversation that matches your conditions and watch the flow run end to end. Preview any branch against the last 500 historical conversations to see what the flow would have done.
Can we roll back a flow publish?
Yes. Each publish stamps a version. The Versions view shows every previous version; click Restore on any one and it becomes live immediately. The current version is archived (not deleted) so nothing is ever lost.
How many flows can we have?
Per plan: Starter locked (no flows), Growth 2 flows, Business 6 flows, Scale unlimited. Each flow can be arbitrarily complex with as many branches, conditions, and actions as you need.
Is the flow builder a workflow engine like Zapier?
No. The flow builder runs on Keloa events against Keloa data: a message arrives, a conversation reopens, a contact is created. It cannot be triggered by an external webhook today and cannot move data between two third-party systems on its own. For cross-system orchestration ('when payment succeeds, create CRM deal'), use a workflow tool built for that.
Build your first flow today.
Start from a template or a blank canvas. No code, no consultants, no waiting.