Intake01
Customer messages your WhatsApp line
Konkon reads order intent, resolves menu items, asks clarification questions, and keeps the conversation moving without forcing a new app.
Food commerce infrastructure for WhatsApp
Turn messy food chats into paid orders, station tickets, rider trips, and settlement records.
Konkon sits behind the WhatsApp line your customers already use. It structures intake, confirms payment before prep, keeps the station moving, and gives operators a single view of every exception.
1 line
WhatsApp number customers already trust
6 states
From order intake to settlement visibility
0 apps
Required for customers to browse and pay
Live order spine
Asun & More
WhatsApp intake
2 jollof, suya, delivery to Lekki
Cart resolved
3 items, 1 delivery note
Station ticket
Accepted, 18 min prep target
Dispatch
Preferred rider first, pool fallback ready
Next action
Station marks ready, rider receives pickup handoff, customer gets delivery PIN.
The operating flow
One commerce spine from first message to completed delivery.
Konkon is not a chatbot skin. It is the operational layer that turns chat demand into controlled restaurant workflow.
Cart02
A clean cart is built from chat
Variants, quantities, delivery notes, and customer identity are converted into a payable order with fewer back-and-forth calls.
Payment03
Payment confirms before production
Paystack handoff, webhook confirmation, and order state updates protect the station from unpaid or duplicated tickets.
Station04
Tickets move through prep states
Staff see paid orders, accept or reject tickets, mark preparation progress, and signal readiness for pickup.
Dispatch05
Rider flow stays operational
Own riders are prioritized, pool riders can cover gaps, and delivery completion is protected with customer PIN verification.
Settlement06
Finance stays reconciled
Vendors get payment visibility, settlement settings, and order history that match the operational record.
Control room, not dashboard theatre
Built for vendors who need fewer calls, fewer missed payments, and fewer blind spots.
Every surface is designed around operational clarity: what needs attention, who owns it, and what should happen next.
WhatsApp coexistence and line status controls
Menu, branch, rider, and station staff setup
Paid order queue with prep-state accountability
Dispatch fallback when preferred riders are unavailable
Customer PIN handoff for delivery disputes
Admin visibility into stuck orders and payment risk
Pilot ready for serious operators
Bring one vendor line online, prove the flow, then expand branch by branch.
Start with WhatsApp intake, menu setup, paid checkout, station queue, and dispatch. The customer keeps using chat; the business gets infrastructure.