CRM automations for follow-ups, assignments and reminders
Superlane's workflow builder turns your follow-up rules into steps that run on their own. It is built, but not switched on yet, so workflows do not run for customers.
- Start from 10 events, such as a new enquiry
- Wait, branch, assign, create tasks and send email
- Stop when the customer replies, opts out or books
Automations are built but not running for customers yet.
The builder already creates and saves workflows, but none of them sends a message or changes a record until then. This page shows what the builder does, and what it cannot do yet.
How a workflow works
A workflow is one trigger followed by steps that run in order. The trigger is an event in Superlane, such as a new enquiry or a deal moving stage.
Build a workflow as a list, or as a diagram on a larger screen. Switching between the two keeps every step and setting.
Triggers: what starts a workflow
| Trigger | Starts when |
|---|---|
| Contact created | Someone adds a contact, or a lead source creates one. Contacts imported from a CSV file never start a workflow. |
| Enquiry received | An enquiry arrives from a website form, your private lead address or a Meta lead form. Or someone new writes to you first on WhatsApp or email. |
| Deal created | A new deal is opened. |
| Deal stage changed | A deal moves to another stage. Won and lost count as stages. |
| Contact owner changed | A contact is given to a team member, or taken away from one. |
| Deal owner changed | A deal is given to a team member, or taken away from one. |
| Payment received | A payment is confirmed through your own Cashfree account. Payment links are built but not switched on yet. |
| Customer replied | A contact replies on a connected channel. |
| Appointment booked | A meeting is booked on a workspace calendar. |
| Appointment cancelled | A booked meeting is cancelled. |
A trigger tied to a channel works once that channel is connected. For new workspaces, WhatsApp numbers and Meta lead forms wait on Meta's app review. Gmail and Microsoft 365 mailboxes wait on Google's and Microsoft's verification.
Steps a workflow can take
- Wait. Pause for a set time, up to 365 days, or until a fixed date and time.
- Wait until a time. Pause until a time of day, such as 10:00, on the weekdays you choose.
- If / else. Branch on a value from the trigger, the contact or the deal, such as the lead source or the new stage.
- Contact. Add or remove a tag, or update the contact's name, company, business type or status.
- Owner. Give the contact or the deal to a team member. A contact keeps an existing owner unless you choose to replace them.
- Deal. Create a deal in any pipeline and stage, or move the deal to another stage of its pipeline.
- Task. Create a task for the contact's owner or a named person, due from one minute to a year later.
- Notify a team member. They get your message as a task in Superlane.
- Send email. Send from your own connected business email address.
- Send WhatsApp. Send a free-text message from a number you allow for automated messages.
- Appointments. Book, reschedule or cancel a meeting on a workspace calendar.
- Call webhook. Send the details of the run to a secure web address used by your other software.
- Stop. End the workflow.
An If / else step can check whether a value equals, contains, is more or less than, or is one of a list. It can also check whether a value is filled in at all.
Rules every automated message follows
Automated messages follow the same consent rules as the rest of Superlane. Superlane checks them again just before each message goes out.
- Email. A marketing email goes only to contacts who agreed to email. A message the contact expects, such as a booking confirmation, can be marked as a service message.
- WhatsApp. The contact needs WhatsApp consent on record and must have written to that number in the last 24 hours.
- Opt-outs. A STOP reply blocks later WhatsApp messages, and an unsubscribe blocks later emails. A contact marked do-not-contact gets neither.
Stop rules and goals
Each workflow can stop for a contact the moment they reply, opt out or book an appointment. A follow-up then never chases someone who has already answered.
A workflow can also have a goal. It stops once the contact gets a tag you choose, or the deal reaches a stage, such as Won.
When a workflow stops, any message still waiting to go out is cancelled.
Workflows you can build
These examples use only the triggers and steps above. None of them runs until automations are switched on.
| What you want | Trigger | Steps | Stops when |
|---|---|---|---|
| Thank each new enquiry, then chase it | Enquiry received | Send a thank-you email. Wait 1 day. Create a task for the owner to call. | They reply, opt out or book |
| Chase a quote that went quiet | Deal stage changed | If the new stage is Quote sent, wait 3 days, then create a task for the owner. | They reply, or the deal reaches Won |
| Start onboarding when a deal is won | Deal stage changed | If the new stage is Won, create a deal in your Onboarding pipeline and notify the account manager. | It finishes |
| Review lost deals | Deal stage changed | If the new stage is Lost, notify the sales head to check the lost reason. | It finishes |
| Confirm a booked meeting | Appointment booked | Send an email confirming the meeting. | It finishes |
The starter setup adds two ready-made workflows: a thank-you email for each new enquiry, and a meeting confirmation.
Keeping automations polite
An automation that messages at midnight, or after the customer has replied, costs you goodwill. Three habits prevent most of it.
- Use Wait until a time so messages go out in working hours, such as 10:00 on weekdays.
- Turn on the reply, opt-out and booking stop rules in every follow-up workflow.
- Give each workflow a goal, so it ends once the deal moves on.
What automations cannot do yet
- No WhatsApp template step. The WhatsApp step sends free text inside the 24-hour window only. An automated reminder to someone who has not written recently is not possible.
- No date-based triggers. Nothing starts from a birthday, renewal or expiry date on a contact, or on a fixed schedule.
- No keyword or button branching. A workflow cannot read what a customer wrote, so it cannot route by keyword. WhatsApp button replies are not supported.
- No invoice step. Invoices are raised for a billing client on the billing page, not by a workflow. See GST billing.
- No SMS or calls. Superlane does not send SMS or make calls.
Active automations and sequences are limited by plan: 5 on Starter, 25 on Growth and unlimited on Scale.
Every new business gets a 30-day free trial, starting when its workspace is ready. Start your free trial.
Common questions
Are Superlane's automations live?
Not yet. The builder is built and saves workflows, but they do not run for customers until automations are switched on.
Can an automation send a WhatsApp template?
No. The WhatsApp step sends free text only, inside the 24-hour window after the customer last wrote. A follow-up to someone who has gone quiet needs a person to send an approved template.
Can a workflow start on a birthday or renewal date?
No. Workflows start from events, such as a new enquiry or a stage change. A wait step can pause until a fixed date, but nothing starts from a date saved on a contact.
Can an automation raise an invoice when a deal is won?
No. Invoices are raised for a billing client on the billing page. A workflow can create a task for someone to raise it.
Will a workflow take a lead away from its owner?
Only if you tell it to. The Assign contact step keeps an existing owner unless you tick the option to replace it.
Give every lead a lane.
Every new business gets a 30-day free trial. Plans start at ₹2,000 a month before GST, billed in rupees with GST invoices.