Customer 360 architecture in a bank and at a telecom operator
Customer 360 in a bank and at a telecom operator is not a CDP procurement but an architectural layer above the existing stack. This article walks through the layer's components — identity resolution, unified profile, event flows, consents — and the approach to building them around existing core systems without core replacement.
Discuss Your ChallengeThis architectural article covers Customer 360 as a layer above the existing customer landscape of a bank or telecom operator — without core replacement, with a mandatory data steward and consents.
What architecture challenge is being solved
Customer data in a bank and at an operator is fragmented across product systems — billing, CRM, anti-fraud, AML, mobile app. One customer has 1.5-2 versions on average. Without a unified profile layer, cross-sell is weak, the contact center switches between systems, marketing operates on coarse segmentation. Customer 360 architecture solves this through a specialized layer above product systems, keeping them as sources of truth in their domains.
Which systems, data flows and teams are involved
- Sources of truth — core/BSS (products), CRM (inquiries), marketing platform (campaigns), anti-fraud (risk events)
- Identity resolution layer — deterministic and probabilistic record linkage rules
- Profile storage — hot (current snapshot for channels) and cold (history for analytics)
- Event flow — event bus through which product systems publish changes
- Consent layer — granular consents by use purpose verified in real time
- Consumption channels — mobile app, contact center, marketing platform, partner gateway
Typical architecture mistakes
- Trying to create a copy of all customer data in one storage — violates sources of truth and creates a sync nightmare
- Customer 360 as procurement of a ready CDP without adaptation to bank/telecom landscape specifics
- No data steward role — the profile degrades from garbage in the first 6-12 months
- Launch without a consent layer — legal problems on the first regulator audit
- Event flows without schema registry — consumers break on format change
- Profile built in isolation from marketing — after launch turns out to be without main consumer
Possible approaches
- MDM approach — single customer master with sources of truth by field. Good for mature organizations with established processes
- CDP approach — event-driven hot storage for marketing. Good for dynamic personalization
- MDM + CDP hybrid — MDM as source of truth, CDP as hot layer for channels. Approach of most mature banks and operators
- Lightweight identity resolution layer without separate storage — profile assembled on the fly. Suitable for smaller organizations
How to avoid unnecessary core replacement
Core/BSS remain sources of truth in their domains and are not replaced. Customer 360 is a layer above them, consuming events and providing the profile to channels. When one of the product systems ages out, it can be replaced without rebuilding the layer — the layer consumes events from any source implementing the shared contract.
Risks, dependencies, constraints
- Source data quality — the layer will not fix garbage, only make it visible
- Data steward as a mandatory role — without it the profile becomes an error source
- Dependency on event flows from product systems — each integration is a separate task
- Consents to data use — legal part without which the layer cannot be used in marketing and partnerships
- Biometrics 2026 as a new identification key — embed architecturally from day one
How a phased roadmap should look
- Months 1-3: fragmentation diagnostics, architecture design, approach selection (MDM/CDP/hybrid)
- Months 4-9: identity resolution layer and unified profile, integrations with 3-5 key sources
- Months 10-15: consumption channels — contact center first, mobile app second
- Months 16-24: marketing layer, partner gateway, biometric contour
- After 24 months — expansion to new product systems and channels
What else is worth exploring
Topics from the same area we usually explore together
CRM
Not an off-the-shelf CRM, but a properly built customer management contour — from first contact to loyalty.
→SolutionBI
Analytics is not pretty charts on the wall. It's the answer to 'why?' before the problem becomes a loss.
→SolutionContact Center
The contact center is not a phone station — it's the point where a client decides: stay with you or leave. The question is how it's built…
→SolutionOnboarding
Onboarding is your company's first impression. If it takes 5 days and 12 paper forms, there won't be a second impression.
→I do not just write about this. I can come in, examine your situation and design a solution for your specific landscape.
Discuss applying this →Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours