Skip to content

Anonymized operational case

Route orders stopped living on personal phones

A food distributor sells to restaurants, hotels and neighborhood stores along fixed delivery routes. Orders arrive on WhatsApp at any hour, and usually the night before the route runs.

Review a similar operation See all cases

Evidence status

Anonymized operational case

Page published August 27, 2026.

This page describes an operation documented by Meteor without disclosing the client’s identity. It is not a review, does not attribute percentage outcomes and does not present an anonymous voice as independent customer testimony.

Read the evidence registry and method

How does a Met automate this operation?

In this operation, the Met coordinates Alegra, CRM de Meteor to execute the documented workflow: The Met identifies the customer by phone number even when they write from a new one, then confirms list price and warehouse stock by reading Alegra in the moment. The page separates automated work from decisions that still require human confirmation and does not present the process as a guarantee of results.

Context

The documented operation

A food distributor sells to restaurants, hotels and neighborhood stores along fixed delivery routes. Orders arrive on WhatsApp at any hour, and usually the night before the route runs.

Documented country: Colombia

Before: manual work

  • Every rep worked from a personal line. When someone left the company, their customer history left with them.
  • Prices and stock were checked by hand in the accounting system, or answered from memory.
  • Orders were retyped from the chat into the order form, with data entry errors as a standing risk.
  • Collecting on a past due invoice depended on somebody remembering to call.

Now: work handled by the Met

  • The Met identifies the customer by phone number even when they write from a new one, then confirms list price and warehouse stock by reading Alegra in the moment.
  • It builds the quote with a link to the formal PDF inside the same conversation. When the customer accepts, the order reaches the team with the line items and the total, and someone records it in Alegra from the desktop.
  • When the customer says they paid, the Met notes it in the conversation so the team records the payment in Alegra from the desktop: fiscal records are never touched over WhatsApp.
  • Past due invoices get listed, and the collection reminder goes out on WhatsApp on the agreed date.
  • The whole conversation stays in the CRM with its history, its tags and its assigned rep.

Integrations

Systems behind the case

Each link opens the connector’s technical page, including its tools, requirements and limits.

Alegra CRM de Meteor

Documented limits

  • It does not replace your accountant. This is an operating window into Alegra, not accounting judgment.
  • Meteor leaves the invoice ready in Alegra as a draft, and you issue it to the DIAN from Alegra. The invoice tools sit behind an explicit human confirmation, and a Met can have them turned off entirely.
  • The Met does not message the whole customer list at once. Collection reminders go out one at a time as approved templates. A notice to many customers goes through Broadcasts, with a Meta-approved template, a segment built from tags or contact fields and a messages-per-minute cap that protects the line.

Want to review a similar operation?

We show what can be connected, what needs human confirmation and what should not be promised.

Book a demo