See it work
Three pieces, one rule.
At a glance
4 events
Baghdad-time conditions
Call your system
Extra tools
When an event happens, under your conditions, do what you want.
Rules that run after the assistant replies: you choose the event, set the conditions and decide what happens. The conversation is tagged, or handed over to an employee, or a notification arrives, or your system is called.
What it does
Automations, in detail.
Four events
New message, new conversation, handover to an employee, and conversation resolved.
Precise conditions
On the message text, its language, the channel, the customer ID, the hour and the day of the week in Baghdad time. All of them must be met.
Practical actions
Notify the team, tag the conversation, change its status, hand it over to an employee, run a smart action, and call your external system.
By priority
Every matching rule runs, the highest priority first.
Know why it did not run
The test conversation shows which rules ran and why others did not, such as: “Channel equals WhatsApp · Actual: site widget”.
A switch and a counter
Each rule has an on-off switch and a counter of how many times it ran.
How it works
From setup to your first customer.
Add a rule
With a name and a priority.
Choose the event
From the four events.
Set the conditions
All of them must be met.
Define the actions and turn it on
Then try it in a test conversation.
The full list
Everything in Automations.
18 features available today, in 4 groups.
Events
4 features
- New message
- New conversation
- Handover to an employee
- Conversation resolved
Conditions
4 features
- Message text, its language, the channel and the customer ID
- Hour and day of the week in Baghdad time
- Equals, contains, does not contain, in a list, greater than, less than, exists and pattern
- All conditions must be met
Actions
5 features
- Notify the team
- Tag the conversation and change its status
- Hand over to an employee with an alert and assignment
- Run a smart action
- Call your external system
Management
5 features
- A priority for each rule, and the highest runs first
- An on-off switch for each rule
- A counter of how many times it ran
- The test conversation shows what ran, and why others did not
- External calls never reach internal network addresses
Clear limits
What it never does.
Rules written into the platform itself.
- Never
runs a rule unless all of its conditions are met.
- Never
lets the owner assistant edit your rules; you edit them yourself.
- Never
lets calls to external systems reach internal network addresses.
Works with
Every service is worth more when connected to others.
Questions
About Automations
Is there a log of every time a rule ran?
Each rule has a counter of how many times it ran, and the test conversation shows what ran and why. There is currently no detailed log of each run.
Can it be connected to my system?
Yes, with the “Call an external system” action, which sends a request to your address. For signed events with retries, use the Developer tools service.
What time do the hour and day conditions use?
Baghdad time.