In this article
- Before automating: what happens by hand today
- Define routing rules, availability and exception handling
- Trigger tasks and messages without losing human ownership
- Test the failures, audit the outcomes, protect consent
- Lead-routing automation
- Mistakes, measures, and what good automation does
- Questions owners ask
Before automating: what happens by hand today
Watch an enquiry arrive. Where does it land — an inbox, a WhatsApp, the CRM? Who notices, how long after, and how do they decide who works it? What reminds that person to follow up on day three? Most SMEs find the answers are: an inbox, whoever looks, an hour to a day, and nothing. Write those down as the baseline: time to assignment, time to first contact, follow-ups completed per lead.
Decide the owner of the automations: the CRM champion or the RevOps person, who builds them, tests them and is the first call when one misfires — because one will.
Define routing rules, availability and exception handling
Routing rules are the answer to “who gets this enquiry?” written so a machine can apply them: by territory, from the city on the form or the phone number’s area; by service, from the page the enquiry came from or the drop-down; by round-robin among the available salespeople for everything else; by value or account type for the enquiries that should go to the owner. Availability: a salesperson on leave or out of hours is skipped, which needs a simple availability flag the team actually sets; an enquiry outside business hours is queued for the first person available in the morning and acknowledged immediately.
Exceptions are where automation earns or loses trust: an existing customer’s enquiry goes to their account owner, not round-robin; an enquiry that matches an open deal attaches to it rather than creating a new one; a spam or job enquiry is filtered before assignment; an enquiry the rules cannot place goes to a named default person, never to nobody. Every exception is a rule, and the default is the most important rule of all.
Trigger tasks and messages without losing human ownership
On assignment, the automation creates a task — “call within the hour” — on the owner’s list with the due time, notifies them on their phone, and starts a timer; if the task is not done by the standard, it escalates to the manager. On first contact logged, it schedules the follow-up sequence appropriate to the lead’s stage — a task on day two, a message template on day four, a call task on day seven — each as a task the person completes, with the message personalised at the top before sending. On any reply from the buyer, the sequence pauses and a task tells the owner to respond today.
The human owns the lead throughout: the automation reminds, drafts and escalates; the person calls, writes the first line and decides. Fully automated message sequences with no person behind them are the thing buyers have learned to ignore, and in India, where the reply comes on WhatsApp, the person has to be there to receive it.
Test the failures, audit the outcomes, protect consent
Test before switching on, with real enquiries sent by you: an enquiry from a new city, one from an existing customer, one at 9 pm on a Sunday, one with a missing phone number, one from a job-seeker, one that replies to the first message. Watch where each lands and what fires. Then test the failures: the salesperson on leave who forgot the flag, the integration that stops writing, the sequence that ran after a reply. Each failure gets a fallback — a daily report of unassigned or untouched enquiries to the manager is the simplest and the most valuable.
Audit monthly: enquiries assigned within the standard, tasks completed on time, sequences paused on reply, escalations fired and what happened. Consent: follow-up on an enquiry the buyer made is expected; automated marketing messages are not, and WhatsApp treats them differently — keep the two separate, record opt-ins, honour a “stop” instantly and automatically, and never let an automation message someone who asked not to be messaged.
Map · use it here or print it
Lead-routing automation
Seven steps a new enquiry passes through automatically, with the human ownership at each and the failure it is tested for. Build it in the CRM; test it with ten real enquiries before trusting it.
Capture
The enquiry writes into the CRM from the form, the call-tracking number, WhatsApp or the portal, with its source.
- Failure tested: a form field missing; a duplicate phone number
- Consent recorded with the enquiry
Classify
Rules read the enquiry: service, territory, budget band, urgency words, existing customer.
- Exception: unclassifiable → the queue owner, not a default salesperson
- Existing customer → their account owner, not the round-robin
Assign
To one person, by territory or by rotation among those available, within a minute.
- Availability from the calendar and a simple on/off flag
- Failure tested: nobody available → the manager, with an alert
Notify
The assignee gets the enquiry on their phone; the enquirer gets an acknowledgement saying who will call and when.
- The acknowledgement is honest about hours
- Failure tested: notification not read in 10 minutes → reassign or escalate
Task and sequence
The first-call task is created with the deadline; the follow-up sequence is scheduled but pauses the moment a human logs contact.
- Messages in the sequence are useful and say how to stop
- A human owns the lead throughout; the automation carries the calendar
Escalate
No first attempt logged by the standard → manager; still nothing an hour later → owner.
- Escalation is visible on the dashboard, by person
- Failure tested: the escalation itself failing silently
Audit
Weekly: every enquiry traced from capture to outcome; any that fell through become a rule change.
- Ten random enquiries a week traced by hand
- Consent honoured: an opt-out stops every message across every sequence
Free to print and share with your team.
Mistakes, measures, and what good automation does
The mistakes: automating the messages before the assignment; sequences that ignore replies; no default owner, so unmatched enquiries vanish; round-robin to people on leave; a template that reads as automated; no daily exception report; and building ten automations at once so nobody knows which one misfired. A safeguard: send an enquiry to your own business under another name once a month and watch what the automations do with it.
Measure by time to assignment, time to first contact, follow-ups completed per lead, escalations, and — the outcome — conversion of enquiries to qualified opportunities against the baseline. Good automation makes every enquiry owned within minutes, reminds the owner until the buyer has answered, and never sends a message a person did not choose to send. This is the workflow automation we set up in an SME’s CRM — the routing rules and exceptions, the task and message triggers, the escalation and daily exception report, the tests, and the consent rules — one automation at a time, each tested before the next. The free audit starts with the enquiry we send you.
Questions owners ask
What should be automated first?
Assignment: every enquiry to a named person within minutes, with a task and a notification. Then the reminders. Then, carefully, message templates the person personalises. The conversation itself is never automated.
Should follow-up messages be sent automatically?
Drafted and scheduled automatically, sent by a person after a personal first line, and paused the moment the buyer replies. A fully automatic sequence is the message buyers ignore.
What happens to enquiries outside business hours?
An immediate acknowledgement with a real callback time, and assignment to the first available person in the morning. Urgent enquiries, if your trade has them, go to the owner’s phone regardless.
How do we handle a salesperson on leave?
An availability flag they set, and a daily report of unassigned or untouched enquiries to the manager so that a forgotten flag costs an hour rather than a week.
Is this allowed under India’s data-protection rules?
Following up an enquiry the person made is expected. Marketing messages need consent, recorded, with an instant stop. Keep the two flows separate and the automation never crosses the line.
What does GullySales do?
The routing rules and exceptions, the task and message triggers with human ownership, escalation and the daily exception report, testing with real enquiries, the consent rules, and a monthly audit — built one automation at a time in your CRM. Scoped in the free audit and priced in writing.