Skip to content
Codivine
Automation

CRM Automation Explained: What’s Worth Automating and What Isn’t

Which parts of a CRM should run themselves — capture, deduplication, assignment, follow-up, reporting — and which automations quietly damage relationships.

Marta Szymczak3 min read

Most CRM automation projects start at the wrong end. They begin with sequences and scoring, when the actual problem is that the data in the CRM is incomplete, duplicated and three days old.

Fix the input first. Everything downstream gets better for free.

Layer one: capture (do this first)

Every lead source lands in the CRM automatically. Website forms, phone calls, the shared inbox, ads, marketplaces, referrals. If any source requires manual entry, that source has worse data and slower response — and you’ll draw the wrong conclusions about which channels work.

Deduplicate on arrival. Match on email and phone. A returning enquirer should attach to their existing record with history intact, not create a second one. Duplicate contacts are the fastest way to make a CRM untrusted.

Capture the source properly. Not just "website" — which page, which campaign, which search. Without this, marketing attribution is guesswork.

Acknowledge immediately. An automatic reply that confirms receipt and says when a human will respond. This single automation reduces "did you get my message?" emails to nearly zero.

Layer two: routing

Assign by rule. Territory, service type, workload, language — whatever fits. The rule matters less than the fact that there is one and it runs in seconds.

Escalate on silence. If a new lead hasn’t been contacted within a defined window, tell someone. This is the automation with the clearest revenue impact of anything on this list, because speed of first response is consistently one of the strongest predictors of conversion.

Round-robin with a fallback. If someone’s out, work reassigns. Leads that sit in an away colleague’s queue are the most avoidable loss there is.

Layer three: keeping records honest

Auto-fill what you can derive. Company from email domain, location from phone prefix, industry from a data source you already pay for. Every field a salesperson doesn’t have to type is a field that’s more likely to be correct.

Log activity automatically. Emails and calls attached to records without anyone remembering. Manual activity logging is the first thing to lapse under pressure.

Nudge on incomplete records. A deal can’t move to "proposal sent" without a value. Gentle enforcement beats a quarterly data clean-up.

Layer four: follow-up

Sequences for the not-yet-ready. Most enquiries aren’t ready today. A light, useful sequence keeps you present without pestering. Detailed approach in how to automate lead follow-up.

Alerts on re-engagement. Someone who went quiet opens a proposal again, or revisits the pricing page. That’s a signal worth acting on within the hour.

Automatic re-activation. Closed-lost deals return to a nurture track after a defined period. Circumstances change; budgets reset.

Layer five: reporting

Pipeline reporting that doesn’t need assembling. If your weekly numbers require someone to export and reconcile, either the CRM isn’t the source of truth or the fields aren’t being filled in. Both are fixable, and both are more valuable than another dashboard.

Alerts on the shape of the pipeline, not just its size: deals stuck at one stage, an unusual number of losses at a specific point, response times drifting.

What not to automate

Anything that pretends to be personal but isn’t. "I was just thinking about you" sent by a robot at 09:00 to 400 people. Recipients can tell, and it costs you more credibility than the email is worth.

Aggressive multi-channel sequences. Email, then SMS, then LinkedIn, then a call, over four days, to someone who downloaded one thing. This generates unsubscribes and reputation damage.

Lead scoring you can’t explain. If nobody can say why a lead is an 87, the score is decoration. Start with two or three explicit criteria you can defend.

The actual conversation. The point of all this is to get a well-informed human into a well-timed conversation. Automation that tries to replace that stage is optimising for the wrong outcome.

A sensible first project

  1. Every source into the CRM, deduplicated.
  2. Automatic acknowledgement.
  3. Assignment by rule.
  4. Escalation if nobody responds within your target window.
  5. One measurement: median time to first human response.

That’s typically a couple of weeks of work, and it’s the version of CRM automation with the clearest link to revenue.

If you’d like it built on top of the CRM you already use rather than replacing it, that’s usually what we recommend — see business automation and integrations.

Marta Szymczak

Sales & Key Account Manager

Your point of contact for everything commercial — scope, communication and making sure the project matches what the business actually needs.

More about the team

Want help with this?

This is the kind of work we do. These pages explain how.

Got a version of this problem?

Describe it in your own words. We'll tell you what we'd do about it — and whether it's worth doing at all.

No specification needed. A description of the problem is enough to start.