When a Kuwait merchant needs a wallet agent

The job is a question from the kitchen about money you already keep. “Why was this fee taken.” “Why will the order not go out.” Ops still opens the wallet screen and types the same two sentences into chat.

Teams ask for “a delivery bot.” That is a tracker. This agent reads the prepaid ledger you already run, answers with the balance, the fee, and the block, and holds when cash-on-delivery and the wallet disagree.

What the agent actually does

It knows which merchant chat is tied to which account. It reads the KWD balance, the last top-up, and the fee on that order. It says whether the order is blocked, what is due, or which deduction already posted. It does not invent a credit. It does not move money.

AI agents can sit on that lookup. Manzil already keeps a prepaid wallet, MyFatoorah top-up, and fee deductions next to merchant chat. We will not treat a WhatsApp “we will settle tonight” as a funded row.

This is not blocking an order when the wallet is short. The block is a rule on create. This job answers a person who asked why. It is also not a COD envelope that does not match the shift. COD is cash after the door. The wallet is the kitchen’s fee before dispatch. And it is not an order-status reply. Status says where the bag is. This job says what the till did.

When we leave the ledger with a person

If two branches share one wallet and one does not, the agent should refuse, not pick a branch. If finance still accepts a voice note as a top-up, software should not pretend a MyFatoorah row exists. If a manager can waive the fee in chat, log the waive — do not hide it in the reply.

Kuwait fees are in KWD. Do not convert a guest AED total and hope the deduction matches what the merchant sees.

Bring three “why was I charged” threads and the wallet screen a person opened to answer them. Book thirty minutes or write hello@jamilglobal.com.