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's new since 2.0.0
Version 2.1.78 expands supported ServiceNow releases through Zurich and improves the Nametag verification experience in Classic UI and Service Operations Workspace.
Highlights
• Send verification links through the ticket, SMS, or WhatsApp when those channels are enabled for your Nametag environment.
• Cancel an in-flight verification and refresh request status more reliably after Create, Get Status, and Cancel.
• View request ID, verification status, name-match result, timestamps, links, and Verification History on Incident and Interaction records.
• Validate SMS and WhatsApp phone numbers using stricter E.164 country-code and length checks.
• Prevent duplicate Create and Cancel requests.
• Access Nametag Identity Verification Records from the Classic agent menu.
• Keep the selected Incident related-list tab in Service Operations Workspace.
• Use a tightened access model while verification data remains in Nametag-scoped tables.
Upgrade notes
Use the standard ServiceNow Store upgrade path. Existing Nametag environment and credential configuration is preserved, and no additional data migration is required. After upgrading, run the integration test and the Classic and Service Operations Workspace smoke tests in the Installation Guide.
Supported ServiceNow releases: Zurich, Australia, and Yokohama.
Service Operations Workspace must be installed for SOW features; Classic features do not require SOW.
Application scope: x_namet_nametag_se.
Required roles:
• Administrators: x_namet_nametag_se.admin
• Classic agents: x_namet_nametag_se.agent
• Service Operations Workspace agents: x_namet_nametag_se.agent, itil, and sn_sow.sow_user
These roles supplement ServiceNow's normal Incident and Interaction permissions. They do not grant access to tickets a user cannot otherwise read.
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.