Notes for owners · CRM, automation and RevOps
What should and should not be automated in sales?
Automate the recording, the routing and the reminders, and keep the qualifying question, the price conversation and the loss reason with a person.
The GullySales team · Updated 15 Sept 2026 · 6 min read
On this page
Automate the mechanical parts: capturing the enquiry, routing it to the right person, alerting them in seconds, creating the follow-up tasks, sending acknowledgements and documents, and producing the weekly report. Keep the human parts human: the qualifying question, the price conversation, the objection, the negotiation and the decision to call a deal lost. The test is simple. If the step needs judgement about a person, do not automate it. If it needs memory or typing, automate it.
Automate these, in this order
| What | Why it pays | What good looks like |
|---|---|---|
| Enquiry capture from every channel | Nothing else works on enquiries you cannot see | Website, calls, WhatsApp, IndiaMART and the Google profile land in one record with the source stamped |
| Assignment to an owner | Ends the shared-inbox lottery | A written routing rule by product, city and language, with a backup owner |
| Alerts within seconds | Reply time is the biggest single lever | The owner's phone buzzes with the name, number and requirement |
| Dated follow-up tasks | People forget the fourth attempt, not the first | Six tasks created when the lead is created, across a month |
| Acknowledgement to the buyer | Stops them calling a competitor while waiting | One short message from a named person, not a template essay |
| Sending the quotation, catalogue or drawing | Removes an hour of typing a day | Generated from the CRM, sent after a person approves it |
| Escalation on inactivity | Makes neglect visible instead of silent | Seven days with no activity and it moves to a supervisor's queue |
| The weekly management report | Ends the argument about whose numbers are right | Built from the CRM, same definitions every week |
| Renewal, AMC and recall reminders | This is revenue you already own | A task sixty days before expiry with last year's history attached |
| Data hygiene checks | Bad data is what kills CRM trust | Duplicate alerts and missing-field flags, weekly |
Do not automate these
The qualifying conversation. A form can collect a budget range. It cannot hear that the buyer is asking about capacity because a second line is being sanctioned next quarter. That sentence is worth more than the whole form.
Price and negotiation. Automated discounting trains buyers to wait, and a price sent without a conversation removes your only chance to explain what is in it.
Objection handling. The buyer who says the price is high may mean three different things. Only a person can find out which.
Lost reasons. A system that automatically marks leads lost after thirty days destroys the most useful data you have. Someone should write the reason in their own words.
The relationship messages. A festival greeting sent by a machine to two thousand contacts with the wrong first name is worse than silence. So is a birthday message to a customer whose order you delivered late last week.
Judgement about who to chase. Lead scoring is a useful hint and a poor decision maker. A score cannot know that the smaller enquiry came from a plant that is about to expand.
The hidden costs of over-automation
Three appear reliably.
Messages that read like a machine. Indian buyers notice immediately, and a templated message with a placeholder still showing loses trust that a phone call cannot recover.
Activity theatre. When the system creates tasks and the team closes them without doing the work, you get a dashboard full of completed activity and a flat conversion rate. This is the most common failure and it looks like success for about two quarters.
Too many steps. Every automated step is a thing that can break, and nobody in a small business is checking. A rule pointing at a salesperson who left six months ago will quietly send enquiries nowhere.
What does this look like in practice?
For example, a commercial laundry equipment supplier in Bengaluru selling to hotels, hospitals and hostels across Karnataka. The details and figures below are illustrative. It had bought a CRM and configured a great deal: automated email sequences of seven messages, lead scoring, and an automatic loss rule after forty-five days.
The reporting looked healthy and orders were not moving. Two problems were visible in the records. Hotel purchase managers were receiving a seven-part email sequence while a salesperson was also calling them. The first thing several of them said on a call was that they were getting too many messages. And the automatic loss rule was closing deals with hospitals whose tender cycles ran longer than forty-five days. A genuine pipeline worth an illustrative ₹60 lakh had been marked lost without anyone speaking to the customer.
The fix removed more than it added. The email sequence was cut to two messages, an acknowledgement and a document. The automatic loss rule was replaced with a task asking the salesperson to record a reason. Lead scoring was switched off, and a weekly list of untouched leads replaced it. The owner could believe the pipeline number again.
A test you can apply to any step
Ask three questions before automating anything.
Does this step need to know something about a person that is not written down? If yes, keep it human.
If this runs wrongly two hundred times, what is the damage? A wrongly routed alert is recoverable. Two hundred wrong messages to your customer list is not.
Who will notice when it breaks? If the answer is nobody, do not build it.
What to do next
List every automated step running in your sales process today and, beside each, write what happens if it fails and who would notice. Switch off anything that fails that test. Then check the two that matter most, whether every enquiry lands in one record with its source, and whether the owner is alerted within a minute. Automate those two first, and only add another automated step once you know who is watching it.
