Credit

From the incomplete fileto a decision with everything in view.

The agent collects and validates documentation over chat, assembles the file and hands it to the analyst ready to decide.

Consumer lenders and savings cooperatives

An analyst reviews the printed documentation of a credit application
The starting point

The credit decision takes minutes. What took days was gathering the paperwork to make it.

What reached the analyst

  • ID documentWhatsAppblurry photo
  • Proof of incomeEmailarrived 3 days later
  • Utility billnever arrived
  • Bank statementWhatsAppexpired 4 months ago

Four documents, three channels and no way to know what was missing without opening them one by one. The file wasn’t held up by judgment: it moved at the speed of paperwork.

How it runs

From the application to the file in the analyst’s hands.

  1. 01Application intake

    It arrives over WhatsApp or web and opens the case.

  2. 02Documents, one by one

    It asks one by one and stops if one is illegible.

  3. 03Reading and validation

    OCR extracts, checks validity and cross-checks.

  4. 04File assembly

    Documents, data and bureau in a single record.

  5. 05Handoff to the analyst

    The case arrives complete; failures are flagged.

What it uses from Shimli

The pieces that make this case work.

AI agents

They request, review and ask again when a document isn't legible, without anyone having to chase.

  • How it was used here
  • It requests one document at a time and won’t move on until it arrives legible.
  • If the photo is blurry or cropped, it explains what’s missing and asks again.
  • It answers requirement questions without taking an analyst’s time.
CrediAmigoAgent · actionslive
buscarUsuarioDatabaseLook up the customer by ID
clasificarUsuarioLogicClassify the credit level
requisitosDataValidate approval requirements
aprobacionLogicConditions to approve credit
cuotaMensualComputeCompute the monthly payment
Code InterpreterWeb Search

Flow Builder

Each document is a step with its own validation; the flow won't advance if one fails.

  • How it was used here
  • Four steps, one per document, each with its own validation.
  • The bureau isn’t queried until all four pass.
  • If a field doesn’t match the database, the case is flagged before it reaches the analyst.
Flow canvas
Start
BranchContact · 5068…Contact · 5066…Else
AI AgentCrediAmigoDigital assistant · live

Databases

The file lives in its own structure, with the fields the credit committee requires.

  • How it was used here
  • The fields are the ones the committee already used, not generic ones.
  • Each document is linked to the applicant and to its expiry date.
  • The analyst opens one record, not four scattered conversations.
Databaseoptica · crediamigo Edit structure
NamePhoneIDAmountStatus
Cliente 01+504 ····0801-····$75,000active
Cliente 02+504 ····0501-····$75,000active
Cliente 03+504 ····1623-····$75,000review
Cliente 04+504 ····0107-····$75,000active

Integrations & API

Bureau queries and core writes, without replacing the systems already running.

  • How it was used here
  • The bureau query fires from the flow, without leaving the case.
  • The approved file is written to the core with the fields already validated.
  • The core remained the source of truth: nothing was migrated.
CRM
Core
Bureau
WhatsApp
FusionAI
AI Voice
SMS
Email
API
POST /v1/agents/run200 OK
The outcome

What changes in the operation.

01The file arrives complete

The analyst opens the case and has everything: legible documents, verified data and the bureau query already run.

02Nothing moves forward half-done

The flow stops at the missing document instead of dragging the gap all the way to the end of the process.

03The analyst decides, doesn't chase

The team's time goes into assessing risk, which is the part that can't be delegated.

This case describes how the agent operates on the process. Result figures are defined with you during discovery, against your own indicators.

Common objections

What teams usually ask before getting started.

Straight answers to the most common questions from credit, collections and technology teams.

Shimli isn't a chatbot. It's a platform to build AI agents that understand context, analyze information, execute tasks in your systems and escalate to a human when needed. A chatbot replies; an agent resolves.
The agent never decides out of bounds. It operates under policies, rules and guardrails defined by your institution, and the final decision can still be human. You define what it can and cannot do.
No. You can start with a controlled pilot and connect progressively via APIs. Shimli doesn't require replacing your current systems, it integrates on top of what you already have.
The next step

Let's build this same case
on your operation.

We review your credit process, identify where the agent fits and define with you the indicators we're going to move. No commitment, nothing to install.

From $139 a month, with a 14-day trial and self-serve setup. See pricing