Operations

Financial process automation: from the WhatsApp order to the invoice issued.

Orders come in however the customer likes and go out invoiced without anyone keying them in by hand.

Distribution and wholesale · high-volume ordering

Three colleagues reviewing a process together in a meeting room

The starting point

Customers ordered however they could. The system accepted one format only.

How orders came in

WhatsAppphoto of a handwritten list

Emailspreadsheet with 60 line items

Phone calldictated and written down

WhatsAppa two-minute voice note

Someone keyed it into the systemItem by item, checking code and price against the catalog.

340orders came in every day

3people transcribing full time

48 hbetween the order and its invoice

The bottleneck wasn’t selling or shipping: it was turning four ways of ordering into one way of recording. And every transcription was a chance to get a code, a quantity or a price wrong, which later showed up on the invoice.

How it runs

From reading the order to the issued invoice.

01Order intake
It arrives by WhatsApp, email or phone.
02Reading and structuring
It extracts customer, product and quantity.
03Validation against the catalog
Code, price and available credit.
04Entry into the system
The order enters the ERP already structured.
05Invoice and notice
It’s issued and the customer gets a copy.

What it uses from Shimli

The pieces behind process automation.

AI agents

They read the order however it arrives and return it structured.

How it was used here
They read the photo, the spreadsheet, the dictation and the voice note alike.
If a product isn’t in the catalog, they ask before entering it.
They confirm the order with the customer before it enters the system.

Orders · DistributionAgent · actionslive

leerPedidoReadExtract product, quantity and customer

validarCodigoDatabaseCheck every code against the catalog

aplicarPrecioDataApply the price agreed with that customer

revisarCreditoLogicVerify the available credit line

cargarERPActionWrite the structured order

Code InterpreterWeb Search

Flow Builder

The order’s journey, from intake to invoicing.

How it was used here
Trigger: a message arrives from a registered customer.
Branches by amount: above a threshold it goes through approval.
If the customer exceeds their credit line, the flow stops and raises a flag.

Flow canvas

Start

BranchContact · 5068…Contact · 5066…Else

AI AgentCrediAmigoDigital assistant · live

Databases

Catalog, prices and customers each line is validated against.

How it was used here
The catalog validates the code, not the memory of whoever types it.
Each order keeps its origin: channel, time and the original message.
Customer-specific pricing applies on its own.

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

The order enters the ERP and the invoice goes out the same way.

How it was used here
It writes the order into the ERP with the fields that system expects.
The invoice is issued in the usual system, not a new one.
The customer receives their copy through the same channel they ordered on.

CRM

Core

Bureau

FusionAI

AI Voice

SMS

API

POST /v1/agents/run200 OK

The outcome

What changes in internal operations.

01The order comes in however it arrives

The customer keeps ordering by WhatsApp, email or phone. The difference is nobody transcribes it anymore.

02The catalog validates, not memory

Code, price and credit are checked against the database before the order exists, not later on the invoice.

03Invoicing stops waiting

The invoice no longer depends on someone finishing yesterday’s typing queue.

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

The other three processes

The agent runs the same way on every one of them.

CollectionsFrom cold receivables to confirmed payment.See the case CreditFrom the incomplete file to a decision with everything in view.See the case SupportFrom the message queue to the reply that resolves.See the case

What people ask before getting started.

Straight answers on what Shimli is, what it costs, what it integrates with and who is behind it.

Shimli is a platform to build and run AI agents inside a company's operation. An AI agent is a program that understands the context of a conversation, queries the institution’s systems, decides within the policies defined for it and carries the task through to the end. It is built by Sheilim LLC, headquartered in Miami.

A chatbot replies from a script: it recognizes an intent and returns text written in advance. An AI agent understands context, analyzes information, executes tasks in the institution’s systems and escalates to a person when needed. A chatbot replies; an agent resolves.

One plan at $139 a month with every feature on the platform: there are no editions or tiers. It includes 3 human seats and 1 admin, 1 Flow Builder, WhatsApp, Facebook, Instagram and web connection, and unlimited WhatsApp templates. Added separately: an extra instance at $59 a month, an extra Flow Builder at $19, an extra human seat at $9, and AI usage at $49 per 2,450 queries. You can create the account and get into the platform yourself.

Let's build this same case
on your operation.

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

Design my operations case