Topics

Knowledge Creation Laboratory by CRM(xRM)

"Eliminating the Personalization of Sales" — A Complete Guide to Creating a System with EMOROCO CRM Lite Where Customer Relationships Continue Even When the Salesperson Changes

Hello, this is Matsubara, CRM Evangelist.

"Since Mr. Tanaka left, our business with company XX has been cut in half."

How many companies have come to realize the dangers of over-reliance on individual expertise with just this one statement?

Personalization refers to a situation where "only a specific person knows customer information, relationship context, and follow-up timing." Every time that person leaves or transfers, that information disappears from the organization.

However, many companies view this as an "individual problem." "I wish they had done a better job with the handover"—but that's not the real issue. Personalization is not an individual problem; it's a systemic problem.

A "culture of striving for smooth handovers" will not eliminate reliance on individual expertise. The only way to fundamentally resolve this is to create a system where customer relationships continue even without handovers.

This article outlines the inherent risks of over-reliance on specific individuals and provides a complete guide on how to build a system with EMOROCO CRM Lite that ensures relationships continue even when the person in charge changes.


The "Three Essential Risks" of Personalization

Risk ① "Instant evaporation of relationship assets"

Long-term relationships with customers—trust, context, emotional evolution, and shared challenges—are "relational assets" that reside in the memories of the person in charge. These assets disappear from the organization the moment that person leaves.

"President Tanaka of Company A experiences a drop in emotional temperature every October," "Company B is facing competition from Company X, but their representative trusts us," "Company C is considering a major investment for its 30th anniversary next year"—these are all relationship assets that exist only in the minds of the people in charge.

Risk ②: "Skills becoming a black box"

"Why was Mr. Tanaka able to build such a deep relationship with company XX?" — This is something the organization doesn't understand. The know-how of a high-performing employee—"how he built good relationships with customers"—is treated as individual talent and not translated into organizational learning. His successor has to start from scratch through trial and error.

Risk ③: "Repeated handover costs"

Each time the person in charge changes, costs are incurred for "creating handover documents, providing explanations, accompanying visits, and rebuilding relationships." In large companies, dozens to hundreds of personnel changes occur every year, and this accumulation leads to a "chronic deterioration of customer relationships" throughout the organization.


Why can't this be resolved through a "handover culture"?

[Three structural limitations of the "handover culture"]

Limitation ①: The person taking over doesn't know what's important.
The person in charge has been accumulating information that they consider to be "common sense,"
It cannot be identified as "important information that should be handed over."
"October is a busy month for company XX." "The president of company YY prefers visits to phone calls."
These things are so obvious that they aren't included in the handover documents.

Limitation #2: The handover takes place "just before retirement."
In most cases, the handover process begins after the decision to resign or transfer has been made.
At this point, the person in charge's memory was fading.
Under time pressure, only the "minimum information" remains.

Limitation #3: The successor who takes over the knowledge "cannot read it or use it."
Even if handover documents exist, the "context of the relationship with this customer"
Successors who haven't experienced it firsthand will only understand half of what it means.
Ultimately, it comes down to "rebuilding the relationship from scratch."

The essential answer to eliminating reliance on specific individuals lies not in "working hard on the handover," but in "a system where relationship information is naturally recorded, accumulated, and passed on within the course of daily work."


Five design features to eliminate reliance on individual expertise, built with EMOROCO CRM Lite.

Design ① "Narrative Memo Field" - Externalizing the thoughts in the mind of the person in charge.

[Designing a Narrative Memo Field]

Field name: " 담당자
Format: Multi-line text (added chronologically)
Update rule: Record within 30 minutes of contact.

Answers to the four questions to record:
① What is the most important thing the next person in charge needs to know from what we discussed today?
② What were the customer's emotions, state of mind, and overall atmosphere?
③ What words resonated with you today, and what words didn't?
④ What hooks (topics/suggestions) can be used next time?

