Validation with photo (Flows)

Version: always use the latest available version

This agent lets you run a complete identity verification within WhatsApp Flows, combining photo liveness check, document validation, and facial comparison.

This agent blocks the use of documents from the gallery or files, preventing fraud.

Prerequisites

✅ Checklist to start without blockers

You must have a verified WhatsApp account.
You must have a Terms and Conditions PDF (public URL) to configure in the agent. This is mandatory.
The user must be able to take photos from the chat (camera permissions must be enabled on the device).
Recommended: define the handling flow if you enable Human in the loop (who reviews, response times, and what happens if there is no response).

How does it work?

In less than 1 minute, the user completes the following steps:

Take a photo of their face

Using the front camera, the user takes a photo of their face. Access to the photo gallery or documents is blocked.

Capture photos of their identity document

Front and back photos of the identity document are requested to validate validity and authenticity. Access to the photo gallery or documents is blocked.

Automatic facial comparison

The system applies the 1:1 technique, comparing the photo with the image on the document (or with the official government source if enabled).

Threshold configuration, expiration, and error handling depend on each stage of the flow.

How is the agent composed?

The Biometrics Agent (Flows) is made up of three specialized agents:

Liveness check agent with WhatsApp Flows - Validates the person’s liveness via photo: confirms there is a single face, detects recaptures, and evaluates fraud attempt signals.
Document verification agent - Verifies the authenticity and validity of the document, detects recaptures, and evaluates fraud attempt signals.
Facial comparison agent - 1:1 facial comparison between the photo and the face from the document/government entity. As a result it delivers a match percentage and binary status (approved/rejected) according to the configured threshold.

If you only need to implement part of the process (for example, document only), see the configuration in Agents by stage.

Connection from Marketplace

Access the platform

Go to apps.jelou.ai. On the home screen you will see Brain Studio and Connect. In Brain Studio, select Marketplace.

Find the agent in Marketplace

In Marketplace you will see three tabs: Catalog, Installed, and Developers. Click on Developers and use the search bar to find Biometrics flows agent. Then click the download icon to install it.

Confirm the installation

If the installation was completed successfully, you will see the Installed tag in green.

Open the agent in Brain

Go to Brain. In the sidebar you will see your installed skills and tools. Search for Biometrics flows agent and click to open it: the node will load in your canvas.

Initial configuration

Click on the node, open Advanced settings (at the bottom), and select the agent version.
None of the inputs (except the PDF) require changes if you will use the default values. If you need to change them, you can enter them in the corresponding field.
If you want to modify any input, configure them in the sidebar.

Configure Outputs

This agent has 10 error outputs and 1 success output. Each can be directed to:

A text input with a custom message.
Connect, only if you have this module.

Run tests

With the configuration you just completed, you can proceed to run tests using a skill or another agent as a precursor.

Important: The “Terms and Conditions PDF” field is mandatory. The document must explicitly include the use, storage, and handling of personal and biometric data. It must be presented and accepted before starting the verification process.

Configuration

Inputs
Outputs

Maximum biometrics attempts

number

default:"2"

Variable: maxBiometricAttempts. Available values: 1-4

Notification email for exceeded retries

string

Variable: customerServiceEmail. Alert email when attempts are exceeded.

Accepted threshold for facial comparison

number

default:"60"

Variable: facematchThreshold. Available values: 55-95 Minimum approval percentage for facial comparison.

Verify document expiration date

Verify expiration date

string

default:"false"

Variable: dateExpiracyCheck. Available values: false, true Enables document validity control.

Enable government validation

boolean

default:"false"

Variable: flagGovValidation. Available values: false, true Defines whether an official source is queried.

Enable terms and conditions

boolean

default:"false"

Available values: false, true Set to “true” to load the terms and conditions URL

Terms and conditions PDF (mandatory)

string (URL)

Variable: termsAndConditionsPdf. Public URL of the terms and conditions PDF. It must explicitly detail the handling of personal data, including the use, storage, and processing of biometric information. It must be shown to the user before starting the process.

Enable Human in the loop

boolean

default:"false"

Variable: enableHumanInLoop. Available values: false, true Indicates whether the review process with a human agent is activated. Add-on service with additional cost.

Edit flow images

boolean

default:"false"

Variable: validateImage. Available values: false, true Allows replacing default images. When editing is enabled, five fields are displayed to integrate custom images. The step-by-step guide for customization is found in the “Customization” section.

Success

Biometric Validation Approved

Biometric validation has been completed successfully. Variable: biometricVerificationSuccess Response structure (JSON)

{
  "response_document_check_success": {
    "document_check": {
      "verified_fields": {
        "...": "Main document data"
      },
      "secondary_fields": {
        "...": "Secondary document data"
      },
      "details": {
        "...": "Document type details"
      },
      "image_quality_details": {
        "...": "Image quality details"
      },
      "images_extracted": {
        "...": "Images extracted from the document"
      },
      "gov_entity_fields": {
        "document_number": "Identity document number"
      }
    },
    "gov_entity_data": {
      "...": "Data obtained from the country's government entity"
    },
    "document_image_front_url": "URL of the front image of the document",
    "document_image_back_url": "URL of the back image of the document",
    "document_face_image_url": "URL of the face photo from the document"
  },
  "response_liveness_success": {
    "result": "true/false",
    "url_selfie_image": "URL of the photo obtained to validate liveness"
  },
  "result_facematch": {
    "facematch_result": "Facematch result (e.g. `approved` or `decline`)",
    "facematch_confidence": "match percentage"
  },
  "reporte_de_biometria": {
    "report": "URL of the generated biometrics report",
    "report_pdf": "URL of the generated biometrics PDF report"
  }
}

Important fields:

response_document_check_success: Identity document information
response_liveness_success: Photo submitted to validate liveness
result_facematch: Facial comparison result
reporte_de_biometria: Report URLs in web and PDF format

JSON response variable definitions: response_document_check_success:

document_check: Object with all extracted and validated document information
verified_fields: Main verified fields of the document (names, surnames, dates, etc.)
secondary_fields: Secondary fields extracted from the document
details: Details of the recognized document type
image_quality_details: Results of the image quality validations
images_extracted: URLs of images extracted from the document (portrait, signature, etc.)
gov_entity_fields: Fields used to validate against the government entity
gov_entity_data: Data obtained from the country’s government entity (varies by country)
document_image_front_url: URL of the front image of the document
document_image_back_url: URL of the back image of the document
document_face_image_url: URL of the face photo extracted from the document

response_liveness_success:

url_video_liveness: URL of the video selfie submitted by the user during the liveness check
url_selfie_image: URL of the frame extracted from the video used to validate liveness

result_facematch:

facematch_result: Facial comparison result (approved if matched, decline if not matched)
facematch_confidence: Comparison confidence percentage (0-100)

reporte_de_biometria:

report: URL of the biometrics report generated in web format
report_pdf: URL of the biometrics report generated in PDF format

Errors

Service Error

A problem occurred with the service. Variable: serviceError

Document Validation Unsuccessful

The user’s document could not be validated. Variable: documentCheckError

Terms and Conditions Not Accepted

The user has not accepted the terms and conditions required to continue. Variable: termsNotAcceptedError

Process Abandoned

The user abandoned the process. Variable: userExitProcess

Error saving to Datum

An error occurred while creating or updating the record in Datum. Variable: datumError

Liveness check unsuccessful

The user’s liveness could not be detected. Variable: livenessError

Facial Recognition Verification Error

Facial recognition verification has not been completed successfully. Variable: facematchError

Time Expired

The time to complete the process has expired. Variable: timeExpiredError

Error flow public validation

Error integrating the public key in the channel because a key is already configured. Variable: error_flow_public_validation

User Blocked

User Blocked. Variable: userBlocked

Report

By default a database called “Biometrics Agent Report” is created with the following fields:

Field	Description
Biometrics Code	Unique process identifier
Date and Time	Verification timestamp
Biometrics Result	Final process status
Identification Number	User’s document
Identification Type	Document type
First Names	User’s first names
Last Names	User’s last names
Date of Birth	Date of birth
Phone	User’s phone number
Email	Email address
Liveness Check Result	Liveness check status
Selfie Photo	URL of extracted photo
Document Check Result	Document validation status
Front Document Photo	URL of front image
Back Document Photo	URL of back image
Face Photo on Document	URL of document face photo
Government Entity	Entity queried
Facematch Result	Facial match percentage
Biometrics Report	Web report URL
Failure Description	Error details (if applicable)
Observations	Additional notes

The biometric report is available for download in PDF format and contains all the information detailed in the table.

Customization

You can customize only the images that appear on each screen; the rest of the flow copy is not customizable.

On the flow screens, fields marked with a yellow box are customizable. The remaining texts cannot be modified.

General view of the biometrics flow in Flows with yellow boxes on the customizable fields

General view of the document flow in Flows with yellow boxes on the customizable sections

Frequently asked questions

Does the agent respond if I don't enter data in any field?

Yes, the agent can respond because all fields have default values. However, selecting the agent version is mandatory; we recommend always selecting the latest available public version.

What documents are needed during the biometric process?

Photos of the identity document from both sides are required: front and back.

Is it possible to skip any step in this agent?

No. This agent is designed as a complete flow: photo + document + facematch. If you only need part of it (for example, document only), you must install the agents by stage.

Can I customize the texts in this agent?

No, you cannot modify the interaction texts. You can add messages, conditionals, and other customizations in your skill on the canvas.

What happens if I enable 'Human in the Loop (HIL)'?

HIL is an add-on service with an additional cost. When active, some cases may go to manual review (for example, if the threshold is not reached or attempts are exhausted). In this agent, manual review is applied after document validation.

What security measures does this agent apply?

Encryption in transit and at rest.
Evidence recording with hashes to ensure integrity.
Access control with roles (RBAC) and MFA.

How many attempts does the user have before being blocked?

It depends on your configuration:

Maximum biometrics attempts (maxBiometricAttempts): controls biometrics attempts.

Getting Started

AI Agents

Brain

Nodes

Databases

Variables

Tools

Functions

Configuration

Marketplace

Enterprise

Billing

Validation with photo (Flows)

Prerequisites

✅ Checklist to start without blockers

How does it work?

How is the agent composed?

Connection from Marketplace

Configuration

Success

Errors

Report

Customization

Frequently asked questions

Getting Started

AI Agents

Brain

Nodes

Databases

Variables

Tools

Functions

Configuration

Marketplace

Enterprise

Billing

​Prerequisites

​✅ Checklist to start without blockers

​How does it work?

​How is the agent composed?

​Connection from Marketplace

​Configuration

​Success

​Errors

​Report

​Customization

​Frequently asked questions

Prerequisites

✅ Checklist to start without blockers

How does it work?

How is the agent composed?

Connection from Marketplace

Configuration

Success

Errors

Report

Customization

Frequently asked questions