Understanding Sessions

What a session is, how its status is determined, and what the possible outcomes are

A session is a single, unique instance of a journey completed by one user. Every time someone opens a journey link and goes through the verification steps, a new session is created.


Session lifecycle

A session goes through several states during its lifetime:

StateDescription
CreatedThe session has been generated but the user hasn't opened the link yet
SentThe session link has been sent to the user (via email, SMS, or shared manually)
StartedThe user has opened the link and begun the journey
ProcessingThe user has completed all steps and the AI is analysing the submitted documents
CompletedThe AI has finished analysing and a verdict has been assigned
ExpiredThe session link expired before the user completed the journey
AbandonedThe user started but did not finish the journey

Session verdict

Once all documents and checks in a session have been processed, the AI assigns an overall verdict. This verdict determines the colour indicator you see in the back office.

Possible verdicts

VerdictColourMeaning
AI Approved🟒 GreenAll documents and checks passed β€” the session is fully verified
To Review🟑 YellowOne or more documents could not be fully verified and need manual review
AI RejectedπŸ”΄ RedOne or more documents failed verification
User Approved🟒 GreenAn analyst manually approved the session
User RejectedπŸ”΄ RedAn analyst manually rejected the session

How the verdict is calculated

The overall session verdict is determined by the worst-case outcome across all documents and checks in the session. The rule is simple:

  1. If any document is rejected β†’ the session is rejected (red)
  2. If no document is rejected, but one or more need review β†’ the session is to review (yellow)
  3. If every document is approved β†’ the session is approved (green)

More precisely, the system evaluates every analysis node (identity document check, biometrics, document collection, etc.) and applies this priority:

user_rejected > ai_rejected > verify > user_approved > ai_approved
  • If any node has user_rejected β†’ session = User Rejected
  • Else if any node has ai_rejected β†’ session = AI Rejected
  • Else if any node has verify β†’ session = To review
  • Else if all nodes are user_approved β†’ session = User Approved
  • Else if all nodes are ai_approved β†’ session = AI Approved
  • Otherwise β†’ To review

In short: one red result makes the whole session red. Everything must be green for the session to be green. Anything in between is yellow.

End node override

The journey designer allows you to configure the End node with a forced result. When set, the end node overrides the calculated verdict:

End node settingForced verdict
AutomaticNo override β€” the verdict is calculated from the checks (default)
CompliantForces the session to AI Approved regardless of individual results
Non-compliantForces the session to AI Rejected regardless of individual results
To reviewForces the session to To review regardless of individual results

Individual document statuses

Each document or check within a session has its own status, determined by the AI controls that ran on it:

StatusMeaningHow it's determined
AI ApprovedAll AI controls passedEvery control returned true
To reviewThe AI could not make a definitive determinationOne or more controls returned null (inconclusive), but none returned false
AI RejectedOne or more AI controls failedAt least one control returned false
PendingThe document is still being processedAnalysis has not completed yet
CollectedThe document was collected but not analysedUsed for document collection steps that don't run AI checks
ErrorAn error occurred during processingThe analysis could not be completed

After the AI assigns a status, an analyst can override it manually:

StatusMeaning
User ApprovedAn analyst reviewed the document and approved it
User RejectedAn analyst reviewed the document and rejected it

Multiple documents per node

When a journey step allows multiple submissions (e.g. the user retries after a poor photo), the system keeps all submissions and picks the one with the highest priority status for that node:

user_rejected > user_approved > ai_approved > ai_rejected > verify

This means a manual decision (user approved/rejected) always takes precedence over the AI verdict.


Viewing session results

Session results are visible in the back office under Analysis β†’ By session. Click on any session to see:

  • The overall verdict and colour indicator
  • The status of each node (document check, biometrics, etc.)
  • The extracted data and AI controls for each document
  • The audit trail of all actions taken

See Journey Sessions for how to create, share, and review sessions from the back office.


What’s Next