Nametag in the Gartner® Magic Quadrant™ for Identity Verification. ->
Protect your helpdesk against deepfake impersonation by embedding Nametag identity verification inside of your existing Zendesk flows.
How to use it
Bring Deepfake Defense™ identity verification into ServiceNow with Nametag's turnkey integration. With just a couple clicks, agents can confirm who’s behind a support ticket, without ever leaving their current workflows.
Customers and employees verify themselves in seconds by scanning their government-issued ID and taking a selfie. Returning users can breeze through with Nametag’s patented express reverification, completing the process with only a quick selfie.
1. Integrate Nametag with Zendesk
Quickly integrate your Nametag tenant with your Zendesk tenant. Click a few buttons, fill in a few text fields, and you're all set.
You can choose exactly what information you ask users to provide, decide when it expires, and customize their experience with your logo and branding.
2. Verify users from inside Zendesk tickets.
When someone opens a ticket to request a high-risk action, such as an employee asking for a password reset, simply press a button to create and share a new identity verification link.
The person on the other end quickly scans their photo ID and takes a selfie. If they've verified themselves before, they just take a selfie thanks to our patented reverification technology.
See how Nametag verifies a person ->
Verification results update instantly inside of the same Zendesk ticket. Bad actors are surfaced to you, preventing account takeovers and other fraud, while agents can quickly move onto helping legitimate users resolve their issues.
3. Prevent fraud and accelerate resolutions.
Behind the scenes, Nametag's workforce-grade Deepfake Defense™ engine uses cryptography, biometrics, AI and other to verify their identity with unmatched assurance.
Learn more about Deepfake Defense™ ->
Deepfake Defense is the only engine built to combat modern, AI-powered impersonation.
Use Nametag + Zendesk when you really need to know who's behind a ticket, such as:
