Automate the repetitive work without scripting every customer
QualiBot combines form-based automation rules, agent macros, Brain and human assignment. Use deterministic rules where consistency matters. Use Brain where the customer speaks naturally and context matters.
Five events can start a rule
Every automation rule begins with one of these platform events.
A conversation is created
A conversation is updated
A conversation is resolved
A conversation is opened
A message is created
Apply supported conditions
Rules support AND or OR condition logic.
Complete supported actions
Rules handle the deterministic path. Brain handles the conversational one.
A rule and Brain can act on the very same conversation, each doing the part it's built for.
A platform event fires
A new conversation, a new message or a status change.
Rule conditions evaluate
Inbox, status, priority, labels, language or message content.
Brain works the conversation
Understands intent, calls approved tools and hands off when needed.
Platform actions apply
Assign, label, message, note, webhook or attachment.
The human team reviews and continues
Whenever a conversation needs a person.
Each rule runs immediately against one of the five supported trigger events, so behavior stays predictable. Sequencing across days, recurring schedules and direct CRM or MCP calls run through Brain's tool calling during a conversation, the webhook action, or an external workflow platform.
Macros for agent-controlled speed
A macro lets an agent execute a predefined group of actions in one click. Macros may be personal or global.
Apply a Qualified label
Set High priority
Assign the sales team
Send the approved next-step message
Add a private note
Move the conversation to Pending
Rules and Brain, working the same operation
New inquiry
A new conversation enters the right inbox. Brain asks qualification questions, and a rule routes the resulting conversation by label, language or another stored field.
Priority escalation
When priority changes to Urgent, assign a team and send an internal email notification.
Out-of-office handling
Use inbox working hours and out-of-office messages while preserving the customer conversation for the next available agent.
Customer feedback
CSAT is sent after resolution when enabled. Pair CSAT review with status, label or priority-based rules to route follow-up.
How rules behave
Is there a drag-and-drop workflow canvas?
Automation is configured through a structured form: one trigger event, a set of conditions and a fixed set of supported actions.
Can automation call an MCP tool?
Automation calls a webhook as its external action. Brain calls MCP tools directly, inside an active conversation.
Can automation wait a few days before acting?
Rules run immediately when one of the five supported events occurs. Multi-day sequencing runs through Brain, campaigns or an external workflow platform.
Can we review past automation runs?
Automation today runs on triggers, conditions and a fixed set of supported actions, including Brain-driven actions and a webhook action that lets you log and retry runs on your own receiving system. Contact us if your team needs dedicated run-history and retry tooling for advanced workflows.
Is loop prevention in place?
Yes — QualiBot prevents a rule from directly retriggering itself. Test multi-rule designs, since separate rules can still cascade into one another.
Bring one manual process that consumes agent time
We'll separate what belongs in deterministic rules, what belongs in Brain and what must remain human.