Why Your Team Won't Update the CRM (and the Step to Remove Instead of Reminding Them)

The sticky note and the CRM are both true

One person at a business I am working with told me their team relies on the CRM for everything. In another conversation, someone else on the team mentioned that phone messages still get written on sticky notes.

Both are true. The CRM holds whatever gets entered into it, and a call on a sticky note has not been entered yet. Until somebody copies it over, the person who needs to call that customer back may not know they are waiting.

That is the situation behind the reminder most owners end up sending. Please update the CRM. Please log your calls. When that reminder keeps coming up, I would look at what the update actually involves. Is someone recording information for the first time, or copying something they have already written down? Those are different problems, and another reminder will not necessarily solve the second one.

Recording versus copying

Recording is a judgment task. Someone has to decide what the customer wants and write it down. You cannot remove it, and you should not want to.

Copying is a transport task. The information exists; it is in the wrong place. Every copying step is a place where a message can be delayed, lost or entered differently from the original. And every copying step is a place a person will skip when they are busy, which is why the reminder keeps coming back.

When you separate the two, the fix stops being "discipline" and becomes "remove the copy."

What the fix looks like

For that business, the goal is simple. A call summary lands on the right customer's record and the callback shows up on the right person's task list, without anyone writing it twice. The team still has the conversation, reviews anything unclear, and returns the call.

Sometimes that takes AI to capture what was said: a transcript of the call, summarized into the fields the CRM expects, attached to the right contact. Sometimes it only takes connecting tools they already own: the phone system already logs the call, the CRM already has an API, and nobody had joined them. Either way, taking the message and getting it to the right person should not be two separate jobs.

This is the same pattern as the invoice workflow on our business process automation page: capture once, move it with rules, let a person review only what is unclear.

Try this: finish the sentence

Think of one recent request that had to pass from one person to another. Where was it written down? Who needed it next? What did someone have to do to get it to them?

Then finish this sentence:

When _____ happens, _____ should reach _____, without someone having to _____.

For example: "When a customer asks for a callback, the request should reach the assigned person's task list, without someone entering it in two places."

Keep it that specific. You are looking for one step you could remove, not a plan to automate the whole business.

Frequently asked questions

Why won't my team update the CRM?

Usually because the update is a copy of something they already wrote down somewhere else. People skip transport tasks when they are busy. Reminders treat it as a discipline problem; removing the double entry treats it as the design problem it is.

What is the difference between recording and copying in a workflow?

Recording is deciding what matters and writing it down the first time; it needs a person. Copying is moving information that already exists into another system; it is where messages get delayed or lost and it is the step automation should remove.

Does fixing CRM double entry require AI?

Not always. Sometimes the phone system already logs the call and the CRM already has an API, and the fix is a connection. AI is needed when the information is in speech or free text and has to be turned into the fields the CRM expects.

How do I find the step to remove?

Take one recent request that passed between two people and finish the sentence: when X happens, Y should reach Z, without someone having to W. The W is the step.

First published in The Humming Agent Brief, Shawn's twice-monthly newsletter for business owners. Subscribe there to get the next issue first.