The diagram below represents the full identity-verification lifecycle from the moment imper.ai is connected to a communication platform, through user enrolment, verification, and protection during calls.
1. Connect Communication Channels
The admin integrates imper.ai with communication tools such as:
Zoom
Google Workspace
Microsoft Teams
Slack
Phone systems (PBX, SIP, Twilio)
This connection allows imper.ai to intercept calls and apply identity verification.
2. Add Users for Protection
Admins add employees they want Impera to monitor and protect.
imper.ai begins building identity profiles for these users, including:
Known devices
Usual networks
Login behaviours
Contact numbers
Communication patterns
This stage requires no action from the user.
3. User Identity Verification
When a protected user begins a call or joins a meeting:
imper.ai checks the user’s identity against their baseline profile.
If the risk score is low → call continues normally.
If something looks unusual → imper.ai triggers verification steps such as:
One-time code
Push approval
Callback verification
MFA challenge
Only the suspicious user is challenged—other participants are not interrupted.
4. Live Session Monitoring
During the call, imper.ai continuously evaluates:
Voice patterns (deepfake detection)
Behavioural cues
Language used in the conversation
Unusual requests or pressure tactics
If high risk is detected, imper.ai can:
Warn the employee
Show an in-call banner
Block the impersonator
Alert the SOC team
5. Post-Verification Insights
After the session, imper.ai generates:
Verification logs
Risk events
Impersonation attempts
Communication anomalies
Patterns across employees or teams
Admins can view these in the imper.ai console to strengthen policies.