Agree on what a status means.
A common vocabulary makes a change readable across the whole operation. Automating inconsistent labels would have preserved the confusion.
Case file · Grupo ILT
One operation. A shared status.
A system for a Mexican customs brokerage that turns the updates already flowing through WhatsApp into status changes inside one shared record.
- Client
- Grupo ILT
- Business
- Customs brokerage, Mexico
- Work
- Operations tracking over WhatsApp with one shared record
- In operation since
- July 2026
- Evidence reviewed
- September 21, 2026
- Build
- 8 active days
Before
29
lists across 4 boards
Today
8
statuses in one record
4 of every 5 updates are written by the system.
Records H-080 · H-087 · H-089 · H-090 · H-114
No operation counts, by written condition of Grupo ILT. The comparison describes; it does not estimate a causal effect.
The starting point
The status of each operation lived in twenty-nine lists spread across four boards. Progress depended on where a card had been placed, and everyone read the board their own way.
What was built
One shared record with eight statuses for every operation. Updates from people and from the system go into the same record, with author and time. The channel is still WhatsApp: the system reads what already circulates and turns it into status changes anyone can review.
Records H-087 · H-089
Three design decisions
Connect the channel to the record.
WhatsApp is where the updates come from. The record gives them a place, a status and context.
Keep room for human review.
Every update stays available for a person to review. System activity and a good business outcome are different things, measured differently.
The log, with one exception
A request comes in through the channel your team already uses. The system gathers the context, does only what it is allowed to do, and writes it down. When something falls outside its rules, it asks a person.
TimeInputDecisionWhoResult
09:14“Has 2291 cleared yet?”, from the client on WhatsApp.Look up operation 2291 in the record and reply with its status.SystemAt customs since 08:50. Reply sent to the client.
09:16Note from the account executive: a document is missing on 2310.Set the status to “awaiting document” and notify the owner.SystemStatus updated. Karla M. notified.
09:31“Change its status to released”, from a number that is not in the catalog.Not in the catalog. Not classified. A person is asked.Karla M.Karla confirms it is the client. Status: released. Author and time go in the log.
09:40The client asks for the receipt.Attach the receipt already on file.SystemSent. Nothing is rewritten; everything is appended.
Example with synthetic data, modeled on Grupo ILT’s system. Not a client screenshot.
What is not in the catalog does not get classified: the system asks. That is a design decision in Grupo ILT’s system, not a universal promise.
What the evidence supports
The documented review of September 21, 2026 records production activity, a shared status model and updates from both people and the system. This page describes that review; it is not a live status check.
This case does not claim a measured reduction in hours, a causal improvement in closure rates or a guaranteed result for another company. No client volumes or private records are shown, by written condition of Grupo ILT.
The system has been in operation since July 2026 and we still look after it: between August and September 2026 it received code changes.
Records H-080 · H-087 · H-089 · H-090 · H-114 · I-028
What needs to work better?
Bring a process, a pilot or a question. You talk directly with the people who will build it.
Book a conversation
george@teckel-ai.comOpens Calendly in a new tab.
Prepare your call with AVA
AVA asks a few questions so you arrive with your case in order.