Introducing Automations: No-Code Workflows in ASH

Most teams lose leads not because the intent was weak, but because a follow-up slipped through the cracks. Someone was on leave, the sheet did not get updated, and a warm enquiry went cold. Our new Automations builder is designed to take that repetitive, easy-to-forget work off your team's plate. It is fully no-code: you describe what should happen and when, and ASH does the rest in the background.

How an automation is put together

Every automation follows the same simple shape: a trigger, optional conditions, and one or more actions. You do not write any code or formulas.

• Trigger is the event that starts the workflow. Today you can start on lead created, lead stage changed, or lead inactive for a set number of days.
• Conditions narrow down when the actions should fire. For example, only run when the source is IndiaMART, or only when the course interest is a particular programme.
• Actions are what ASH does in response. You can create a task, send an email template, enrol the lead into an email sequence, send an SMS template, or notify the lead owner.

You can chain several actions into one automation, so a single trigger can create a task and notify the owner at the same time.

Three examples worth setting up first

Rather than describing every option, here are three automations that most teams find useful on day one.

• Welcome new website leads. Trigger on lead created, condition source is Website, then enrol the lead into a short email sequence and create a first-call task for the owner. The enquiry gets a prompt acknowledgement even if your team is mid-conversation with someone else.
• Re-engage quiet leads. Trigger on lead inactive for seven days, then send an SMS template and notify the owner to review. This is a gentle nudge, not a guarantee the lead will respond, but it makes sure nobody is quietly forgotten.
• Stage-change handoffs. Trigger on stage changed to a qualified stage, then create a task for the next step and send the relevant email template. The handoff between stages becomes consistent instead of depending on who remembers what.

Where email and SMS actions fit

Automations can trigger email and SMS actions, and those channels are part of the Enterprise plan. If you are on Enterprise, sequences and SMS templates plug straight into your workflows. If you are not, task and owner-notification actions still work, so you can automate assignment and follow-up reminders regardless of plan. You can read more about the messaging side in our posts on email marketing and SMS campaigns.

A note on control

Automation should reduce mistakes, not create noise. We recommend starting with one or two workflows, watching how they behave for a few days, and expanding from there. Every action an automation takes is visible in the lead's activity trail, so you always know why a task appeared or an email went out. You stay in control; ASH simply handles the parts that are easy to forget. To see how this fits with the wider product, have a look at our features overview.