Why replace challenge questions
Security questions and “tell me your employee ID” can be researched or socially engineered, and they put the agent in the position of judging an answer. With TruU IDV the agent never sees the evidence. The caller proves who they are on their own device, against your directory, and the agent sees the outcome.How it works
- The caller asks for help. The agent finds them by name or email.
- The agent sends a verification link by email or SMS to a contact already on file, or copies it to share in chat.
- The caller opens the link on their phone and completes the flow the Helpdesk use case assigns them.
- The agent watches the request move to Verified (or not), then proceeds with the reset.
Before you start
- A connected directory. See Connect your directory.
- A flow suited to callers. The Standard Corporate template (Face, then Proofing, then SMS + Knowledge) is a good start. See Flows and templates.
- Agents invited with the Agent or Admin & Agent seat. See Team and roles.
Set it up
1
Route the Helpdesk use case
In Use Cases → Helpdesk, set Everyone (or Everyone else) to your caller flow. Add rules above it for groups that need something different, for example a stricter flow for administrators. See How use cases work.
2
Choose what happens after
Under When it ends → Passed, keep Report only if agents do the reset themselves, or choose Issue a Temporary Access Pass or Ping re-enrollment to automate it.
3
Pick where agents work
Agents can send verifications from any of these. You can use more than one.

