The Nametag Identity Verification for the ServiceNow application enables support teams to securely verify the identity of people directly within ServiceNow. This integration helps prevent account takeovers, social engineering, and deepfake impersonation attacks, while streamlining support workflows and protecting user privacy.
Support agents can initiate a verification request from any ServiceNow ticket. End-users take a selfie and scan their government-issued photo ID. Nametag validates and compares them using its Deepfake Defense™ engine. Verification results are automatically updated in the ServiceNow Incident or Interaction record, giving agents the confidence to securely reset passwords or MFA, grant access to sensitive data, and authorize account changes.
By reducing reliance on phishable one-time passcodes or guessable security questions, Nametag helps teams increase security, efficiency, and user satisfaction.
Benefits include:
Protect Support Workflows and Accounts
Prevent account takeovers and impersonation attacks by ensuring you know exactly who you are supporting. Nametag’s advanced verification prevents common threats such as deepfake impersonation and Scattered Spider–style social engineering attacks.
Streamline Identity Verification in ServiceNow
With a few clicks, agents can send a Nametag request directly from ServiceNow tickets. Verification results sync automatically, reducing manual steps and eliminating back-and-forth with end-users.
Balance Security with Privacy
Nametag’s industry-leading privacy controls allow organizations to verify identities without compromising user trust. Data is handled securely, and only the minimum required information is shared.
Improve Efficiency and Lower Costs
Automating identity verification shortens resolution times and reduces operational costs by freeing agents from lengthy manual verification processes.
Nametag Identity Verification for ServiceNow enables authorized agents to request ID-and-selfie verification from Incident and Interaction records in Classic UI and Service Operations Workspace. Agents can add a verification link to the ticket or choose SMS or WhatsApp delivery when those channels are enabled for their Nametag environment. Request ID, verification status, name-match result, links, timestamps, and Verification History appear on the ticket. Agents can check status and cancel an in-flight request. The API key is held in ServiceNow Connections & Credentials. A verification is always started by an agent selecting Create Verification Request; saving a ticket or selecting a Password Reset category never creates a request.
What is included in 2.1.76
Version 2.1.76 replaces the 2.1.64 submission and responds to the certification review. Deprecated flows, script includes and legacy actions from earlier releases are restored as inactive records instead of being deleted, and the package carries only two deletion records (superseded Incident form sections), down from 223. Five legacy Incident and Interaction columns remain as inactive entries so that an upgrade cannot destroy customer data. Verification state and history remain stored exclusively in Nametag-scoped tables.
Since 2.1.64 the release also includes: stricter country-code (E.164) phone-number validation for SMS and WhatsApp; duplicate-request protection for Create and Cancel; more reliable refresh after Create, Get Status and Cancel in Classic and Service Operations Workspace; the Nametag Identity Verification Records list in the Classic agent menu; Incident related-list tabs in Service Operations Workspace keep their selection; and a tightened access model for verification records.
Upgrade notes
Use the standard ServiceNow application upgrade path. Preserve the instance-local Nametag Environment ID, credential alias, API key credential, and required agent/admin role assignments. When you preview an upgrade from the 2.0.0 listing you may see two deletions (the superseded Incident Details and Work Notes sections of the Nametag Verification view); everything else from earlier releases is kept as inactive records. After the upgrade, run the integration test and the Classic/SOW Incident and Interaction smoke tests in the Installation Guide.
ServiceNow release: Yokohama or Australia (the releases selected as compatible in the Store listing). Service Operations Workspace must be present for SOW features; Classic features do not require SOW.
Application scope: x_namet_nametag_se.
An administrator configures the integration. Agents need their normal Incident or Interaction access; x_namet_nametag_se.agent exposes the Nametag application menus, while x_namet_nametag_se.admin is required for Integration Settings.
A Nametag environment with the ServiceNow integration enabled is required.
Other Requirements:
Nametag License & API Credentials (Environment ID and API key from the Nametag Console).
Outbound HTTPS access from the ServiceNow instance to https://nametag.co.