By clicking "Accept", you agree to the storing of cookies on your device to enhance site navigation, analyze site usage and assist in our marketing efforts. More info
CASE STUDY · TELEFÓNICA

Telefónica reduced call-center authentication from 3–4 minutes to under 60 seconds.

Telefónica tested a simpler way for customers to authenticate when calling a contact center. Instead of answering security questions or entering SMS codes, customers could confirm an authentication request with one tap on their phones.

A Telefónica project with Dock Labs, GSMA and TMT ID.

Add the YouTube link in Tweaks
The problem

Proving identity took minutes, yet left security gaps.

Traditional call-center authentication relies on security questions, personal information and SMS one-time codes. It takes 3–4 minutes to complete and remains vulnerable to stolen answers, phishing and phone-number impersonation. Fraudsters can pose as legitimate customers calling in to gain access to accounts.

Customer authentication
Manual call-center process
03:42Elapsed time
Common authentication checks
Ask security questionsAnswers can be phished or socially engineered.
Confirm personal informationDetails may be stolen or used for impersonation.
Send SMS codeCodes can be intercepted, redirected, or phished.
Call center authentication still depends on information that can be stolen, intercepted, or socially engineered.
What Telefónica tested

One tap to confirm identity.

Telefónica used customer information to create verifiable credentials. When customers called, they received a request on their phone to confirm their identity with one tap. The call center then automatically verified the digital proof, without needing security questions or SMS codes.

1. Customer calls

Customer contacts the call center.

I'd like to access my account.
Call center agent with a headset at a computer
2. Customer approves

The customer receives an authentication request and confirms with one tap.

9:41
Authentication requestnow
Confirm it's you calling customer support.
DeclineConfirm
3. Proof verified

The call center verifies the digital proof.

Authentication verified
SourceIssued by TelefónicaApplies toMatches customerIntegrityNot changed since issueStatusValid
Pilot results

Faster authentication. A preferred experience.

Glyn Povah

“The solution transforms authentication times from 3-4 minutes with traditional methods to under 60 seconds.”

Glyn PovahGlobal Product Development Director, Telefónica

Telefónica
80%of trialists said authentication was faster than their normal experience.
67%said it felt more secure.
100%said they would definitely or probably prefer it to their current method.

These findings came from a controlled proof of concept with a limited trial group. They are directional results, not production benchmarks.

Behind the experience

Telefónica provided the trust. Truvera made it verifiable.

Telefónica used customer information it had already verified, supported by network APIs such as Number Verify and SIM Swap, to establish trust in the customer's identity.

Truvera, built by Dock Labs, turned that information into cryptographically signed verifiable credentials. When customers authenticated, the call center could verify the presented digital proof without contacting Telefónica again for each credential check.

Trusted information
Telefónica
Provides verified customer information
Number VerifySIM Swap
Verifiable credential
Truvera
Creates verifiable credentials from trusted information
Verifiable credential
Verified customer identity
Issued byTelefónica
Phone numberVerified
Digitally signed by Telefónica
Verification
Call center
Verifies the digital proof to authenticate the customer
Source verified
Credential integrity verified
Credential status valid

This proof of concept used a standalone identity wallet. In a production implementation, the wallet would be embedded invisibly in Telefónica's existing customer app.

What this could unlock

Beyond caller authentication.

Telefónica's pilot demonstrated how verified customer information could be reused for authentication. The same approach could support other identity workflows and create new opportunities for mobile operators.

Verified customer identity
Third-party verification

Let other businesses verify your customers' identities for their own use cases.

Account recovery

Help customers securely regain access to their accounts.

Onboarding

Reuse verified identity information to create smoother, faster onboarding experiences.

Fraud prevention

Add trusted identity checks to help detect and prevent fraud.

Potential new revenue model
Pay-per-verification revenue.

Mobile operators could charge third parties for verification of trusted information.

Third party requests verification
Telecom provides verifiable proof
Pay-per-verification revenue

Potential future applications and revenue opportunities, not outcomes demonstrated during the pilot.

Where could verified customer information remove friction in your business?

Dock Labs can help you identify where your existing customer data and network signals could support verifiable credentials and new verification workflows.