Voice RuntimeInside Camlin Contact
Where Voice Sits
Nested inside the Contact operating model
What Voice handles inside the Contact stack
IVR turns and session control
Camlin Voice runs the live voice loop inside Contact, including prompts, recognition handoff, retries, transfers, queue entry, and runtime state management.
Operational flow inside Contact
Voice is the runtime inside the Contact layer, not a separate front-door product. It exists to support operational service journeys and telephony execution.
Speech handoff and prompting
Voice uses Camlin Speech for recognition, transcription, prompting, and structured capture so Contact journeys can be tuned without splitting the product story.
Observability and follow-through
Voice events, runtime behaviour, and operational context can then be understood through Insight and extended with Avatar when a visual step helps.
Voice only makes sense in relation to the rest of the platform
Inside Camlin Contact
Contact owns the operational layer. Voice is the runtime that makes IVR, queue entry, transfer paths, and telephony interactions work within it.
Powered by Camlin Speech
Speech provides the shared recognition and prompt layer. That keeps the voice runtime connected to the same speech capabilities used elsewhere across the platform.
Extended by Insight and Avatar
Insight adds diagnostics and audit context. Avatar can add a visible assistant when a journey benefits from a face and voice without changing the core runtime story.