Automations
When something happens, Aiva Chat acts.
Set rules once and they run on every call, lead, booking and order: create a task, alert your team, email a follow-up or have the AI call. No code, and templates to start from.
On every planStart from a templateWebhooks and API included
Rules
A trigger, then the actions.
Pick what starts the rule, narrow it down if you need to, then list what should happen, in order.
- Narrow it downOnly for one assistant, one location, inbound or outbound calls, or one lead source like web forms or lead ads.
- Personal messagesWrite {{firstName}}, {{phone}} or {{assistantName}} and each message is filled in from the event.
Actions
Real work, not just a notification.
Each action uses the same parts of Aiva Chat your team uses, so its results land where you already look.
- Create a taskA follow-up in Tasks, with a due date, for whoever picks it up.
- Send a notificationAn alert in the dashboard’s bell and on the mobile app.
- Send a follow-upAn email to the customer, written by you. Text follow-ups return when texting is back.
- Call the leadThe AI phones a new lead who agreed to be contacted, with a purpose you give it.
Safe by default
Rules that respect your customers.
Automations follow the same protections as everything else in Aiva Chat.
- Consent before callsA rule only calls a form or ad lead who agreed to be contacted, and never a website chat lead.
- Do-not-contactNumbers on your list are always skipped. If the list can’t be checked, nothing is sent.
- Checked messagesMessages filled in from caller details are checked before they go, so a rule can’t be tricked into sending payment instructions.
- LoggedRule changes are in your activity log, with who made them.
Webhooks & API
Connect your own systems.
For anything the rules don’t cover, send events to your own tools, or read and write your data with an API key.
- WebhooksOver 40 events, from calls and leads to bookings, passes, waitlists and orders. Signed with your secret, retried twice, with a delivery log and test sends.
- API keysKeys for your scripts and automation tools. They can work with contacts, calls, bookings and leads, but never change your account, billing or stored credentials.
- Up to 25 webhooksA webhook that keeps failing is paused for you, so a broken endpoint isn’t hammered.
How it works
Your first rule in a minute.
- 01Open Workflow RulesUnder Webhooks in the dashboard.
- 02Pick a templateOr start from a blank rule and choose the trigger.
- 03Fill in the gapsThe assistant that calls, the message, who gets the task.
- 04Switch it onIt runs on the next event. Pause it any time.
No. Rules run inside Aiva Chat. If you already use an automation tool, connect it with webhooks and an API key.
Not right now. Texting is switched off across Aiva Chat while we bring it back, so rules email instead. Text follow-ups, missed-call text-back and review requests return with it.
No. The AI only calls form and ad leads who gave consent, never website chat leads, and always skips your do-not-contact list.
Each one is signed with its own secret in the X-AIVA-Signature header, so your endpoint can check it came from Aiva Chat.
Work with your data: contacts, calls, bookings, leads and webhooks. It can’t change your account, billing, stored credentials or where calls and texts go.
Get started
Let the follow-up run itself.
Rules, webhooks and an API on every plan.