Salesforce Decode
Salesforcedecode
Back to questions
Data CloudArchitect (Hardest)unified-profileapicontact-centerreal-time

Expose unified profile APIs for contact center real-time personalization

Real World Scenario

Contact center IVR and agent desktop need unified profile showing loyalty tier, recent orders, and open cases within one second of call start. Current CRM screen pop shows CRM only, missing Data Cloud attributes.

Expected Answer

• Design Profile API aggregating Data Cloud Individual attributes with CRM operational fields • Cache hot profile slices with TTL; invalidate on high-value events like order placed • Authenticate API with scoped OAuth for contact center vendor per PCI requirements • Return consent-gated marketing attributes separately from service-required fields • Implement circuit breaker returning CRM baseline if Data Cloud API latency exceeds threshold • Monitor API p95 latency and error rate per routing skill group • Document field lineage so agents trust data freshness indicators displayed in UI

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Design Profile API aggregating Data Cloud Individual attributes with CRM operational fields. Cache hot profile slices with TTL; invalidate on high-value events like order placed. Pick based on your integration pattern and team capability. Contact center real-time is the hardest latency SLA—design graceful degradation, not all-or-nothing profile calls. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Contact center real-time is the hardest latency SLA—design graceful degradation, not all-or-nothing profile calls.