[Standards for the quality of records]

high quality:
"The president places great importance on the company's 30th anniversary."
The phrase "giving back to the community" came up. Next time...
A framework for proposals that contribute to the local community is highly likely to resonate.
His expression hardened when the name of competitor X was mentioned—this is a cause for concern."

Low quality:
"I visited and spoke with them. I got a positive impression."
→ This record shows that the successor "doesn't know anything."

Design ② "Emotional Temperature Field" - Visualizing changes in relationships over time.

[Designing emotional temperature and its use when responsibilities change]

Field: Selectable (Hot / Warm / Cool / Cold)
Update rule: Update after each contact.

How to use this when someone is in charge:
- Check the trend in emotional temperature over the past 3 months.
- If there is a change from "warm → cool → warm"
"What happened that made him cool down, and what made him recover?"
Check the narrative memo.
→ This alone allows you to understand "the history of your relationship with this customer."

Design ③ "ICX Capture Field" - Recording information that cannot be put into words.

[ICX Capture Field Design]

"Customer values, preferences, and taboos" (text):
Example: "A manager who prioritizes feedback from the field over numbers."
"Stories based on real-world anecdotes resonate more than those based on data."
For example, "They don't react well to the term 'cost reduction'."
The phrase "strengthening relationships with customers" really caught my attention.

"Notes to be aware of when changing personnel" (text):
Example: "I had a particularly close relationship with the previous person in charge."
When switching to a new person in charge, be thorough during the first two interactions.
Trying to rush the sale carries the risk of customers leaving the sale."

"A hook that only this customer will understand" (text):
For example, "My hobby is fishing. I start by talking about fishing for the first five minutes."
It warms up the atmosphere. However, be careful, as you'll be seen through if you're not knowledgeable about the subject."

These are things that are "obvious" to the previous person in charge and are not written in the handover documents. However, by defining them as "things that need to be updated every time" as fields in the CRM, records are naturally accumulated.


Design ④ "Person in Charge Change Protocol" - Standardize the handover process into a "30-minute session".

[Standard protocol for changing personnel (30 minutes)]

Part 1 (10 minutes): Read the CRM together with your predecessor.
Narrative memos, emotional temperature, and ICX capture
The previous person in charge added a supplementary explanation, saying, "The background to this record is..."
I will add those verbal supplements to the narrative memo on the spot.
→ Finally, formalize the "sense of temperature" that is not written in the records.

Part 2 (10 minutes): The new person in charge designs the "initial contact plan".
"What to say and what to ask during the first contact"
Design after reading the narrative memo.
The previous person provided feedback on whether it was "right/wrong".

Part 3 (10 minutes): Register your ABC list of important customers in EMOROCO
Classify into "A (to act this week), B (to act this month), and C (to be confirmed next month)".
Register as a workflow task

→ After this session:
The new person in charge is in a position to understand the context of all customers.
From the next day, you can contact customers as "the continuation of the story."

Design ⑤ "Monitoring Dashboard After Personnel Change" — Early detection of risk periods

The six weeks following a change in personnel represent the risk period during which relationship assets are most likely to be lost.

[Monitoring Dashboard After Personnel Change]

Display criteria: "Customers who have had a change in their assigned representative within the last 6 weeks"

Alert settings:
"More than 14 days have passed since the change × No initial contact."
→ "[Urgent] Mr./Ms. XX has not been contacted since the change in personnel - please contact them this week."

"The emotional temperature after the change has fallen to below cool."
→ "[Change Risk] Mr./Ms. XX's emotional temperature has decreased—careful follow-up is necessary."

→ "Deterioration of relationships due to changes in personnel" can be detected and intervened within two weeks.

"The ultimate solution to eliminating reliance on individual expertise"—the "continuation of the story" begins the day after the change.

[Scenes of responsibilities being changed after eliminating reliance on specific individuals]

