Why a CRM does not fix client context, even when everyone fills it in.

Job posts for care coordinators and case managers tend to mention the CRM somewhere in the middle of the duties. It sits on the same line as WhatsApp, email, phone, SMS and the spreadsheets, as one more place the new hire will have to look. The duties themselves say things like "maintain records of" and "follow up across", and the CRM in that list is one the company already pays for.

So the company is paying twice. The CRM was bought so each client would live in one place, and the coordinator is being hired because the client does not.

The usual fix is discipline. If everyone filled the CRM in properly, the thinking goes, the reassembly would stop. So a field becomes compulsory and a manager starts reading the notes on Friday afternoons. For a few weeks the records look very complete, and the coordinator still starts every morning in the WhatsApp search bar.

What a filled in CRM holds

A CRM holds what a person typed into it, after the fact, in the words they had time for. Often those words are accurate. They are still a summary of a conversation, written by somebody on their way to the next one, and the conversation stays wherever it happened, along with the email nobody thought to log.

Say a client messages your account lead on WhatsApp on a Tuesday to say the start date has to move. On Thursday an email arrives with a different date in it, and on Friday the client rings to say which one they meant. A careful account lead types "start date moved, confirmed by phone" into the CRM, and every word of it is true. The coordinator who picks the client up next week still does not know which date. That means scrolling the WhatsApp thread and the email, and then messaging the account lead to ask what was said on the call. All the CRM note did was tell them there was something to look for.

The other problem is age. A CRM note carries the day somebody typed it, which is rarely the day the thing became true, and nothing on it says whether it still is. The case study for Brain, the planning system OCTYN runs its own portfolio on, has a name for this failure. It calls it a stale recall, a fact that was true in July and comes back in September with no sense of its age, and says that is worse than no memory at all. A well kept CRM is full of notes that could fail this way, and they all sound equally sure of themselves.

Why the coordinator checks anyway

A coordinator who has been caught out once by an old note stops trusting notes. That habit explains how a company ends up with a complete CRM and a person rebuilding clients by hand at the same time. The note gets read, then checked against the thread, and the checking turns out to be most of the job.

OCTYN's own description of the problem is the same client rebuilt by hand from WhatsApp, email, phone, a CRM and a spreadsheet, before every next action. The CRM is one of five sources in that sentence. More compulsory fields make it a longer one to read, and leave the other four exactly where they were.

The details that change the next conversation are also the ones least likely to reach the CRM. Say the client mentions in a voice note that their finance person is away until the fifteenth. Nobody types that in, because on the day it sounded like small talk, and it is the reason the invoice sits unpaid for two weeks.

One record the channels write into

The fix takes the typing out of the middle. Every channel writes into one record per client as the messages arrive, and each fact in the record points back to the message or email it came from, with the date it came in. A phone call still needs somebody to write a note, and that note lands in the same record with its own date, next to the messages it was about. When the coordinator reads that the start date is the twenty first, one click shows where the client said so.

OCTYN runs its own client work this way, on Agency Ops. WhatsApp, email, Telegram and direct messages land in one conversation record and are sorted as they arrive. The client pipeline sits on the same data, so where a client stands and what they last said are one lookup. As of 6 July 2026 that meant four channels in one conversation store. There is more in the case study.

The tracing is the part to insist on. A summary on top of the record is handy, and sometimes it will be wrong. When it is, the line under it saying WhatsApp, Tuesday lets the coordinator settle the question in a few seconds, instead of deciding the whole page cannot be trusted and going back to the search bar. Brain made the same call: its case study says that being able to trace a fact to its source mattered more than how well it recalled. A Company Brain is built on that choice, and shows where every answer came from.

None of this means throwing out the CRM. If its reports are useful, keep them. What changes is where the coordinator starts in the morning, and the hours that went on reassembly go back to the part of the job that needed a person, which is the client. There is more on this problem under client context.

The Friday notes can carry on as well. They will just have something to be checked against now.