MARK5827 Chap.2 CRM, Customer Value and Privacy
CRM, Customer Value and Privacy
Customer relationship management selects customers the firm can profitably serve and shapes interactions across the relationship. This chapter separates value for the customer from value for the provider, follows the satisfaction, loyalty and profit chain, and explains why customer heterogeneity and lifecycle change make one approach unsuitable for everyone.
It also treats privacy as an analytical and commercial issue because weak trust can reduce data quality, campaign response, brand equity and firm value. Customer-side value can be functional, economic, emotional or symbolic, and it must be considered alongside time, learning effort, price and risk. Provider-side value includes lifetime purchases, referrals, influence and knowledge that improves future decisions.
Those contributions may disagree, particularly as relationships develop or decline. The satisfaction chain should therefore be read as a sequence of testable links rather than a guarantee that better service always produces profit.
Privacy sharpens the trade-off: greater data access can improve personalisation, but opaque collection can reduce truthful disclosure, trigger withdrawal and weaken the very information the analysis depends on.
What this chapter covers
- 01
CRM as customer selection and interaction management
- 02
Customer-side functional, economic, emotional and symbolic value
- 03
Provider-side lifetime, referral, influencer and knowledge value
- 04
Customer lifecycle and changing relationship contribution
- 05
Heterogeneity and differentiated CRM interventions
- 06
Privacy, transparency, control and data quality
Worked example · free
Evaluate value from both sides of a service integration
- 1Customer value can increase through lower planning effort, greater choice and better fit.
- 1Provider value can increase through customer knowledge, personalisation, retention and additional purchases.
- 1Combining detailed records may weaken trust, lower truthful disclosure and cause opt-outs, so use transparent opt-in testing.
Key terms
- Customer Value
- The perceived benefit-cost balance for a customer or the contribution to a provider, depending on viewpoint.
- Lifetime Value
- The financial contribution expected across a customer's relationship with the firm.
- Knowledge Value
- The contribution customer information makes to learning and better decisions.
- Privacy Concern
- Customer unease about collection, access or use of personal information.
CRM, Customer Value and Privacy FAQ
Why are there two views of customer value?
Customers evaluate benefits such as function, convenience, emotion or symbolism against costs and risks. Firms evaluate lifetime, referral, knowledge and influencer contributions. An initiative can improve one side while harming the other, so a responsible analysis states both viewpoints.
How does the customer lifecycle affect CRM decisions?
Needs, purchases, costs and future potential change as a relationship develops. A current snapshot can misclassify a declining, growing or temporarily inactive account. Analysts should consider relationship duration, direction, future potential and non-purchase contributions before allocating CRM resources.
Why is privacy part of customer analytics?
Privacy concern can make customers withhold or falsify information, reduce response, damage trust and weaken brand perceptions. Those outcomes lower the quality of analytical inputs and the effectiveness of actions, so transparency, control and limited collection protect both customers and analysis.
Does higher satisfaction always create more profit?
No. Satisfaction may fail to produce loyalty when switching is easy, and retained customers may remain costly to serve or unprofitable. Treat product performance, satisfaction, retention and profit as links to test. Measure the mechanism and customer group rather than assuming the whole chain moves automatically.
Assessment move
Draw two columns for every case: customer-side benefit and provider-side contribution. Add a third row for relationship risk, especially privacy and trust. Practise tracing the satisfaction, loyalty and profit chain without assuming every link is automatic. When a prompt describes different customer groups or relationship stages, identify how the recommended action should change.
Finish each answer with a measurable outcome and one adverse effect to monitor, so the proposal remains relational rather than merely extractive. Build a lifecycle sketch for acquisition, development, retention and possible reactivation, then place the evidence in the appropriate stage. Challenge any recommendation based only on current revenue by asking about future contribution, service cost, referrals and knowledge.
For privacy questions, connect the practice to a behavioural consequence such as false information, opt-out or lower response instead of writing only about compliance. Rehearse the distinction between transparent choice and mere notice. A strong case answer should show what customers gain, what the firm gains, what could damage trust, and which measure would reveal whether the relationship improved.
After drafting, replace vague promises such as personalisation or engagement with the specific service change, customer behaviour and relationship metric that would demonstrate value.
Working through CRM, Customer Value and Privacy in MARK5827? Sia is AskSia’s AI Marketing tutor — ask any MARK5827 CRM, Customer Value and Privacy question and get a clear, step-by-step explanation grounded in how MARK5827 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
