CAMLIN VOICEID

Verify callers without bolting on another vendor

Account takeover. Recovery calls. Sensitive changes. These are the moments where identity matters.VoiceID verifies callers inside your Contact journeys: consent-first enrolment, one-to-one checks, step-up when it matters, audit evidence throughout. Built by Camlin, hosted in Sydney. Authored in Architect, run in Contact, audited in Insight.
Voice verification in the live call
Consent-first, revocable voice templates
Consent and audit in Insight
Authored in Architect, run in Contact
See Camlin Contact
He says hello on the call; the avatar holds his voice template and the journey gets an outcomeA man on the phone says “Hi, it’s me.” After consent, his live call audio becomes a protected voice template rather than a recording, shown as the VoiceID shield in the hands of the avatar on a mobile. The journey receives match, no match or inconclusive, never a score.Consent first“Hi, it’s me.”Live call audioA protected voice templatenot a recording · keyed, revocable, one-to-oneTO THE JOURNEYMatchNo matchInconclusivenever a score
“Is my voice kept as a recording, and can I have my voiceprint deleted?”
HOW IT WORKS

How it works

Voice identity inside Contact journeys.
1. Enrol with consent
The caller hears the disclosure and agrees before anything is captured. Enrolment happens in the live call. A quality gate rejects audio too short, quiet, clipped or noisy to trust, and checks for replayed recordings and synthetic voices.
2. Verify in the live call
Contact runs the journey. VoiceID checks the caller against their own template, passively from natural speech, or with a randomised spoken passphrase for higher-assurance steps.
3. Decide on a clear outcome
The journey receives match, no match or inconclusive. Never a score. A match continues; anything else falls back to knowledge questions, an agent or analyst review.
4. Audit, revoke, and stay in-region
Every outcome, consent step and reviewer action is recorded in Insight. Templates are keyed and revocable per person. The engine is Camlin-built and runs in Sydney or in your own environment. No third-party biometrics cloud in the path.
CAPABILITIES AND CONTROLS

Verification with the controls you already expect

Consent-first enrolment, one-to-one verification, protected templates and audit evidence. One layer, built by Camlin, not a separate vendor stack.

Consent-first enrolment

Enrolment proceeds only after the caller has heard the disclosure and agreed. Decline, and no template is captured. The consent basis and capture path are recorded with every enrolment.

One-to-one verification

Verify a claimed identity live in the call, passively from natural speech, or with an optional randomised spoken passphrase for higher-assurance steps. One-to-one only. No watchlists.

Clear outcomes, not scores

The journey receives match, no match or inconclusive. Never a raw score. Inconclusive falls back to knowledge questions, an agent or analyst review, not a dead end.

Quality gate and protected templates

Enrolment fails closed on audio that is too short, too quiet, clipped, noisy or mixed-speaker. Templates are keyed per store and can be reset or revoked for any individual.

Presentation-attack detection

Detects replayed recordings and synthetic voices on telephony audio. The result reaches the journey as an outcome and a reason code, not a score.

Measured per deployment

Performance is measured with genuine and impostor test matrices, reported in line with ISO/IEC 19795-1. The numbers you see come from your own test runs, not our brochure.

Audit evidence

Outcomes, consent steps, reviewer actions and journey decisions stay visible to support, security and governance teams in Insight. Your team sees outcomes, not biometrics.

Hosting
  • Camlin-hosted in AWS Sydney (ap-southeast-2), in Nuamedia’s own account, on an engine Camlin built. No third-party biometrics cloud in the path.
  • Customer-hosted: run the same engine in your own environment, with the same consent, template and outcome rules.
WHERE IT SHOWS UP

Verification where the journey needs more trust

VoiceID appears at specific moments, not as a blanket rule. Recovery, account changes, sensitive actions: the calls where the name of your first pet stops being enough.

Three actions in a call flow

  1. Step 1

    Enrol

    First call, after the disclosure and consent. The quality gate refuses audio too weak to trust.

  2. Step 2

    Verify

    Later calls, passively from natural speech, one-to-one against the caller’s own template.

  3. Step 3

    Step up

    For sensitive actions, an optional randomised spoken passphrase for higher assurance.

Match — the journey continues.
No match or inconclusive — knowledge questions, an agent or analyst review. Never a score.
Inbound call verification

An enrolled caller reaches the IVR for an account change. VoiceID verifies them from natural speech as they talk. On a match the journey continues; on no match or inconclusive it falls back to knowledge questions. No dead end.

Queue and IVR entry
Agent-assisted verification
Step-up for sensitive actions
Recovery and account takeover defence

Account recovery calls are the highest-risk moment. VoiceID adds a voice check beside your existing security questions. An extra trust signal, not a replacement.

Recovery call verification
Spoken passphrase for higher assurance
Analyst escalation
Cross-channel trust

The same trust layer works on the phone, in avatar-guided sessions and at digital step-up moments, wherever voice identity adds to your existing controls.

Phone to avatar continuity
Digital step-up moments
Consistent trust model
FRAUD AND TRUST

Identity checks only work when they fit the operation

Identity checks need customer wording, retry rules, fallback paths, review workflows and a clear record of what happened. That is why VoiceID sits beside Contact, Speech and Insight.
Layer identity into the right moments

Higher-confidence checks at recovery, account change, outbound confirmation and other risk-sensitive steps.

Keep a path for review and override

Analyst review, agent escalation and fallback handling when confidence is unclear or the customer context changes.

Make trust decisions explainable

Leave enough context for your team to see what happened and why the journey moved the way it did.

PLATFORM SYSTEM

Explore the platform

Architect designs it, Speech hears it, Avatar shows it, Contact runs it, Insight proves it. Each one works better with the others around.
See Camlin ConnectSee how it works
Product

Camlin Architect

Describe the service, inspect the Blueprint, trace it live, publish.

Product

Camlin Avatar

A live avatar on the call, on your website and in meetings.

Product

Camlin Contact

Voice, SIP trunks, queues, visual IVR and SMS, run live.

Product

Camlin Speech

Recognition, Camlin Voice TTS, prompts and visemes, hosted in Sydney.

Product

Camlin Insight

Traces, diagnostics, change history and audit evidence, in one place.

SEE IT LIVE

See voice verification live

Walk through the verification model, where the trust signals sit, and how VoiceID fits beside Contact, Speech and Insight.