In this article
- Readiness: the process has to exist first
- 1–4: separate repeatable administration from judgement and trust
- 5–8: assess risk, volume, variability and customer impact
- 9–12: design human checkpoints, exceptions and monitoring
- Sales-automation decision matrix
- Mistakes, and what the right balance feels like
- Questions owners ask
Readiness: the process has to exist first
Automation applies rules. If the sales process is not written — stages, criteria, standards, handovers — there are no rules to apply, and the automation will encode whatever the person configuring it assumed. Write the process. Then list every task in it, from enquiry to renewal, with who does it now, how often, and how long it takes. That list is what the checklist runs over.
Decide the owner of automation — the CRM champion or the RevOps person — who builds one automation at a time, tests it, and switches it off when it misbehaves.
1–4: separate repeatable administration from judgement and trust
1. Automate the routing: every enquiry assigned to a named person by rule, within minutes, with a task and a notification — no judgement needed, high volume, cheap to get wrong and easy to fix. 2. Automate the reminders: follow-up tasks scheduled by stage, escalations when they are missed, stale-deal flags, renewal dates — the memory work that people are bad at and machines are made for. 3. Automate the data entry where the data already exists: the website form writing in, WhatsApp and email logged, calls captured, the quote generated from the deal, the invoice from the order — double entry is where CRMs die. 4. Automate the reporting: the weekly pipeline page, the funnel by source, the adoption numbers — produced by the system on Monday morning, read by a person.
None of these four touches the customer’s experience of being sold to. All of them are where enquiries and follow-ups are lost by hand.
5–8: assess risk, volume, variability and customer impact
For every other task, four questions. 5. Risk: what happens if the automation gets it wrong — a misrouted enquiry is fixed in an hour; a wrong price sent to a customer is a lost deal or a lost margin; a message to someone who asked not to be contacted is a complaint and possibly a legal problem. High risk means a human checkpoint or no automation. 6. Volume: is this done fifty times a day or five times a month? Automation earns its setup cost at volume; a monthly task is faster done by hand. 7. Variability: does the task look the same every time, or does each instance need a decision — which customer, which offer, which tone? Low variability automates; high variability is assisted at most. 8. Customer impact: does the customer experience this task — a message, a call, a proposal — or is it internal? Anything the customer experiences is, at most, drafted by software and sent by a person, because customers can tell, and because someone must be responsible for what was said.
Score each task on the four. The high-volume, low-risk, low-variability, internal tasks automate; the rest are assisted or left with people.
9–12: design human checkpoints, exceptions and monitoring
9. Checkpoints: for every assisted task, the point where a person reviews and decides — the drafted follow-up read and personalised before sending; the qualification sorted by machine and sampled by a person; the pricing suggested and approved. The checkpoint is a named person and a moment, not a hope. 10. Exceptions: every automation has a rule for what it cannot handle — the enquiry that matches no territory goes to a default owner; the reply that arrives mid-sequence pauses it and creates a task; the customer flagged “do not contact” is excluded everywhere. The default and the pause are the two exceptions most often forgotten. 11. Monitoring: a daily exception report — unassigned enquiries, untouched tasks, sequences that fired after a reply — and a monthly audit of a sample of automated actions, read by the owner of automation. 12. The off switch: every automation can be paused in a minute by the person who owns it, and is, the first time it does something a customer noticed.
The four are what let a small business run automation without a systems team. Without them, the first misfire becomes the reason automation is switched off for good.
Decision table · use it here or print it
Sales-automation decision matrix
Automate what is repeatable and low-risk; keep judgement and trust with people. Read the rows, then pick a task to see where it falls.
| Task | Automate | Human, with automation supporting | Human only | Why |
|---|---|---|---|---|
| Enquiry capture and acknowledgement | Yes | High volume, no judgement, and speed matters | ||
| Lead assignment and escalation | Yes | Rules, availability, time — a machine keeps them better | ||
| First-call reminders and task creation | Yes | The calendar, not the conversation | ||
| Qualification | Scoring and the first question | The decision | A form can sort; a person decides who gets a salesperson’s hour | |
| Follow-up messages to silent leads | Scheduled, with stop rules | Useful and consistent — but paused the moment a person is talking | ||
| Discovery and proposals | Drafting and research | The conversation and the recommendation | Trust is built by a person who listened | |
| Pricing and discounts | Rule checks and approvals routing | The exception | Money decisions need a name against them | |
| Objections and negotiation | Yes | Judgement, reading the room, and the relationship | ||
| Complaint responses | Acknowledgement and logging | The response | A templated apology makes it worse | |
| Reporting | Yes | From the CRM, weekly, unedited | ||
| Data entry after calls | Transcription and summary | Approval of the summary | Saves the hour; the salesperson owns what is recorded |
Free to print and share with your team.
Mistakes, and what the right balance feels like
The mistakes: automating the conversation; sequences that ignore replies; pricing or discount decisions left to a rule; ten automations built in a week; no default owner; no exception report; and treating a customer complaint about an automated message as a technical issue rather than a trust issue. A safeguard: enquire through your own business once a month under another name and experience the automations as a customer.
The right balance feels, to the customer, like a business that responds fast and remembers everything, and, to the team, like a system that does the administration and leaves them the selling. This is the automation assessment we do with SMEs — the task list scored on the four questions, the automations built one at a time with checkpoints and exceptions, the daily report and the monthly audit — and the free audit starts with the list of tasks your team does by hand that a machine should, and the ones a machine does that a person should.
Questions owners ask
What should never be automated in sales?
The discovery conversation, the price and discount decision, the negotiation, the complaint, and any message sent to a customer without a person reading it first. These are where trust is won or lost, and someone must be responsible.
What should be automated first?
Enquiry assignment, follow-up reminders and escalations, data entry from the website, WhatsApp and email, and the weekly report. High volume, low risk, no judgement — and the places enquiries are lost by hand.
Can AI draft our customer messages?
Draft, yes; send, no. A person reads, personalises and sends, and is responsible for it. The draft saves the typing; the review protects the relationship.
How many automations should a small business run?
As many as it can monitor: usually four to eight, built one at a time, each with a default, a pause rule and an exception report. Ten built in a week is how automation gets switched off.
How do we know an automation is misbehaving?
The daily exception report — unassigned, untouched, fired-after-reply — and a monthly sample read by the owner of automation. And the monthly enquiry you send yourself under another name.
What does GullySales do?
The task inventory scored on risk, volume, variability and customer impact, the automations built one at a time in your CRM with checkpoints, exceptions and the daily report, and a monthly audit for the first quarter. Scoped in the free audit and priced in writing.