Automation Pitfalls: Finding the Balance That Works

Mark, a consultant at a mid-sized firm specializing in customizing the global SalesPulse CRM, recently overheard a conversation between his colleagues and a new client. The client was requesting extensive automation—email notifications for expirations, renewals, and other key updates.

One of Mark’s experienced colleagues, familiar with similar business processes, offered an insightful perspective: not all automation is helpful.

Instead of relying solely on notifications, many of the client’s needs could be addressed through a well-structured report with the right filters. This would prompt users to engage more actively with the CRM, offering a broader and more strategic view of relevant data—without overwhelming them with isolated alerts.

This discussion triggered Mark’s memory of a past project where a CRM system was designed to notify users at every stage of an incoming request and offer process. The workflow included:

1. Incoming request
2. Initial cold email
3. Response received:
   Positive path: Transition to warm emails → client engagement → follow-up 1 week before the offer due date → check-in on the due date.
   Negative path: Warm farewell.
   No response: Cold farewell after multiple attempts.

While the process itself seemed reasonable, the automation led to an overwhelming number of notifications. Each request triggered up to 11-12 notifications, and with 7-10 new requests per week, the sheer volume of alerts cluttered the system.

What initially seemed like a helpful feature—a simple bell notification with a red icon—became a constant distraction for users.

Luckily, Mark’s experience helped him recognize the issue early on.

With a simple logic tweak, he introduced a setting that allowed users to disable non-essential notifications.

Once implemented, the change made a big difference—reducing clutter and boosting productivity.

Agents using the CRM were noticeably happier. They could finally focus on what mattered, without being interrupted by constant, irrelevant alerts.

Not all automation is necessary. Before implementing notifications, assess whether a well-designed report could provide the same value.

Think about scalability. What works for a small volume of requests might become unmanageable at scale.

User experience matters. Too many notifications can lead to frustration rather than efficiency.

Always review and refine processes. Just because something made sense initially doesn’t mean it remains effective as usage evolves.

Automation is a powerful tool, but when overused, it can create more problems than it solves. By questioning assumptions and refining processes, businesses can strike the right balance between helpful automation and usability.