CRM
Stop keeping notes in someone's head
If the only person who knows the customer is on leave, you do not have a CRM. You have a bottleneck. Write the few facts that would stop a colleague sounding new.
6 min read
Verbal handover feels fast. It does not scale past one busy week. The test is simple: can someone else ring the customer tomorrow, with the access code, the person not to call, and the promise you made on Thursday?
If the answer is no, the knowledge is not in the business. It is in a head, and heads take holidays.
Verbal handover feels fast. It does not scale past one busy week. If the only person who knows the customer is on leave, you do not have a CRM. You have a bottleneck.
You do not need a biography. You need the few facts that would stop a colleague sounding new: access, who not to call, the promise you made on Thursday.
If the busiest person being sick would make you sound new, the notes are still in a head. That is the risk, not a compliment.
Write the bits that matter
Access codes, who not to call, the real decision maker, the dog, the tenant's hours. That is the stuff that lives in heads and causes mistakes. You do not need a biography. You need the facts that change how the next visit or call goes.
If you would shout it across the office before someone left for site, it belongs on the record instead.
Shared does not mean long
Two accurate lines beat an essay. The record should be easy to scan before a call. People skip notes that look like homework. They will read a short block that starts with 'side gate, don't ring the mobile after 6, decision is with Priya'.
Length is not professionalism. Accuracy is.
- ✓Preferences: how they like to be contacted, and when
- ✓Open promises: anything you said you would do
- ✓Risks or extras: access, safety, commercial sensitivities
“Our best technician was also our biggest risk, because half the customers only existed in his memory. When he was sick, we sounded brand new. We now have a rule: if it would change the visit, it goes on the customer before you drive off.”
Make it the default
If writing the note is slower than shouting across the office, the system is too heavy. Keep the fields few. Put the note where people already look when they open the customer.
Reward the habit in small ways. Thank people for notes that saved a second visit. Do not praise heroic memory. Heroic memory is the failure mode.
The leave test
Pick a customer the busiest person knows well. Ask someone else to prepare a call using only the record. If they cannot, the notes are still in a head. Fix that customer, then the next ten, then make it how you work.
If one person being away stalls customers, you do not have coverage. You have a single point of failure with a friendly face.
What stays out of the record
Gossip, irrelevant personal detail, and anything you would not want the customer to read in a dispute. Shared notes are a working file, not a diary. Be specific about the work, and careful about people.
Write the bits that would change the visit
Access codes, who not to call, the real decision maker, the dog, the tenant's hours. That is the stuff that lives in heads and causes mistakes.
If you would shout it across the office before someone left for site, it belongs on the record instead.
Two accurate lines beat an essay. People skip notes that look like homework. They will read a short block that starts with side gate, do not ring the mobile after 6, decision is with Priya.
Keep shared notes short enough to scan
Length is not professionalism. Accuracy is. Preferences, open promises, risks or extras. Not a diary of how you felt about the conversation.
If writing the note is slower than shouting across the office, the system is too heavy. Keep the fields few. Put the note where people already look when they open the customer.
Reward the habit in small ways. Thank people for notes that saved a second visit. Do not praise heroic memory. Heroic memory is the failure mode.
- ✓Preferences: how they like to be contacted, and when
- ✓Open promises: anything you said you would do
- ✓Risks or extras: access, safety, commercial sensitivities
Run the leave test
Pick a customer the busiest person knows well. Ask someone else to prepare a call using only the record. If they cannot, the notes are still in a head.
Fix that customer, then the next ten, then make it how you work. If one person being away stalls customers, you do not have coverage. You have a single point of failure with a friendly face.
The best technician can be the biggest risk when half the customers only exist in his memory. When he is sick, you sound brand new.
Leave gossip out of the working file
Gossip, irrelevant personal detail, and anything you would not want the customer to read in a dispute. Shared notes are a working file, not a diary.
Be specific about the work, and careful about people. Write the access code. Do not write a character study.
Write what you would shout across the office
Side gate. Do not ring after 6. Decision is with Priya. Those lines change the visit. They belong on the customer before anyone drives off.
You do not need a biography. You need the facts that stop a second trip.
Do not praise heroic memory
The technician who remembers every dog is also the single point of failure. Thank the note that saved a visit. Do not thank the memory that never got written down.
Heroic memory feels like culture. It is a bottleneck with a friendly face.
Foxtra is only as good as what you put on the customer. Short, shared notes beat heroic memory. Write the bits that would change the next call or visit, and treat a blank record as a risk, not a tidy page.
Short, shared notes beat heroic memory. Write the bits that would change the next call or visit, and treat a blank record as a risk, not a tidy page.
If one person being away stalls customers, the knowledge is not in the CRM yet. Write the few facts that would let a colleague ring tomorrow.
Short, shared, and safe to read in a dispute. That is a note worth having. Blank pages are not tidy. They are risk.