Automation steps in ERIX Flow

Send a message

Send a WhatsApp message to the contact the run is about. Inside WhatsApp's 24-hour window you can send a normal message; outside it, use a template WhatsApp has approved. The message can use the contact's details, such as their first name.

Wait

Pause the run for some minutes, hours or days, such as two days before a follow-up, so messages arrive when they make sense instead of all at once.

Wait for a reply

Pause until the contact answers or a time limit ends. The run then carries on down one of two paths: Replied, when they answered, or No reply, when the time ran out. It's the step behind every “nudge them if they go quiet” follow-up.

Ask for approval

Hold the run until someone on your team decides. Use it before money or a customer message goes out, so nothing leaves without a person's OK. Requests collect on the Approvals page, live.

AI reply

Let the AI agent write the reply from your knowledge: documents, price lists, FAQs and website pages. Like the agent in the inbox, it drafts for a person by default, and refunds, complaints and medical questions always go to your team.

Update the contact

Save what the run learned on the contact, such as a tag or a field, so your team sees it on the timeline and the pipeline.

Coming soon in version 1.2

These steps aren't in ERIX Flow today. They arrive in version 1.2:

• Webhooks, to send data to other software and take data in
• Schedules beyond once a day, such as every few hours or on chosen weekdays
• Branches with more than two paths, and AND/OR conditions
• Loops over a list
• Connected apps