When a Kuwait rider is late to pickup

The job is a clock you already printed. A rider accepted. The kitchen said the bag would be ready. The pin has not moved toward the restaurant. Someone still hears it from the merchant after the food has gone cold.

Teams ask for “live tracking.” That is a map. This loop pings when the accepted rider is late to the pass, then stops.

What the automation actually does

It starts when a rider has already accepted. It compares the kitchen ready time, or the ETA you already show the merchant, to the rider’s last ping. It sends one note with the order, the minutes late, and who may reassign. It does not invent a new offer.

Manzil already keeps that clock next to the live map. AI automation is the late-and-ping. We will not treat a grey pin with no GPS as “almost there.”

This is not auto-dispatch with a timeout. Dispatch argues who gets the first offer. This job starts after someone said yes. It is also not the pickup gate that hides the drop. The gate unlocks an address. A late ping pages ops while the bag is still on the pass. And it is not a proof photo to close the door. Close is the customer. This clock is the kitchen.

When we leave the clock with a person

If two shifts still argue what “ready” means — plated, bagged, or handed — software will wake the desk for the wrong minute. If riders go offline the moment they accept, fix the app before you add an alert. If you run twelve orders at lunch and the manager already watches the board, keep the shout.

Kuwait kitchens often quote a time on WhatsApp that never lands on the order. Write the minute into the ticket first. Do not average “ten minutes” from three voice notes.

Bring last week’s “rider accepted, food still here” tickets and the ready time you already promise. Book thirty minutes or write hello@jamilglobal.com.