Designing Real-Time Decisioning for the Call Center
A major telecommunications organization needed to connect enterprise customer data, real-time decisioning, and its Salesforce agent desktop so call-center representatives could receive contextually relevant next-best actions at the beginning of an interaction.
THE CHALLENGE
The organization needed to make a real-time decision when a customer entered the call-center experience, but profile selection could not assume that every telephone number would resolve cleanly to one customer.
The solution needed to account for:
- Successful customer-profile matches
- No-match scenarios
- Telephone numbers associated with multiple profiles
- Alternate identity-resolution paths
- Eligibility and suppression
- Channel-specific context
- Appropriate fallback behavior
- Reuse across multiple call-center organizations
THE APPROACH
The engagement translated the business objective into a structured Adobe Experience Platform and Adobe Journey Optimizer decisioning model. The architecture treated the customer telephone number as an important initial identifier while explicitly designing for unsuccessful or ambiguous matching.
The design connected:
- Call routing and interaction initiation
- Salesforce agent desktop
- Adobe Experience Platform profiles
- Adobe Journey Optimizer decisioning
- Customer eligibility
- Offer and action prioritization
- Real-time context
- Response presentation
- Measurement and feedback
The approach was designed first for Mobility Sales and Service while establishing reusable patterns for future expansion into wireless retention, broadband sales, broadband service, and broadband retention.
BUSINESS OUTCOMES ENABLED
- Contextually relevant next-best-actions delivered at the beginning of every call
- Ambiguous and no-match calls handled with intentional fallback behavior
- A reusable pattern extendable across additional call-center lines of business
- A shared understanding across marketing, contact-center operations, data, and Salesforce teams
DECISIONS RESOLVED
- Which identifier is used to initiate a real-time decision
- How profile ambiguity and no-match scenarios are resolved
- Which eligibility, suppression, and prioritization rules apply
- How offers and actions are presented on the agent desktop
- How outcome and feedback data flow back into the decisioning model
REPRESENTATIVE DELIVERABLES
- Business requirements document
- Real-time interaction flow
- Identity-resolution decision tree
- Profile-match and fallback requirements
- Next-best-action eligibility framework
- Salesforce activation requirements
- Risk and dependency register
- Phased implementation roadmap
- Future call-center reuse model
EXECUTIVE VALUE
Turned an ambitious real-time decisioning ambition into an accountable, phased build plan that engineering, contact-center operations, and Salesforce teams could execute together.
CAPABILITY UNLOCKED
A reusable enterprise blueprint for delivering contextually relevant decisions to agents while handling identity uncertainty intentionally rather than treating every interaction as a perfect profile match.
REAL-TIME INTERACTION FLOW
Incoming Call → CTN Lookup → Unique / Ambiguous / No Match → Eligibility & Decisioning → Salesforce Agent Experience → Outcome Measurement
IS THIS A FIT FOR YOUR ORGANIZATION?
This engagement pattern typically fits organizations where:
- You are launching or expanding real-time decisioning, next-best-action, or agent-assisted personalization
- Identity resolution — particularly around telephone number, account, or household — is not fully governed
- The program depends on the Salesforce agent experience or a comparable service desktop