STT, TTS, visemes, and avatar-ready voice
Camlin Speech
Recognition, prompting, and validation
Own the speech layer, keep provider choice
First-party STT, tuned for the service
Camlin Speech gives Nuamedia a first-party recognition layer for contact-centre and avatar journeys. It is tuned around the phrases, IDs, names, and service moments your flows actually need.
Tenant vocabularies and field capture
Register the names, brands, reference formats, and service terms your callers will say. The speech layer can bias recognition and route output into business fields instead of raw transcript text.
TTS plus viseme output for avatars
The TTS path generates spoken responses plus viseme/blendshape timing for avatar playback — the same envelope that drives live avatar lip-sync on a real phone call.
Provider choice when you need it
Promote the Camlin engine by default while keeping other providers available for tenders, specific languages, or fallback requirements. Architect can author the speech settings without splitting the service.
One speech service, every channel
Contact + Voice
Recognition, TTS, and structured capture power every live call. 5 providers, 16 entity types, and confidence-based retries drive the phone experience.
See Contact + VoiceArchitect
When agents draft Interactions, the speech prompts, recognition grammar, TTS settings, and validation rules are authored alongside the service design.
See ArchitectAvatar + Visual IVR
The same speech service drives avatar voice, lip-sync timing, and visual IVR input — so recognition stays consistent across screen and phone.
See Avatar + Visual IVRHow speech flows through the platform
Caller speaks or types
Audio or text input arrives from the channel — phone, web chat, avatar, or SMS.
The channel determines which speech provider and mode to use based on the Interaction design.
Agents author speech as part of the service
Agents see the prompt wording, TTS voice, and timing alongside the Interaction it belongs to.
Grammar, confidence thresholds, retry logic, and capture fields are defined per-Interaction, not globally.
Different Interactions can use different speech providers — Google for one, Deepgram for another — without splitting the service.
Four ways to go deeper
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 Contact
Voice, SIP, queues, visual IVR, SMS, and live service operations.
Camlin Insights
Trace, diagnostics, change history, audit evidence, and product memory.
Camlin Biometrics
Voice identity, step-up checks, fraud controls, and consent evidence.
Hear the difference
What’s next for Camlin Speech

