Drafts beside the CRM

An operations team of about a dozen already kept status in the CRM. When a customer asked where something stood, a person opened the record, copied four fields, and wrote an email from a blank page. They did this several times a day. The facts were fine. The blank page was the cost.

The project was a draft that read the fields already on the record. The assistant used the fields the team already treated as current and proposed a short note in a voice they had specified. A person edited it and sent it. If a field the draft needed was empty, the draft said so and stopped, instead of filling the gap with a plausible sentence.

Nothing in the setup was allowed to email the customer, change the record, or become the place people checked first. The CRM stayed the system of record. The team kept a simple log of what had been suggested, enough to see whether the draft was helping or wandering.

The blank page went away. The task got shorter. A precise percentage is not reported here, because this example is a composite and that number would be fiction.

If the fields had been wrong, the project would have stopped and gone back to the CRM. A fluent draft on a bad record leaves the record worse. The AI consulting practice keeps the existing system as the place the facts live.