Customer 360 build: интеграция fragment customer data

Контекст

Universal коммерческий банк УЗ. 800k retail customers, 12k SME, 800 corporate. Customer data fragmented across 7 product systems (АБС, cards, lending, deposits, ВЭД, ипотека, investment). Cross-sell ratio 1.6 products average.

Marketing campaigns hit-rate 1-2% (target 4-5%). Contact center handle time высокий — operator switches между systems.

Диагностика (5 недель)

Identity resolution audit:

• 800k customer records → 580k unique persons (28% duplicates).
• Cross-product visibility: <40% customers visible across product systems.
• Consent state: dispersed, partial, partly invalid.

Подход (12 месяцев)

Месяцы 1-3. Architecture design. Greenfield CDP, identity resolution engine, event ingestion. Не replacement product systems, layer above.

Месяцы 3-6. Identity resolution build. Probabilistic matching, golden record builder, manual stewardship workflow для conflicts.

Месяцы 6-9. Profile store + event ingestion. Real-time updates через event bus.

Месяцы 9-12. Channel activation. Pilot — contact center первый (high impact), затем mobile app, marketing.

Результаты

После 12 месяцев:

• Identity resolution: 580k unique persons identified (vs 800k duplicate-laden raw).
• Match rate в profile store: 91%.
• Cross-sell ratio в pilot channels: 1.6 → 2.4 products average.
• Marketing campaign hit-rate: 1.5% → 4.2%.
• Contact center handle time: −22%.
• Customer NPS у pilot channel users: +18.

Что критически важно

Greenfield architecture decision — не try в legacy DWH.

CDO sponsorship strong — cross-team alignment essential.

Stewardship workflow для conflicts — automation не resolves all cases.

Pilot first channel (contact center) — measurable impact justifies broader rollout.

Что не сработало бы

Fold CDP в existing DWH — latency и schema constraints.

Identity resolution rules-only — too brittle.

Big-bang channel activation — operations risk.

Связанное

• /solutions/banking-customer-360-platform/ — customer 360
• /architecture/banking-cdp-architecture/ — CDP
• /architecture/banking-master-data-management/ — MDM
• /decisions/banking-build-vs-buy-cdp/ — CDP decision