Insights

/

8 Nov 2026 · 5 min read

Teardown

Teams ignore a system that asks them to type

A new system gets ignored when it asks for typing it could do itself. Let calls, texts and bookings log themselves. Then ask for one line.

Teams ignore a system that asks them to type

The forms nobody fills in, and the one tap they will.

Look up how to get a team using a new customer system. The advice is all about people. The trade calls it CRM adoption. The tips are training, prizes for the most updates, and a champion on every team. Each one treats the team as the thing to fix.

On a call in August, someone put the real problem plainly. “The big challenge that you have is guys have to use it and have to be inputting. That’s unfortunately where a lot of the sales guys stop.” When they stop, the record goes out of date. Then nobody trusts it, and you’re back to asking around.

What does the system record without anyone touching it?

Nearly everything that passes between your business and a customer, all in one place. Run the call, the text and the booking through the system. Then each one can land on the customer’s record by itself. Nobody types it.

  • Calls. Who called, when, and for how long. The recording and a written transcript can sit on the record too. Nobody takes notes on the call.
  • Messages. Texts, emails and WhatsApp, in one place, under the customer’s name.
  • Forms. What they filled in on your website, word for word.
  • Bookings. The time, and what they wrote on the booking form.
  • Quotes and invoices. When each one went out, and whether it was paid.

A tech who never types a word still leaves a full trail. The catch is the word “through.” A call from a personal phone doesn’t reach the record. Nor does a text from someone’s own WhatsApp.

Open a customer whose work ran through the system. The story is there in order. The form on Monday, the call on Tuesday, the booking for Thursday. Nobody wrote any of it.

So the first fix is the phone, not the typing. One business number the whole team uses, on the phones they already carry. Now the system hears the call, and it can write it down.

Skip that step, and you’re asking the team to copy their calls in by hand. That’s the typing everyone hates, and it’s the first thing to stop.

What is left that a person has to type?

Only what the system can’t hear. That comes down to four things, all of them short.

  • What happened. When the call ends, pick from a short list. Booked, call back, or not now.
  • What it’s worth. The rough size of the job, so you can see what’s waiting.
  • What’s next. The next step and the day. The system can remind the right person.
  • The note. One line only a person knows.

Here’s one call, start to finish:

01The call. It rings, gets answered, and lands on the customer’s record. Nobody types.
02The tap. The call ends. Pick what happened: booked, call back, or not now.
03The line. One thing only you heard: “Wants it done before the holidays.”

Example. The choices on the list are set to suit each business.

Why those four? They’re what the next person needs, and the system can’t guess them. Don’t ask the team to retype what the call already holds. Don’t ask for the address twice.

Keep it that small. Every extra box is one more reason to skip all of it. A full write-up after every call isn’t a habit. It’s a second job.

The team isn’t avoiding the system. They’re avoiding the typing.

Once the typing is that small, one rule becomes fair. If it’s not in the CRM, it’s not done.

It sounds strict. It isn’t about watching anyone. It’s how the owner stops being the one person who remembers everything. And it’s only fair once the system does the rest.

If your system already sits unused, start with a list before any training day. Write down everything the team is asked to type. Cross off what the system could catch on its own. What’s left is the ask. Is it more than a tap and a line per call? Then the list is the problem, not the team.

What does the team get back for typing it?

Fewer questions. When the record is right, nobody has to ask them what happened. And they don’t have to ask each other.

The owner stops calling around on a Monday. The office can see a job is booked without calling the tech. When someone’s off sick, the next person opens the record and carries on.

The tech gets something too. No more calls on a Saturday about a job from last week. The answer is on the record, so nobody needs to ask.

On that call in August, we showed a report that arrives each morning. It lists yesterday’s calls and how each one ended. Nobody put it together by hand. It came from the taps. The team sees their own day, counted for them. That’s the reason to tap.

Targets and pay can come from the same record. Then they’re counted, not argued. That’s how a business ends up with one answer everyone trusts, instead of three.

Here’s how that can work in Income Mavericks:

  • Everything in one place. Calls, texts, emails, forms, bookings and payments can sit on one customer record.
  • The call. In the app, a call can land on the record, with its recording and a written transcript.
  • The tap. Your own list of outcomes can pop up when the call ends.
  • The next step. Each pick can send a text or make a follow-up task.
  • The morning report. Yesterday’s calls and how each one ended can reach your inbox.

A keener team won’t fix this. A system that writes down what it can, and asks for one line, will. People use the thing that saves them typing.

More on this topic

Operations

10 Nov 2026 · 4 min read · 4 min

Explainer

Five apps, and nobody knows which one is right

Each app does its job. The trouble is the gaps between them, where someone copies things across and messages wait to be seen. Keep each customer in one place.

→

Operations

2 Nov 2026 · 4 min read · 4 min

Explainer

Manual data entry costs more than the typing

The typing only takes minutes. The real cost is the wrong detail on the bill, and the customer waiting while it sits in an inbox. Type it once.

→

Operations

27 Oct 2026 · 3 min read · 3 min

Explainer

How to write an estimate customers say yes to

Say what you'll do, what it costs, and what it leaves out. Add the date the price holds until and one way to say yes. Then send it the day you see the job.

→

Rather talk than read

Bring us the process that keeps going wrong

Tell us what is breaking and we will tell you what it would take to stop it.

Get in touch