Duka — agiza na ulipe
The customer types what they want in their own words; it becomes a priced order and a mobile-money prompt, and nothing ships until the money actually lands.
Ni halisi
Mtiririko wa ujumbe unaendeshwa na injini ile ile inayohudumia wateja, ndani ya muamala unaotenguliwa. Hakuna ujumbe unaotumwa, hakuna oda inayotengenezwa.
- ✓ Hatua zilizofichwa bado zinafanya kazi — unaona jibu, si jinsi lilivyoandikwa
- ✕ Malipo, SMS na simu hazifanyiki hapa
- ☎ IVR inatembezwa hapa hapa — hakuna laini halisi inayopigwa
Muuzaji ameacha sehemu hii isomeke. Iliyobaki inafunguliwa ukinunua — lakini kila tawi na aina ya hatua inaonekana, ili ujue unachonunua.
The whole trade in one thread: browse, say what you want, get a total, pay, get a receipt. A customer writes “mifuko 3 ya cement na nondo 10, nipo Mbeya” and the flow reads it. Only what is missing gets asked for — and if words fail, it asks for a photo and puts a person on it. The order is written against your catalogue, so what was quoted, what was charged and what shipped are one record. The payment step then WAITS: settlement wakes it, and nothing downstream ever runs on the assumption that a prompt was approved. Unpaid orders are not nagged at midnight — the flow waits for morning, checks the 24-hour window is still open, and splits two wordings so you find out which one brings people back. Paying at the counter is a first-class path: it sends the shop pin, a sales contact, and hands the thread to your AI so questions afterwards still get answered.