When Kuwait orders should auto-dispatch, not wait on chat

The job is an offer that reaches a rider before the food is cold. The order is already on a board. Someone still types a name into a WhatsApp group and hopes the right person taps first.

Teams ask for “AI dispatch.” That is a slogan. This loop sends a timed offer, waits, then escalates to a person when nobody takes it.

What the automation actually does

It sees a new order on the board you already run. It picks eligible riders — online, right vehicle, not already on a drop. It sends an offer with a timeout. If the offer dies, it pages the dispatcher instead of guessing.

The Manzil delivery case study is that shape: auto-dispatch offers, a timeout, and a kanban that surfaces the miss for a manual assign. AI automation is the offer loop. We will not open with a routing model if the live map is still a rumour.

This is not building a delivery platform instead of WhatsApp. Four seats and a wallet are a product decision. Dispatch is the assignment after those seats exist. It is also not reading an address off a delivery photo. A house number is a later, narrower job. An offer does not OCR a parcel.

When we leave the assign with a person

If two companies share riders and nobody agrees who is eligible, software will double-book. If cash-on-delivery has no owner, an offer will not fix the float. If you have one dispatcher and a dozen drops, a group rule is still enough.

Kuwait addresses are often area, block, and street — not a clean pin. The offer can still go out. The map does not have to be perfect on day one. The timeout and the manual override do.

Bring one day’s assignment thread and the board you already use. Book thirty minutes or write hello@jamilglobal.com.