How to verify a customer's identity in Zendesk before an account change
By Jake Marsh · Updated
To verify a customer's identity in Zendesk before a sensitive change, send them a Persona or Onfido check from the ticket with Whowell, and make your process wait for the whowell_approved tag. Whowell tags each ticket with the newest verification's result and, on approval, sets the requester's "Whowell: identity verified on" date. Views and triggers can then hold 2FA resets, payout changes or ownership transfers until the check passed.
Why email alone isn't enough
A display name and even a familiar address can be spoofed, and "it's me, I lost my phone" reads the same from the real customer and from an attacker. A document and selfie check through your identity vendor answers who is asking, on the vendor's own page.
The flow, end to end
- Agent sees a sensitive request: reset 2FA, change the bank account, transfer ownership.
- Agent sends a verification link from the Whowell sidebar with the right flow, such as "Account recovery" or "Payout change", using Send verification link and Create link and add to reply.
- Ticket gets
whowell_pendingwhile the link is sent, in progress or completed without a decision. - Customer verifies on Persona's or Onfido's page.
- Result lands on the ticket as an internal note and one tag: approved, declined, needs review, failed or expired.
- Agent acts only on approved. For needs review, your fraud or compliance team decides in the vendor's dashboard, linked from the note.
Tags and fields you can build on
| What | Values | Use |
|---|---|---|
| Ticket tag | whowell_pending, whowell_approved, whowell_declined, whowell_review, whowell_failed, whowell_expired | One at a time, following the newest verification. Triggers, views, reports |
| User field "Whowell: identity verified on" | A date, set on approval | Know who was verified and when, across tickets |
Record the approval date on the user is on by default; turn it off if you only want ticket tags.
Example setups
- A view of approved payout changes. Tickets with your payout tag and
whowell_approved, so the payments team only works verified requests. - A view of pending checks. Tickets tagged
whowell_pending, so agents can follow up or send a new link. - A review queue. A trigger that assigns tickets tagged
whowell_reviewto the group that reviews identity results. - Recent verification. A view of payout-change tickets where the requester's verified-on date is within the last 30 days.
Build these with Zendesk's own triggers and views; the tags and the date field are ordinary Zendesk data.
Limit who can send links
| Setting | Default | What it does |
|---|---|---|
| Who sees verifications | agent | Who sees the sidebar. Admins always see it |
| Who may send links | agent | Who may send, resend and cancel links. Everyone else sees statuses only |
| Link lifetime (hours) | 24 | 1 to 720 hours |
Values are comma separated: agent (everyone), admin, custom role ids or group:<id>.
When the link expires or is lost
Click Send a new link. With Persona, the same inquiry reopens; with Onfido, a new run starts for the same applicant. Cancel link stops a Persona link sent by mistake.
What stays out of Zendesk
No document images, selfies, ID numbers, dates of birth or addresses. Whowell keeps ids, statuses, the flow name, who sent the link and its expiry in a hidden ticket field (at most 20 per ticket), and never keeps the link itself.
What it costs
Whowell is $129 per Zendesk account per month with every feature, billed monthly by Zendesk with a 14-day trial. Verification fees are billed by Persona or Onfido. The Whowell setup guide has every setting.
Whowell
ID verification links from Persona or Onfido: send from the ticket, see pass or fail. $129/account. $129 a month per Zendesk account.
Questions
How do I verify a customer who emails in without an account?
Send the Whowell link to their email in the reply. They verify with a document and selfie on the vendor's page, so they don't need a login with you.
Can a trigger block an agent from acting until the check passes?
Triggers can route, tag and notify based on whowell_approved. The change itself still happens in your own systems, so make "approved on the ticket" part of the agent's process.
What if the customer is declined?
The ticket gets whowell_declined and a note with the vendor's reason codes and a dashboard link. Handle it under your own policy.
Does Whowell replace my identity vendor?
No. You need your own Persona or Onfido account with a template or workflow ready.
More Whowell guides
- How to send an Onfido verification link from a Zendesk ticket
- How to send a Persona verification link from a Zendesk ticket
More Zendesk guides
- How to bulk delete suspended spam tickets in Zendesk safely (Winnowell)
- How to find your Mirakl shop API key and API host for Zendesk (Wharfwell for Mirakl marketplaces)
- How to load discount codes into Zendesk from a CSV file (Vouchwell)
- How to find duplicate users in Zendesk (Twinmend)