Agent triggers: when X happens, do Y
No-code rules that watch for something and act on it.
A trigger has a condition (a keyword, a button tap, a new contact, an event from an integration), and an action: send a template, reply with a fixed message, tag the contact, assign it to someone, or call your own endpoint.
Rules run in order, so put your specific ones above the catch-all.
Follow up when a customer goes quiet
One global rule that nudges conversations nobody replied to.
Set the wait time and the message once and it applies across the account, rather than being configured chat by chat.
Follow-ups skip anyone who has already replied, and skip chats a human has taken over.
Auto messaging: dates and reminders
Birthday, anniversary, renewal and payment-reminder messages that run themselves.
Point the automation at a date field on the contact and it sends on the day, every year, without anyone remembering.
Payment reminders can read the outstanding balance from Tally, so the amount in the message is current.
WhatsApp Flows: forms inside the chat
Bookings, orders, lead capture and surveys without sending anyone to a website.
A Flow opens as a native WhatsApp screen. The customer fills it in without leaving the app, which converts far better than a link to a form.
Attach a Flow to a template button and it can be launched from a campaign.
Where Flow responses go
Choose a destination per Flow: a Google Sheet, a dataset, or fields on the contact.
Each Flow has its own destination, so a booking form can write to your operations sheet while a lead form updates the CRM record.
Responses are matched back to the contact who submitted them, so nothing arrives anonymous.
Scheduled messages
Everything queued to go out later, in one list, cancellable.
Campaigns, API-scheduled sends and automation output all appear on the Scheduled Messages page with their send time.
Cancel any pending item from that page; anything already sent shows in campaign history instead.