NovelVox + Journey: Execution Without Exposure
NovelVox+Journey:
End-to-End Execution Without Exposing Sensitive Inputs
Customer Verification Minus the Detour
Agent Accelerator and CCIP Cover Both
Agent-Assisted and Self-Service Interactions
Agent Accelerator for Agent-Assisted Interactions
The agent triggers Journey verification from Agent Accelerator. The caller confirms their identity on their own device, and the agent sees a verified or not verified result instead of asking for a date of birth or account number.
CCIP for Self-Service Interactions
The same requests through IVR or an AI agent use the same Journey verification as agent-assisted calls.
Key Integration Benefits
Intent Becomes a Completed Action
NovelVox Governs the Execution Path
Sensitive Inputs Stay Out of AI and Contact Center
Agent Accelerator Shows the Outcome, Not the Data
One Execution Layer, Two Protocols
AI agents reach CCIP over REST or MCP, and AI or IVR requests that require verification can trigger Journey’s API through the same governed CCIP actions.
How It Works
The AI identifies that completing the request requires identity verification.
CCIP validates the request against the system of record and determines what the AI is permitted to do. The IVR or AI agent invokes Journey for verification, directly or through CCIP’s API connection.
The customer completes authentication on their own device through a Journey workflow. The sensitive inputs never reach CCIP, the AI, or the agent.
CCIP receives Journey’s verification result and completes the authorized action in the system of record. The AI or agent continues with the result, not the sensitive inputs behind it.
NovelVox and Journey in Action
A customer is locked out of online banking or asks to reset a password. Journey verifies the customer before NovelVox resets the credential or restores access, replacing knowledge-based questions with a verified result.
A customer verifies through Journey in the IVR, then asks for an agent. Agent Accelerator can show the verified status when the call connects, so the agent moves straight to the request, and transfers can be configured to carry that status forward.
A customer requests a change to a mailing address or other profile detail. Journey verifies the customer first, so the update proceeds on a confirmed identity, and NovelVox completes the change in the core.
A customer raises a dispute or chargeback, a servicing path with elevated fraud exposure. Journey verifies the customer before the dispute is filed, and NovelVox uses the verified result to file it in the system of record, keeping the verification step outside the AI and the agent desktop.
A patient asks to update an address, phone number, or other demographic details. Journey verifies them first, so the update proceeds on a confirmed identity, and NovelVox completes the change in the system of record.