Skip to content

Anonymized operational case

The counter tablet stopped being the bottleneck

A casual dining restaurant with several locations takes delivery orders through Rappi and table reservations through WhatsApp. Both land at the same time, during the same rush.

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 Rappi, Agenda de Meteor, CRM de Meteor to execute the documented workflow: The Met sees incoming orders, accepts them with the real prep time, and later marks them ready for the courier to pick up. 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 casual dining restaurant with several locations takes delivery orders through Rappi and table reservations through WhatsApp. Both land at the same time, during the same rush.

Documented country: Colombia

Before: manual work

  • Orders were accepted from the tablet at the counter. During the rush, any order nobody got to canceled itself.
  • When the kitchen ran out of an ingredient, the item stayed listed until someone logged into the portal to switch it off.
  • With the kitchen backed up, orders kept coming in that were not going to be filled on time.
  • Table reservations were confirmed by message and recorded nowhere, so on the day itself nobody knew how many tables were committed.

Now: work handled by the Met

  • The Met sees incoming orders, accepts them with the real prep time, and later marks them ready for the courier to pick up.
  • It switches off sold out items by SKU without touching their price, and switches them back on when the ingredient arrives.
  • It closes the storefront when the queue backs up and reopens it when the kitchen catches up, instead of stacking up orders nobody can fill.
  • Table reservations come from real open slots, get confirmed in the conversation, and get moved or canceled right there.

Integrations

Systems behind the case

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

Rappi Agenda de Meteor CRM de Meteor

Documented limits

  • It does not change prices or edit the menu. It only turns availability on and off for items that are already published.
  • It does not manage couriers or delivery times. That side belongs to Rappi.
  • It does not resolve marketplace disputes or refunds.

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