Nametag Integration for Intercom

Overview

The Nametag and Intercom integration lets your support agents request identity verification from inside an Intercom conversation. The customer verifies with a government ID and a live selfie on their phone; the result (Verified, Failed, or Expired) posts back into the conversation as a tag, a status custom attribute, and an internal note. No customer personal data is ever stored in Intercom — only pass/fail status, a timestamp, and a link to the Nametag result.

Before you start

Have ready:

• A Nametag administrator account (you start here — you’re already signed in).
• An Intercom administrator who can authorize apps for your Intercom workspace.
• Any paid Intercom plan, with access to the Inbox.
• About 5 minutes.

You will not need to copy a Nametag API key into Intercom or an Intercom key into Nametag. The connection is established with Intercom’s standard OAuth consent.

Setup (from the Nametag console)

1. Open the catalog. In the Nametag console go to Integrations → Add integration and select Intercom.

2. Connect Intercom. Select Connect Intercom. You are taken to Intercom to authorize the Nametag app (standard Intercom OAuth consent). Approve the requested permissions and you return to the Intercom integration page, connected. Setup runs from Nametag; the Connect step authorizes Intercom — you never paste a Nametag key.

3. Choose coverage. Pick where the Nametag card is offered. The default is all inboxes.

4. Activate. Turn on Enable Intercom verification for this workspace and save. Nothing is offered to agents until you activate.

Using it (what your agents do)

In any covered conversation, an agent opens the Nametag card in the conversation details and clicks Request identity verification. The customer receives a secure one-time link in the chat. When they finish, the card shows Verified ✓ and the conversation is tagged (nametag-verified / nametag-failed) and annotated automatically. Train agents to proceed with sensitive actions only after they see Verified.

Managing the connection

From Integrations → Intercom you can view connection status, change coverage, enable or disable the integration, and disconnect. Disconnecting revokes the connector’s access to your Intercom workspace and hides the card.

Notes & limits

• Intercom conversations cannot be hard-blocked. Nametag shows an authoritative, visible status — the Inbox card, a tag, a custom attribute, and an internal note. Train agents to act on that signal.
• Verification requests expire after about 168 hours (7 days). After that the card shows Expired and the agent can re-request.
• No customer personal data is written to Intercom — only pass/fail status, a timestamp, and a link to the Nametag result.

Troubleshooting

• No Intercom card in the Inbox: confirm the integration is enabled and the conversation is in a covered inbox or team, that the Intercom app is installed, and that the agent has Inbox access.
• “Connect Intercom” fails: you must be an Intercom administrator able to authorize apps; retry the OAuth step.
• Status not updating: confirm the customer completed verification and the request has not expired.