When a Kuwait rider needs an exception agent

The job is a problem at the door. “Customer not answering.” “Wrong pin.” “Cash short.” The rider still waits on ops chat while the bag sits in the box.

Teams ask for “a delivery agent.” That is tracking. This agent reads the ticket you already keep, names the one next step the desk already allows, and pages a person when cash and the pin disagree.

What the agent actually does

It knows which rider thread is tied to which order. It reads the state you already store — at the door, cash due, photo required. It replies with one allowed move: wait, return, call, or hold for ops. It does not invent a new drop time. It does not close the ticket.

AI agents can sit on that slice. Manzil already keeps driver chat next to the live order. We will not treat one fleet’s “wait five minutes” as a rule for yours.

This is not a status lookup. Status answers a merchant who asked where the bag is. An exception starts when the drop failed. It is also not a late-to-pickup SLA ping. A ping fires on a kitchen clock. This job waits for a rider who wrote. And it is not proof-of-delivery to close. A photo finishes a good drop. This thread is the bad one.

When we leave the door with a person

If cash-on-delivery and a prepaid wallet show two different amounts, the agent should refuse, not pick a winner. If the merchant still argues with the rider in the same chat, software will talk over a human. Write who may break in.

Kuwait threads often mix Gulf Arabic voice notes with English pins. Name which of those the agent may answer. Do not transcribe a three-minute complaint and invent a new building.

Bring three failed-drop threads and the order screen a dispatcher opened. Book thirty minutes or write hello@jamilglobal.com.