CAMLIN SPEECH

STT, TTS, visemes, and avatar-ready voice

Camlin Speech is Nuamedia’s own speech layer for STT, TTS, prompts, structured capture, and avatar-ready viseme output. Use our engine by default, keep Google, Deepgram, Azure, and other engines available when a tender or journey needs them.
5
Speech Providers
Choose the right one
8
Ways to capture input
Spoken to structured
16
Business details
Dates, numbers, IDs
Try the live demo

Camlin Speech

Recognition, prompting, and validation

LIVE EXAMPLE
Recognition result

Recognition + prompting
Capture, validate, and respond in one service
Structured output
Business fields and confidence checks
📞
Contact
🧭
Design
🧩
API/Avatar
THE SPEECH STACK

Own the speech layer, keep provider choice

Recognition, TTS, prompts, visemes, and structured capture live in one layer so Contact, Voice, Avatar, and every channel can share the same speech logic.

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.

Live STT demo path
Sydney or private deployment options
Reduced dependence on cloud STT

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.

Per-tenant lexicons
Names, IDs, dates, and references
Structured output for Interactions

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.

Frame-accurate ARKit visemes
Avatar-ready timing envelope
Provider-compatible TTS routing

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.

Google, Deepgram, Azure, AWS support
Provider per journey
8 recognition modes
WHERE SPEECH SHOWS UP

One speech service, every channel

Speech powers phone calls, avatar lip-sync, visual IVR, and chat. The same recognition and prompt rules apply everywhere — one config point.

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 + Voice

Architect

When agents draft Interactions, the speech prompts, recognition grammar, TTS settings, and validation rules are authored alongside the service design.

See Architect

Avatar + 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 IVR
SPEECH PIPELINE

How speech flows through the platform

Follow spoken or typed input through recognition, validation, and response. Each step connects to a different speech capability.

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.

AUTHORED IN ARCHITECT

Agents author speech as part of the service

When agents draft an Interaction, the speech prompts, recognition grammar, TTS settings, and validation rules are part of the draft — not configured separately.
Prompts in context

Agents see the prompt wording, TTS voice, and timing alongside the Interaction it belongs to.

Recognition rules

Grammar, confidence thresholds, retry logic, and capture fields are defined per-Interaction, not globally.

Provider per journey

Different Interactions can use different speech providers — Google for one, Deepgram for another — without splitting the service.

HEAR IT LIVE

Hear the difference

Side-by-side clips where Camlin Speech nails Australian phrases the cloud STTs drop. Then try the live engine on your own voice.

What’s next for Camlin Speech

AU-tuned production model · shippingFirst-party AU voices, recorded in Sydney · in studioReal-time live captions on customer hardware · live demo