Google MeetLive verification session
ZoomSessions on your video tool
WhatsAppSession link and reminders
SalesforceOutcome on the application
Google DriveCaptures stored with the case
SlackReviewer queue and alerts
Video 
KYC.Identity checked on video.Decided by your reviewer.
AI employees that run the video KYC session for account opening, loans and policies. They guide the customer, capture the document and face, check what they can and pass every identity decision to an authorised person on your team.
Trusted by teams at
One verification, start to finish.
Every step on the record.
The agent runs the session, captures and checks the evidence, and puts a complete case in front of your reviewer. Your reviewer decides.
Verification session- Hosted by
- Meera, Customer Onboarding
- Application
- Matched to session
- Consent
- Recorded before capture
- Recording notice
- Shown
On video · Account opening
Following your approved capture steps- Document read
- Clear
- Name
- Matches application
- Address
- Mismatch flagged
Not resolved in the session, so passed to the reviewer.
Reviewer queue- Document and face captures
- Attached
- OCR result
- Attached
- Address
- Mismatch flagged
- Identity decision
- With authorised reviewer
Loan application- Applied
- Verified
- Account opening
- Consent record saved
- Audit trail written
Invite and consent
The customer gets a session link for an eligible application. Consent is asked in the wording you approve and recorded before anything is captured.
Your procedure. Your reviewers. The agent runs the session the way your compliance procedure says. Identity decisions stay with the people you authorise. For other face-to-face conversations, see video agents.
Explore video agentsAuthority & handoff
The agent runs the session.
Your reviewer decides identity.
Starts with
An eligible application that needs identity verified, from your onboarding or lending system
Works toward
A complete case for review: consent, captures, check results and every flag, in one place
Leaves to people
The identity decision, account and loan approvals, and anything that looks like fraud
The agent owns
Run the verification session- Sending the session link and reminders
- Asking for and recording consent
- Guiding the document and face capture
- Reading documents with OCR
- Comparing details with the application
- Flagging mismatches and unclear captures
People keep
Authorised reviewers decide- Approving or rejecting identity
- Account opening and loan decisions
- Fraud determinations
- Exceptions to the procedure
- Consent wording and retention rules
Handed off with context
- 01Never approve identity without an authorised reviewer.
- 02Record consent before anything is captured.
- 03Flag a mismatch instead of resolving it by guesswork.
- 04Log every session with its captures, checks and decision.
One verification per journey
Real employees.
Real onboarding journeys.
- Google Meet & Salesforce
- Consent
- Recorded
- Document read
- Clear
- Face capture
- Captured
- Identity decision
- With reviewer
Bank account opening
Customers verified without a branch visit.
What the agent doesMeera invites the new customer to a session, records consent, guides the ID and face capture and puts the case in your reviewer’s queue.
What you can checkThe consent record, the captures, the check results and the reviewer’s decision on the account.
Salesforce & Snowflake- KYC documents
- Received
- Name match
- Matches application
- Fraud signal
- Held for review
- Disbursal
- Not started
Loan onboarding
No disbursal on an unverified file.
What the agent doesArjun chases the missing KYC documents and books the session. Neha screens the identity and fraud signals. Anything that does not clear is held for your fraud reviewer.
What you can checkThe documents on the application, the fraud screen result and who signed off.
Zoom & HubSpot- Session
- Held
- Consent
- Recorded
- Date of birth
- Mismatch flagged
- Policy issuance
- Awaiting reviewer
Insurance policy onboarding
Proposer verified before the policy is issued.
What the agent doesKavya qualifies the enquiry and books the verification session. The session captures the proposer’s ID and consent, and the case goes to your underwriting or compliance reviewer.
What you can checkThe proposal record, the consent and captures, and the reviewer’s decision before issuance.
How we set it up
Map your procedure.
Then run it on video.
- 01
Map the procedure
Walk through your current KYC procedure with your compliance owner: the documents, the consent wording, the checks and who is authorised to decide.
Scope gateApproved verification procedure and named reviewers - 02
Connect your systems
Connect the video tool, document storage, OCR and your lending or onboarding system with least-privilege access.
Connect gateReviewed access, retention and data-flow map - 03
Test hard sessions
Run clear sessions and difficult ones: blurred documents, mismatched details, dropped connections, consent declined.
Evaluate gateAcceptance record signed by compliance - 04
Go live in stages
Start with one product or one segment. Review every case and the audit trail, then widen the scope.
Release gateRollout, support and recovery plan
Systems & permissions
Connect the session and the system of record.
Video sessionHost the live session and guide the customer through capture.Recording notices, recording storage and who can join.Documents & OCRStore the captures and extract text from ID documents for checks.Storage location, access and retention period.Lending & onboardingRead the application before the session. Write the decision and audit trail after review.Field-level permissions and which statuses the agent may set.Risk dataRead the signals your fraud team uses to screen a file.Read-only scope and which signals hold a case.
Customer & reviewer channelsSend session links and reminders to customers, and cases to your reviewers.Consent, template approvals and reviewer routing.Regulatory requirements for video verification differ by market and product. Your compliance owner confirms the procedure during scoping, and the agent is configured to it.
Pilot evidence
Measure the sessions.
Audit every decision.
- Session log
- Sessions started
- Tracked
- Captures completed
- Logged
- Consent declined
- Recorded
Sessions completed
How many eligible applicants finished a session, and where the rest dropped off, against your baseline.
- Reviewer queue
- Evidence attached
- Verified
- Mismatches flagged
- Counted
- Time to decision
- Measured
Cases ready for review
Whether each case reached the reviewer with consent, captures, check results and flags attached.
- System write-back
- Decision
- Written back
- Reviewer
- Named
- Consent record
- Linked
Audit trail complete
Whether every decision, its reviewer and the consent record were written back to the system of record.
Agree the baseline before the pilot, then compare completed sessions, review-ready cases and audit completeness against it.
Buyer guidance
Choose the right kind of verification.
- Use document upload when…
Your procedure accepts uploaded documents alone and does not need a live session.
- Run video KYC with an agent when…
Your procedure needs a live session with guided capture, consent and a full audit trail, at more volume than your team can host.
- Keep a person on the session when…
Your procedure requires an official to conduct the session, or the customer needs help the agent cannot give.
- Build a custom workforce when…
Verification is one step in a longer journey across lending, fraud and onboarding systems.
Buyer & implementation questions
What to know before
you verify identity on video.
No. The agent runs the session, captures the evidence and flags mismatches. An authorised reviewer on your team makes the identity decision, and that decision is recorded with their name.
Requirements differ by regulator, market and product. Your compliance owner defines the procedure, the agent is configured to it, and you confirm the specifics with our team during scoping before anything goes live.
OCR reads the ID document, and the details are compared with the application. Unclear captures and mismatched details are flagged for the reviewer, not resolved by the agent.
Consent is asked in the wording your compliance team approves and recorded before any capture. If the customer declines, the session stops and the application is updated.
The reviewer’s decision, the consent record and the audit trail are written back to your lending or onboarding system. Captures are stored where your retention rules say.
Meera opens accounts and confirms KYC, Arjun takes loan applications and chases missing documents, Neha screens identity and fraud signals, and Kavya qualifies insurance enquiries. You can also define your own role.
Customer reviews
From conversations to completed work.
Voice AI for client work
“Using UnleashX gave our team the power to build voice AI agents that deliver real results for our clients. Every use case became faster to deploy and easier to scale.”
Which onboarding journeyis waiting on verification?
Bring one journey and your current procedure. We will map the session, the systems it touches and the business case.