The voice engine behind every live call in Contact
Where Voice Sits
Inside Contact, not separate from it
What happens when a call arrives
Call arrives via SIP
The call enters Contact through open SIP (Twilio, carrier trunks), hits the queue, and is routed based on the Blueprint authored in Architect.
Contact owns queues, routing, and supervisors. Voice picks up the phone-side experience from here — IVR, prompts, and live call control.
AU-tuned recognition, per-tenant custom lexicons, sovereign hosting
Voice runs on Camlin Speech — our first-party Australian-English STT and TTS engine. Recognises Centrelink CRN, rego renewal, NBN FTTP, BPay reference and AU place names out of the box; teach it your own product, suburb and street lists per-tenant for the rest. Hosted in Sydney or deployed on-prem with no per-minute STT bill.
Every call runs a service designed by agents
Agents draft what the caller hears, how input is captured, and what happens on each response.
Routing, retries, escalation, and handoff rules are part of the Interaction, not hard-coded into Voice.
When the Blueprint changes, Voice runs the new version. No IVR rebuild, no separate deployment.
Explore the platform
Camlin Architect
Describe the service, inspect the Blueprint, trace runtime behaviour, and publish.
Camlin Avatar
Visible agents for websites, calls, meetings, and guided service journeys.
Camlin Speech
Nuamedia STT, TTS, prompts, visemes, and provider routing.
Camlin Insights
Trace, diagnostics, change history, audit evidence, and product memory.
Camlin Biometrics
Voice identity, step-up checks, fraud controls, and consent evidence.