Event-triggered automation
WhatsApp automation that reacts to what customers send
Automations run when something happens in WhatsApp messaging: a customer sends a message, or a conversation is created. They check conditions you set and act, without anyone opening the inbox.
The problem automation solves
The problem
Many inbound messages need the same first response: a price list, a confirmation, a note that someone will reply soon. Typing them by hand is slow, and the contact list never gets organised.
What changes with Vowels Connect
An automation listens for inbound messages, checks what they say or who sent them, and sends the right reply or template. It can also sort contacts into groups for later campaigns.
How it works
Trigger, conditions, actions
Each automation has exactly one trigger. Conditions branch into yes and no paths, and actions run in order.
Triggers
- Inbound message
- A customer sends a WhatsApp message.
- Conversation created
- A new conversation starts from an inbound message.
Conditions
- Message contains
- Matches text, ignoring letter case.
- Contact group
- The contact belongs to a saved group.
- First message
- It is the conversation’s first inbound message.
Actions
- Send text
- Sends only while the 24-hour window is open.
- Send approved template
- Uses an approved company template.
- Add to or remove from group
- Keeps contact groups up to date.
- Delay
- Waits from 1 minute to 7 days, then continues.
- End
- Stops the automation.
Messages can include contact fields such as first name, full name, phone, and company name. An automation can be saved as a draft and activated when it is ready.
Use cases
Automations worth setting up first
Instant first reply
When a conversation is created, send an approved welcome template so every new customer hears back right away.
Keyword-based tagging
When a message contains “price” or “demo”, add the contact to the matching group so it is ready for a campaign.
Follow up after a wait
When a customer’s first message arrives, wait a set time, send an approved follow-up template to that contact, then end the automation.
Part of the platform
Automation or a conversation flow?
| Automation | Conversation flow | |
|---|---|---|
| Starts when | An inbound message arrives or a conversation is created | A customer sends the start keyword of a published flow |
| Customer sees | A reply or template, often without noticing an automation | Interactive steps with buttons, lists, and media |
| Best for | First replies, tagging, delayed follow-ups | Menus, guided questions, and handoff to a person |
Automation questions
Does an automation start from a keyword?
No. Automations start from an inbound message or a new conversation. You can then check whether that message contains specific text. For keyword-started conversations, use conversation flows.
Can it send a template automatically?
Yes, if you add a send-approved-template action and the template is approved and sendable.
Can one automation branch?
Yes. Conditions have yes and no paths, and each path can continue with its own actions.
Who can create automations?
Owners and admins create, edit, and activate automations.
Automate the replies you send every day
Automations start on the Starter plan. Create an account and connect your number to build your first one.