How to stop rebuilding client context before every call

The call is at eleven. At ten fifty the coordinator opens WhatsApp and scrolls up past a voice note, two photos and a thumbs up to find what the client said on Thursday. The useful email turns out to be buried under a subject line from three threads ago. The CRM knows the client's phone number and not much else. By eleven the picture is mostly back together, and the call opens with the most expensive sentence in client work, which is some version of "remind me where we left things".

Nobody designed it this way. It grew one client at a time, and for a while it worked, because the person doing the reassembly also remembered most of it. Then the client list doubled, or that person went on holiday, and the business discovered that its real system of record was one coordinator's short term memory.

Where the context actually lives

Most businesses that run on repeated contact with the same people end up with the story in several places at once. The conversation sits in WhatsApp and email, whatever got decided is in somebody's notes if anyone took them, and the promise made on last week's call was probably never written down.

A CRM looks like the answer and rarely is. It stores what someone remembered to type into it, which tends to be the phone number, the stage of the deal and a note written on Friday afternoon from memory. The detail that would actually change the next conversation, like the fact that the client already tried the obvious fix and hated it, sits in a chat thread the CRM has never seen.

So before every next action, somebody rebuilds it by hand. Businesses with this shape often end up hiring for it without quite saying so. Read a few coordinator job posts and the responsibilities are the tell: keep records of every interaction, follow up across channels, summarise for the team. That is a description of reassembly, written out as a salary.

One record, written as things happen

The fix is a single record per client that every channel writes into at the moment something happens, instead of hours later, whenever someone remembers. When a message arrives on WhatsApp or a call note is saved, a small notice goes to the record, usually through a webhook, and the record files it with the date and where it came from. Nobody has to copy anything across.

The summary on top of that record matters less than the source line under each part of it. A summary that says the client prefers mornings is useful. One that says so and links to the message where they said it is something a coordinator can trust before a call, because checking it takes a single click instead of another scroll through WhatsApp.

We run a version of this on ourselves. OCTYN's own planning layer, Brain, keeps the state of more than twenty codebases, and the failure it is built hardest against is the confident answer that quietly blends two projects into one. The same risk applies to clients. An answer that mixes up two clients reads perfectly well and is worse than having no answer, so each record belongs to exactly one client and every line in it points back to where it came from. That is most of what a Company Brain is, applied to a client list.

What it gives back, in hours

The arithmetic uses three numbers from your own week. Take the number of clients, multiply by the touchpoints each one gets in a week, and multiply again by the minutes someone spends rebuilding context before each touchpoint. Say forty clients, three touchpoints a week each, and eight minutes of scrolling before every one of them. That comes to sixteen hours a week, which is two full working days spent finding out what the business already knew.

Those hours do not disappear when the record exists. They go back to the coordinator, and they go back to the part of the job that needed a person in the first place, which is the conversation itself. The cost model runs the same sum on your real numbers, and the figure it produces is usually the reason this gets built.

Where to start

Start with the channel where most client conversation already happens, get it writing into one record per client, and leave the rest alone for a month. For a lot of service businesses that channel is WhatsApp. A new CRM is rarely the first step, and replacing one is almost never the answer, since the problem was never where the phone numbers were kept.

Not everything belongs in the record, either. The thumbs up and the voice note about running late can stay where they are. What earns a line is anything that would change how the next conversation goes, like a date that moved or a promise somebody made on the phone.

Once the first channel lands cleanly, email and call notes follow the same path. The coordinator's morning changes before anything else does. The call at eleven starts at eleven.