ERIX FlowNewFeature
What starts an ERIX automation
Every automation begins with one event. Pick it when you build the automation, and ERIX starts a run each time it happens.
Replied
No reply
Try it: click a step to change it, add one, or press Test run.
Leads and the pipeline
Most follow-ups start from something that happens to a lead:
Forms and messages
Others start from something a customer does:
Bookings
An automation can start when a meeting is booked, rescheduled or cancelled. Appointment Reminders starts on a booked meeting and sends WhatsApp reminders 1 hour and 15 minutes before the appointment.
Examples by business
The same events cover very different follow-ups:
Templates that come ready
Templates are made for each industry. Welcome Journey starts when a new lead comes in, and Appointment Reminders starts on a booked meeting. Each one installs as a draft until you switch it on.
Every run on the contact
Each run is saved on the contact it's about, with every step and what it did, and it updates live while the run is going.
Coming soon
Today an automation starts on an event inside ERIX, once a day at a set hour, or when you run it for a segment. Webhooks, and schedules beyond once a day, arrive in version 1.2.
Questions
More on ERIX Flow
- FeatureAutomation steps in ERIX FlowAn automation is one starting event and a few steps. These are the steps in ERIX Flow today, and the ones coming in version 1.2.
- FeatureCustom steps in ERIX FlowBuilding your own steps, and sharing them in a marketplace, isn't available in ERIX Flow today.
- ComparisonERIX Flow vs Zapier for Indian SMBsBoth run automations, but they're built for different jobs. Here is an honest split of where each one fits.