Do I need to migrate my users off Auth0?

No. Authsignal connects to your Auth0 tenant via Auth0 Actions. Your user directory, sessions, and existing authentication flows all stay in place. Authsignal adds capabilities on top — it doesn't replace anything underneath.

Can Authsignal give me passkeys without an Auth0 enterprise-tier upgrade?

Yes. Auth0's native passkey support is gated behind enterprise pricing. Authsignal provides FIDO2-certified passkeys, adaptive MFA, and a no-code rules engine on top of your existing Auth0 plan — no tier upgrade required.

Why choose Authsignal?

Deploy passkeys and MFA in weeks instead of months. Flexible integration options including pre-built UI, UI components, or headless SDKs. A visual no-code rules engine for adaptive authentication policies. Real-time developer support, comprehensive documentation, and step-by-step integration guides. SOC 2 Type 2, ISO 27001, and FIDO Alliance certified.

What does it cost to integrate with Authsignal?

You can start integrating on our free tier immediately — up to 1,000 monthly active users at no cost. For production deployments, plans start at $1,099/month. Enterprise pricing is available for larger deployments.

Which MFA methods does Authsignal support?

Passkeys (FIDO2/WebAuthn), biometrics, SMS OTP, email OTP, WhatsApp OTP, push notifications, authenticator apps (TOTP), and magic links. All methods are available from a single integration and managed via the no-code rules engine.

What programming languages and SDKs are supported?

Server SDKs for Node.js, Python, Ruby, Java, C#, PHP, and Go. Client SDKs for Web (JavaScript/TypeScript), React Native, iOS (Swift), and Android (Kotlin). Plus a REST API for any language.

Verify who is calling in seconds, right inside Salesforce.

Authsignal Call Connect is contact centre verification built into Salesforce Service Cloud. When a customer calls your support team, your agent confirms they are the real account holder in one click, without leaving the case. The customer approves on their own device. Verification without security questions or reading out card numbers.

Book a demo View docs

Trusted by:

Caller verification for Salesforce Service Cloud

Confirm the real account holder before your agent actions the ticket, without leaving the case.

Verify the real account holder in seconds, without asking a single security question

Cut around 30 seconds off every call by replacing knowledge-based questions with one-tap verification

Close the social engineering and voice-cloning gap, with a timestamped audit trail on every check

What you get with Authsignal Call Connect

One-click verification from inside Salesforce, on the Case, Account or Contact record

A secure challenge sent to the customer's own device by SMS, email, WhatsApp or Slack

Customer approves with a passkey, biometric or one-time code on an Authsignal-hosted page

Clear Verified or Failed result on the record, updated in real time

Works for inbound and outbound calls, and can pre-verify from IVR before the agent picks up

Timestamped audit trail on every check for SOC 2, ISO 27001, HIPAA and PSD2/SCA

Security without slowing the call

Works inside the tools your agents already use

Call Connect runs inside Salesforce, listed on the AppExchange. The agent triggers the same one-click verification from the record they are already working in, following the identical flow and status model. The result is verified on the record at hand. No new console to learn, and no change to how your service team works.

Built for customer support, not generic login

This is not another way to add passkeys to Salesforce. It is caller verification for your support team. When a customer calls Service Cloud to recover an account, change details, or authorise a sensitive request, your agent confirms it is really them before touching the case. Knowledge-based questions are slow and a determined fraudster can answer them; a verification approved on the customer's own device cannot be talked around. Every check is logged for audit.

One layer across every channel

The contact centre is one touchpoint. The same Call Connect API verifies identity across IVR, chatbots and your web and mobile channels, so a customer gets a consistent experience wherever they reach you. A no-code rules engine lets your fraud and product teams adapt verification to new patterns without waiting on developers.

How Call Connect works in Salesforce

On the caller's record, the agent clicks Start Customer Verification, picks a channel (SMS, email, WhatsApp or Slack) and confirms the contact detail on file.

The customer receives a secure link on their own device, opens an Authsignal-hosted page describing the request, and approves with a passkey, biometric, or one-time code, or declines.

The record's status moves to Verified or Failed in near real time. The agent proceeds only once it shows Verified, and every step is logged for audit.

Verification can also be triggered from your IVR before the agent picks up, so the caller is already verified when the call connects.

“Implementing FIDO authentication through Authsignal has been a game-changer for our members’ digital experience. It’s secure, seamless and sets a new standard for trust in online banking.”

Herb Wulff

Treasury and Agency

Treasury and Agency Banking Manager

Partnering with Authsignal is simple and powerful

Start with a guided evaluation

Talk to our team to scope your contact-center flow and see Call Connect running in a live demo.

Available on Salesforce AppExchange

Install the Call Connect package for Service Cloud, with setup support from our team.

Dedicated solutions engineering

Access real-time support via private Slack or Teams channel for tailored advice from our engineering team.

Flexible options

Drop-in caller verification for production-grade security and compliance, without replacing your contact-center platform.

FAQ

Do I need to replace Salesforce or change how my agents work?

No. Call Connect installs from the Salesforce AppExchange and runs inside your existing org. Agents trigger the same one-click verification from the record they are already on, and see the result there. It drops into your existing stack with no migration.

How is this different from asking security questions?

Security questions are slow and rely on information a fraudster can find, phish, or talk their way around, and AI voice cloning now defeats voice checks too. Call Connect verifies the caller against something only the real account holder holds, a passkey or biometric on their own device. You cut handle time and close the social engineering gap at once.

Which channels and methods are supported?

The agent delivers the challenge by SMS, email, WhatsApp or Slack, and the customer approves with the strongest method their device supports, including passkeys (WebAuthn/FIDO2), biometrics, push, hardware keys, SMS or email OTP, and ID verification. A no-code rules engine decides which methods apply and when.

Can we verify the caller before an agent answers?

Yes. Verification can be triggered from your IVR so the caller is pre-verified when the call connects, or by the agent once the call is live. Both inbound and outbound patterns are supported, and the same Call Connect API also plugs into chatbots and other digital channels.

How quickly can we get it live?

Fast. Integration typically takes around a day, and most teams complete a proof of concept or pilot within two to five days. Install from the marketplace, connect it to your Authsignal tenant, and your agents can begin verifying callers.

Is Authsignal compliant?

Authsignal holds SOC 2 Type II and ISO 27001 certifications and offers a FIDO Certified passkey server. Deployments support HIPAA, GDPR and UK GDPR, and PSD2/SCA-aligned flows, with hosting in US, EU, AU and CA regions so data stays in your chosen region. Enterprise SLAs and DPAs are available.