Someone reads an article, asks a question, signs up, needs help and later returns. Each contact may happen on a different channel or with a different person on the team. Customer relationship management (CRM) is the work of making those interactions coherent and useful over time. The letters also commonly refer to the software used to support that work. A database entry can help a team remember an unresolved issue; it cannot itself create trust.
This chapter helps you design a small CRM process before choosing any product. You will learn what to record, how to hand an issue between teams, how to keep service separate from marketing permission, and how to tell whether the process actually helps people. There is a blank worksheet at the end. You can follow all the teaching in the text; the diagrams and two videos are optional.
Figure 1
Figure 1 in words: SOSTAC® asks what the organisation can promise, resource and review. RACE's Engage stage includes continuing service, while relevant context can support earlier stages too. CRM helps coordinate people, process and information across those contacts. A record supports the plan but is not the relationship itself (Smith, no date; Chaffey, no date).
The simple meaning: relationship, process, record and tool
A relationship is what a person experiences over repeated interactions. Did they receive a clear answer? Was a promise kept? Could they choose to stop receiving messages? A process is the way the organisation assigns work, gives updates and resolves problems. A record holds the information needed for that process. CRM software is one possible tool for organising records and tasks. These layers influence one another, but they are not interchangeable.
An introductory marketing textbook describes CRM as tracking, managing and analysing customer interactions, and distinguishes operational, analytical and collaborative uses (Gomez Albrecht, Green and Hoffman, 2023). Payne and Frow (2005) argue at a strategic level for a cross-functional, process-oriented approach. Their abstract identifies strategy development, value creation, multichannel integration, information management and performance assessment as connected processes. Their point helps us avoid reducing CRM to a contact list or a sales pipeline. The academic paper is a conceptual framework, not evidence that a particular software package improves every organisation's results.
The word customer in CRM does not mean that you should call everyone a paying customer. You may have an enquirer, a subscriber, an existing customer, a former customer or a person who only wants a public answer. Recording the correct status matters because the appropriate next action differs. A question in a public comment is not permission to treat someone as a sales prospect.
Figure 2
Figure 2 in words: The relationship concerns experience and kept promises; the process concerns ownership and handoffs; the record holds relevant, accurate information; software coordinates the work. Buying or building a tool addresses only the fourth layer unless the other three are designed.
A short refresher on two familiar planning lenses
SOSTAC® is a plan organised around situation, objectives, strategy, tactics, action and control. It helps ask what is happening, where you want to go, how you will get there, what you will do, who will do it and how you will review. RACE stands for Reach, Act, Convert and Engage. It is a useful digital journey lens, not a rule that each person must pass through four predictable boxes. A person can need service before a purchase, leave after one visit, or return much later (Smith, no date; Chaffey, no date).
In Chapter 23, community care focused on listening and responding in shared spaces. CRM extends the question across individual contacts and teams: how does the next person who helps know what is necessary, without demanding that someone explain the same unresolved issue again? The chapter connection is conceptual; add a verified live internal link only after both chapters are published.
1. Begin with the promise to the person
Before sketching a database, complete this sentence: “When someone contacts us about [type of need], we will help them by [specific action], through [appropriate route].” Do not promise a speed or result you cannot sustain. Decide which enquiries your team can handle, which require specialist help, and how the person will know what happens next. These choices define the process the record must support.
Consider three practical questions. First, what does the person want to achieve right now? Second, who has the authority to do the next action? Third, what information would let that person act without asking for the whole history again? You may discover that a short case summary and an owner solve the immediate problem more effectively than a complex dashboard. This is a proposed design method, not a claim that every business needs the same fields.
The promise also needs boundaries. If a person is using a support route, the team should not quietly turn that route into an advertising channel. If the organisation cannot give an answer yet, an honest acknowledgement and realistic next update can still be useful. A relationship is shaped by the experience of follow-through, including how the organisation handles a mistake.
Who is involved?
A small operation may have one person responsible for several tasks. In a larger operation, marketing, sales, service and technical teams may each see part of a contact. CRM does not require everyone to see every detail. It requires that the right person can take the right next action with the right level of information. Define roles by their responsibilities: initial responder, case owner, specialist, decision maker for a correction, and person who reviews the process.
In a business-to-business setting, an organisation and a human contact are different things. A named employee's details may still be personal information, even when the email address is used at work. The ICO notes that a business email can count as personal information if it identifies a person (ICO, no date c). Avoid treating an entire organisation as though one contact speaks for every colleague or has agreed to receive every kind of message.
2. Map contacts without forcing people through a funnel
A touchpoint is an occasion when someone encounters or contacts the organisation: a page, a form, an email, a support request, a call or a public reply. A channel is the route, such as a website or telephone. A person may change channels for a sensible reason. A public comment may be enough to explain a general rule, while an individual account issue needs a secure private route.
Draw the likely needs, rather than assuming a perfect sequence. Someone may first discover an explanation, then ask a question, then decide whether to start using a service, then seek help, and eventually return or leave. The drawing does not predict what any individual will do. It tells a team where a handoff might occur and what information would help at that point. A customer journey map from an earlier chapter is a lens for experience; CRM is the continuing operational ability to act on relevant needs.
Ask at each contact: what should be clear here? What did the person already tell us? Is it appropriate to carry that detail forward? Who owns the next action? Where can the person correct an error? If someone stops using a service, their choice and applicable retention rules matter as much as a new opportunity. Respectful service includes a way to leave.
Figure 3
Figure 3 in words: A person may discover information, ask a question, begin using a service, need help, then return or leave. At each point, their need and appropriate route can differ. These are possible contacts, not a compulsory funnel or a prediction about a real customer.
3. Design the minimum useful record
A contact record identifies how to reach someone for a stated purpose. A case or ticket describes a particular request or problem and its progress. A task names what someone on the team will do next. A marketing preference describes a person's relevant communication choice. These may appear on one software screen, but they serve different purposes and may have different rules for access and retention.
Start with the action you need to support. For a support case, that might mean an authorised contact route, a factual summary of the issue, its status, an owner and a next update date. If a field is collected only because a vendor form happens to include it, ask whether you need it. The ICO's data minimisation guidance says personal information should be adequate, relevant and limited to what is necessary for the specified purpose (ICO, no date b).
A useful record makes uncertainty visible. Separate what the person said from what the team inferred. Mark an unverified assumption as such. Avoid labels such as “difficult customer” that mix a judgement with a factual history and may unfairly shape future treatment. If an issue has been resolved, record the outcome accurately and briefly, with a route to the authorised detail where necessary. Do not copy a whole private conversation into every note merely because you can.
Figure 4
Figure 4 in words: A contact route may enable a reply; issue and status help keep work visible; owner and date support follow-through; source or channel provides context only when relevant; a separate marketing choice may be needed for marketing. Each field needs a purpose and an accuracy check. This is an illustrative field design, not a form to fill with a real person's details.
A simple structure, not a software specification
You can start by drawing four empty cards. Card one says Person or organisation, with the minimum identifier needed for the task. Card two says Contact or case, with the question and its status. Card three says Next action, with owner and date. Card four says Communication choice, with the channel and scope of a verified preference if applicable. Draw lines only where there is a genuine relationship. If one person can have several cases, do not overwrite an old case when a new question arrives.
This is a mental model for beginner planning. It does not decide a database schema, lawful basis, retention period or security design. For a real service, the information architecture must fit the organisation, its responsibilities and the relevant legal review. A shared spreadsheet can be a temporary learning exercise, but storing real personal data in an unapproved sheet is not part of this exercise.
4. Make handoffs visible and humane
A handoff happens when an issue moves from one role or channel to another. The person asking should not have to guess whether anyone received it. A good handoff includes a short factual summary, what has already been checked, what remains unanswered, a responsible role and a realistic update point. It also gives the receiving person enough context to avoid making the enquirer repeat information unnecessarily.
An initial response and a resolution are different. “We have passed this to the team” records a route, not an outcome. A case marked closed should mean that the agreed action was completed or that the person received a clear explanation of the result, within the limits of what the organisation can do. If a request cannot be fulfilled, do not hide it as a success. State the decision and explain the next appropriate route where possible.
Write a handoff rule in plain words: “The current owner remains responsible until the receiving owner accepts the case.” This is an example of a proposed internal practice. It prevents a work item from sitting between teams. Decide how to handle absence and when an overdue item becomes visible to someone with authority to reassign it. The exact time window depends on the service, urgency and staffing.
Figure 5
Figure 5 in words: Receive the actual request, summarise the minimum verified facts, assign a responsible role, give a realistic update, then confirm closure and learn from any repeated gap. An issue can change hands while ownership remains explicit.
When channels do not share the same record
A team may speak in one place and work in another. Do not assume a public platform message, an email and a support tool automatically join into one truthful history. Decide what each system is for and what can be transferred. The person helping next may need a reference to an authorised case rather than a copied transcript. Permissions should be designed around who needs to act, and the organisation should decide how changes and access are reviewed.
If a person contacts you through a public community space, answer the general part there where useful and route account-specific details through an approved private channel. Do not use the public thread as a substitute for identity verification or a support case. Chapter 23 covered that public/private boundary in more detail. The CRM lesson is what happens after the handoff: ownership, enough context, a real update and a checked outcome.
5. Know the three common CRM jobs
Operational CRM supports daily activities such as assigning a request, reminding a person of a promised follow-up and making the current status visible. It can automate a routine step, but a human should design the rule and check exceptions. An automated message cannot independently know whether a complex issue has been resolved.
Analytical CRM looks for patterns in records. It may help a team notice repeated questions, unresolved cases or different experiences across routes. A pattern is a prompt to investigate, not an explanation by itself. If the dataset has missing cases, inconsistent labels or a biased sample, the analysis may mislead. Review a sample of original context before changing policy.
Collaborative CRM coordinates relevant information across functions or partners. In a beginner account, think “the service team and marketing team understand their distinct responsibilities” rather than “everyone can access everything.” The OpenStax textbook uses these three broad categories (Gomez Albrecht, Green and Hoffman, 2023). Its examples include wider data sharing, but a real implementation must separately check purpose, legal basis, access and the person's expectations before sharing personal information. The categories describe jobs a system can perform; they do not authorise any particular data use.
Figure 6
Figure 6 in words: Operational work coordinates a next action; analytical work examines patterns; collaborative work shares necessary context with the appropriate people. All three should serve a clear purpose and be checked for accuracy, permission and usefulness.
Where automation helps and where it can hurt
A reminder that an assigned case is overdue may help. A rule that quietly sends a promotion whenever someone asks for support may damage the relationship and require a separate legal assessment. Begin with a manual process you can explain in one paragraph. Then automate a well-understood repetitive step. Define the trigger, the intended action, the exception, an owner for failures and a way to stop or correct it.
Be wary of a stage label that pretends to know a person's intention. Opening an email does not prove interest in a purchase. A missed reply may mean a broken inbox, a change of mind, accessibility difficulty or simply that no reply was needed. Treat behavioural signals as limited observations, not hidden knowledge of a person's feelings.
6. Separate service from marketing permission
This boundary matters. Someone may provide an email address so you can answer a question or fulfil a request. That does not automatically give blanket permission to send promotional messages. The ICO's purpose limitation guidance says to specify why personal information is collected, document the purpose, tell people about it and consider whether another use is compatible with the original one (ICO, 2026). Its direct marketing guidance says that use of contact details for phone or electronic marketing can involve the Privacy and Electronic Communications Regulations, alongside data protection law where personal information is processed; the applicable rules depend on the method and circumstances (ICO, no date c).
Consent is one possible legal basis in relevant circumstances; it is not a universal label to paste on every contact. Legitimate interests may be relevant to some activities when the legal conditions are met, but do not assume that recording it in a CRM makes a message permitted. If an organisation plans actual direct marketing, it needs to identify the channel, recipient type, lawful basis, any PECR requirement and how objections or opt-outs are honoured. This article explains the distinction, not a complete compliance decision for a real campaign (ICO, no date c).
Keep a separate, intelligible record of communication choices. What did the person choose, for which channel and purpose, and when? Can the person change it easily? Does a service team know that an opt-out from marketing does not mean it must ignore a legitimate support request? The exact retention of preference evidence and suppression records requires an organisational decision. Avoid inferring permission from a missing field, an old import or silence.
Figure 7
Figure 7 in words: A help request is primarily for resolving that request; a purchase is for fulfilment and support; a newsletter choice concerns a defined communication; an opt-out must be respected. Before sending marketing, check the applicable channel rules, purpose and lawful basis. The diagram is a question map, not a legal verdict.
Personalisation should make help more relevant
Personalisation means adapting a message or experience using information about a person or their context. A useful version may avoid asking someone to repeat a known unresolved question. An intrusive version may infer sensitive needs from unrelated behaviour and surprise the person. Use the smallest amount of relevant information, be transparent about its purpose and let people correct an error (ICO, 2026; ICO, no date b).
Do not assume that more data equals a better relationship. A team can remember a promised follow-up with a simple factual note. It does not need to collect a person's unrelated interests or private circumstances to be courteous. Good service can be ordinary: a clear answer, a kept date, a correction and respect for a choice.
7. Keep the record accurate, limited and usable
The person may change contact details, correct a factual error or ask why information is stored. Decide how your process handles these events. The ICO says personal data should be accurate and, where necessary, kept up to date, with appropriate steps to correct or erase inaccurate data (ICO, no date a). A record that is useful today may be misleading next year. Put a review date on assumptions and statuses when they may become stale.
Purpose limitation asks why information is being used (ICO, 2026). Data minimisation asks whether each item is needed for that purpose (ICO, no date b). Accuracy asks whether the information is correct enough for its use (ICO, no date a). Storage limitation asks whether it is still necessary to keep it in identifiable form (ICO, no date d). These principles are related, but one does not replace the others. The source pages can change, and the ICO notes that some guidance is under review. A real deployment needs a current, context-specific review.
When designing access, ask who needs to view, change, export and delete each kind of record. A staff member who answers general questions may not need payment information or sensitive notes. An export can multiply the places where data must be protected and corrected. Define an approved place for records, an owner for mistakes and a process for a person's rights requests. The worksheet in this article is blank on purpose: do not use it to store real personal information.
Figure 8
Figure 8 in words: Start with the purpose, check accuracy, restrict access to appropriate roles, review whether the information is still current, and remove or anonymise it when the relevant retention rule calls for that. This is a teaching check, not a complete data protection policy.
How to write a good case note
Keep it factual and brief. A useful note might describe the question, what was actually checked, the current status, the next action, the owner and the date. Avoid copying private details unnecessarily, guessing a person's motivation or declaring a matter resolved before verifying it. If the record must distinguish the person's account of events from the team's conclusion, label the two clearly.
If a record is corrected, consider whether a previous decision based on the wrong information also needs review. Make it possible for the right staff member to see the correction. A neat dashboard built on inaccurate notes will still produce poor decisions. The aim is a coherent service experience, not maximum data collection.
8. Measure whether CRM helps people
Begin with the promise you made. If the promise is to answer and resolve relevant requests, measure the queue and inspect the quality of a sample of outcomes. Open cases show work that is still waiting; check how old or urgent it is. Resolved cases show what the team marked complete; read a sample to see whether the person's issue was actually addressed. Repeat contact may reveal friction, but can also mean a person has a new, unrelated question. Retention means the continued use or purchase of a service over a defined period, but it needs a clear denominator and should not be treated as proof of affection (Gomez Albrecht, Green and Hoffman, 2023).
Write down the definition before reporting a percentage. If you calculate a resolution rate, specify which cases entered the period, what counts as resolved and whether reopened cases are included. A small team can start with an honest count plus a few reviewed cases. Do not invent a benchmark or claim a target is universal. A high number of automated acknowledgements may coexist with a backlog of unanswered issues.
Payne and Frow (2005) place performance assessment alongside strategy, value, channels and information management. That is a helpful reminder that CRM measures should reflect the value delivered and the process used, not merely the size of a database. Their framework is conceptual; it does not supply a single formula that proves a relationship is healthy.
Figure 9
Figure 9 in words: Open cases may reveal a waiting queue; resolved cases need an outcome check; repeat contact needs interpretation; retention needs a clear definition and voluntary context. Counts become useful when read with a sample of real outcomes and a decision to improve something.
A note about customer lifetime value
You may encounter customer lifetime value (CLV), an estimate of the value associated with a customer relationship over time. It involves assumptions about future behaviour, costs and the period considered. It is not a label for a person's human worth, and it should not be used to justify ignoring someone with a small predicted spend. Chapter 25 will explain a beginner-friendly calculation and its limits. Here, remember only that CRM records can inform an estimate when collected and used appropriately; a number alone does not tell you whether service is fair.
Try it: draw a CRM care process before a product screen
Use an empty piece of paper or Figure 10. Choose a real process you are authorised to design, or make a hypothetical blank process with unknowns explicitly marked. Do not write any actual person's name, email, complaint or order details in this teaching exercise. There is no fictional company or invented customer journey to copy.
Promise: Write one sentence about the help the process should provide. Name the type of request, not a specific person.
Routes: List the channels where a request might arrive and the approved route for a private case. Mark any unverified route “needs checking.”
Minimum record: For each proposed field, write what action it enables. Delete fields with no clear purpose. Separate contact, case, next action and marketing choice.
Owner and handoff: Name the role that gives the first reply, the role that can resolve the issue and who follows up if ownership changes.
Communication choice: Explain how service messages and marketing messages are distinguished. Identify the legal and operational check that a real campaign would need.
Access and retention: Write who needs each type of information, how inaccuracies can be corrected and who sets the retention policy.
Review: Pick one measure of waiting work and one check of actual resolution quality. Set a date to review the process and one known question to resolve.
Figure 10
Figure 10 in words: The blank sheet asks for the relationship or service purpose, contact routes, minimum useful record, case owner and handoff, marketing choice, access and retention, and service quality review. It ends with one unanswered question and a next review date. It is not a place to store real personal data.
A strong first draft can be modest. It says who does what and why, where a case goes, what minimum context travels with it, how a person can correct information, and what is still unknown. If you cannot answer who owns a case after a handoff, fix that before adding automation. If your proposed marketing field has no clear basis or scope, leave it out of the live process until it has been reviewed.
Common mistakes to catch
Buying the tool before defining the work. A vendor can show a beautiful screen; it cannot decide your promise, staffing or responsibility. Draw the process first.
Calling every record a customer. An enquirer, subscriber and existing customer may need different service and communication. Keep the actual relationship and purpose clear.
Treating a support enquiry as marketing permission. Check the purpose and applicable channel rules. Keep a separate, meaningful record of communication choice (ICO, 2026; ICO, no date c).
Collecting everything just in case. Every extra detail creates an accuracy, access and retention question. Start with the minimum useful record (ICO, no date b).
Counting acknowledgements as resolutions. Inspect what happened after the message was sent. A case can be acknowledged and still be open.
Inferring intention from a stage label. A person may read, pause, decline or return for reasons the system does not know. Do not turn a guess into a fact.
Keeping data indefinitely. Review what is still needed for the documented purpose and follow the applicable retention decision (ICO, no date d).
Check your understanding
Suppose a person sends a question through a support form. What can the record usefully do? It can hold the question's factual summary, a suitable contact route, an owner, status and next action so the team can respond. The form submission alone does not establish that the person wants a promotional newsletter. The team needs to check the actual communication choice and applicable rules before any marketing use (ICO, no date c). This is a generic reasoning exercise, not a story about a real customer.
Now suppose a case has moved to a specialist. The first responder can acknowledge the route and an update point, while the specialist confirms ownership. Closing the case requires checking the outcome. If a person corrects an inaccurate detail, the authorised record should be corrected and any affected next action reviewed. The tool is useful insofar as it helps these people do the work accurately.
Optional videos
Start with a very short overview:What is CRM and How Does it Work?, Salesforce (published 24 March 2021). Its public description introduces customer information shared across marketing, sales and service. This is a commercial software company's explanation and promotes its own product; watch for the general concept, not as neutral proof of business benefits.
Go deeper with an academic lecture:Lecture 01 CRM A Strategic Imperative, Marketing Analytics by Prof Swag (published 18 November 2025). The channel description identifies it as a copy of Prof. Swagato Chatterjee's NPTEL course lecture; the official NPTEL course lists him and Lecture 01 under the same title. The provenance is stronger than an unattributed repost, but the specific upload and spoken content still need playback review. The lecture may be more demanding than the written chapter; return to it later if you prefer.
Public metadata, descriptions and the official course listing were inspected on 15 November 2026; neither video was played or transcript-reviewed. Exact runtime, captions, spoken language, UK playback and embeddability were not verified. Both choices are provisional. The text above contains the whole lesson.
What comes next
Chapter 25 will examine customer lifetime value: what a simple estimate can help you decide, what assumptions it needs, and why a predicted financial value cannot replace respectful treatment. Add the actual internal canonical link when that chapter is published. Chapter 26 will bring the planning, channels and relationship work into a measurement and launch review.
Payne, A. and Frow, P. (2005) 'A strategic framework for customer relationship management', Journal of Marketing, 69(4), pp. 167–176. Available at: https://doi.org/10.1509/jmkg.2005.69.4.167 (Accessed: 15 November 2026).
A beginner-friendly route through 26 short lessons on customers, offers, channels, content and measurement. Start anywhere, with no account or paid tools.
Learn the difference between features and benefits, write a promise customers understand, and check which kinds of online value you can honestly deliver.