Monday: Mr. Tanaka resigns.
Tuesday: New person in charge, Ms. Suzuki, opens EMOROCO.
- Confirm the progression of emotional temperature with Company A over the past three years.
- Understand the keywords "30th anniversary of founding" and "contributing to the local community."
- Confirm that the discussion will be framed as "strengthening relationships, not cost reduction."
- I found a memo that says, "Starting with a 5-minute fishing story will warm up the atmosphere."
Wednesday: Ms. Suzuki visits Company A
"I'm Suzuki, taking over from Tanaka. We are working towards our 30th anniversary."
I understand you were considering it. How is it going now?
Company A President: "You seem to know our company very well."
"Tanaka-kun has really taken over the responsibilities well."

→ Customer experience: "This company remembers me even when the person in charge changes."
→ Organizational outcome: Relationship assets were not lost due to changes in responsibilities.

Summary - A design checklist to eliminate reliance on individual expertise.

Field design:
□ Is the "Narrative Memo" field set?
□ Is the "Emotional Temperature" field set?
□ Is there an "ICX Capture (Values, Taboos, Hooks)" field?
□ Is there a field for "Notes on changing personnel"?

Update rules:
□ Is the rule regarding recording contact within 30 minutes shared with everyone?
□ Do you discuss "the highest quality narrative memo of the week" at your weekly meetings?
□ Is the habit of "checking the CRM before meeting with the customer" well-established?

Assignment change protocol:
□ Does a "30-minute handover session" exist as part of the process when changes are made?
□ Is a monitoring dashboard set up for the 6 weeks following the change?
□ Is an alert set for "No contact for more than 14 days since change"?

Personalization is not an "individual problem," but a "systemic problem."

When you have all four elements—narrative memos, emotional temperature tracking, ICX capture, and a personnel change protocol—you can create an organization where customer relationships continue even when the person in charge changes. To begin with today, start by writing a narrative memo for one customer.
EMOROCO CRM Lite Product Page


Related article: [Relational Information Generation Theory - How customer interactions are transformed into "organizational knowledge" in CRM 4.0]

Related article: [Assetizing Customer Relationships - How to Transform the "Depth of Invisible Relationships" into a Business Asset with EMOROCO CRM Lite]

Related article: [What is a CRM Doctor (CRM Consultant)? – The role of a specialist in establishing CRM in the CRM 4.0 era]

Person who wrote this article
Shinsuke Matsubara

Arcus Japan Representative Director / CRM Consultant
Click here for detailed profile
He has worked as a system engineer, architect, and consultant at Accenture and other companies, an evangelist at Infragistics (Microsoft MVP for Dynamics CRM (now Microsoft MVP for Business Solutions)), and a solutions specialist at Microsoft (in charge of Dynamics CRM products).He currently leads a service team specializing in CRM, supporting CRM implementation and business launches for companies of all sizes.At the same time, he works as a CRM evangelist, spreading the idea of "true" CRM through events and article contributions.
Having learned CRM at Accenture, and having advocated and globally popularized CRM 2.0 (platform-based CRM) at Microsoft, he is a legitimate successor to CRM and the longest-serving active CRM expert (CRM consultant/CRM doctor), having received an award at Worldwide.
Since then, as a leading expert in CRM who advocates CRM 3.0 (Personalized CRM) and CRM 4.0 (Creative CRM), he has been interviewed and received numerous awards both domestically and internationally from publications such as The Wall Street Journal, Newsweek, TIME, WORLDCOM, Mainichi Shimbun (Weekly Economist), and Nippon Cultural Broadcasting. He has also been selected as a representative company of the Kansai business community by "Keizaikai" for four consecutive years.
book:Versatylist - How to become a "1 in 1" talent by age 35

Interview article
For requests for interviews, lectures, etc., please contact us using the contact information below.
TEL +06-6195-7501-XNUMX
Inquiry via form

Articles in the same category