Customer Experience Mapping in CRM Projects: Identifying Touchpoints

Sales managers at mid-sized Turkish companies often tell a familiar story: a prospect was contacted, a proposal was sent, and then nothing. Nobody knows why the customer went elsewhere. The information existed in someone’s head, but it never made it into a system. Mapping the customer experience is the technique that makes these invisible gaps visible — and it is the foundation of any serious CRM project.

A customer experience map is a structured representation of every stage a customer passes through, from first becoming aware of your business to making a purchase and continuing the relationship afterward. The core idea is straightforward: a customer does not interact with you only at the moment of sale. They see a product brochure, visit your website, receive an e-mail, speak with a sales representative on the phone, place an order, receive a delivery, and perhaps come back with a complaint. Each of these is a touchpoint, and at each one the customer forms an impression of your business — positive, neutral, or negative.

Building the map starts with segmenting your customers. A corporate buyer and a retail customer move through different stages and make decisions differently; within the same segment, purchasing frequency and product category can introduce further variation. A practical starting point is a working session with your sales team. An experienced sales representative can walk you through the customer’s decision process step by step, and writing that account down becomes the first draft of your map. Customer complaint records, return requests, and repeat purchase data are then layered onto that draft to fill in what the sales team may not see.

For each touchpoint, three questions need answers: what is the customer doing at this stage, what are they feeling, and what do they expect? When you send an order confirmation e-mail, the customer wants to know the delivery date — if that information is missing, the expectation is unmet. When a complaint comes in, the customer wants a resolution, not an apology. Answering these questions systematically shows which touchpoints are creating dissatisfaction and which are working well. Completing this analysis before configuring your CRM system is not optional; it directly determines which data fields, workflow stages, and follow-up triggers the system needs to support.

Digital channels have become increasingly prominent touchpoints. E-mail is now the primary channel for both individual and corporate customer communication — pre-sale enquiries, proposals, order confirmations, and after-sales support all flow through it. The company website has become a critical awareness-stage touchpoint; customers increasingly look online before making contact. Mapping these two channels tells you what the CRM system should capture automatically: which e-mails were sent, which web enquiry forms were submitted, and when. Phone calls and face-to-face meetings remain the highest-stakes touchpoints, typically concentrated at the negotiation and decision stages of the map.

The most common difficulty in practice is that sales and customer service teams tend to see the mapping exercise as paperwork rather than useful work. The map is usually built by a project coordinator or CRM consultant, but the real knowledge sits with the people in the field. Leaving those teams out of the process produces a map that looks complete on paper but misses what actually happens. A second challenge is scope: when a map identifies fifteen or twenty touchpoints, trying to improve all of them at once leads nowhere. Focusing on the two or three points where customer loss is most concentrated produces far better results than spreading effort thin.

For a small or mid-sized business owner considering this kind of work, the practical starting criterion is your existing data. How many customers placed a second order, and how many did not? Do you have complaint records, or do complaints disappear without being logged? If you cannot answer these questions, the mapping exercise will show you both where your process breaks down and exactly what data your CRM system needs to capture. Finishing the map before selecting or configuring a CRM system consistently reduces the cost of customisation later — and more importantly, it increases the chance that the system will actually be used.

This article was originally written in Turkish by Gökhan MERCANOĞLU on April 16, 2007 and has been automatically translated into English and other languages using machine translation.


churn risk is not merely a technical choice; it reflects how the organization makes decisions. When process, data, and ownership are unclear, investment creates speed in the short term and complexity in the long term. Real value begins when technology is connected to a business outcome.


Gökhan Mercanoğlu
CRM ve Müşteri Yönetimi