Food delivery orders on WhatsApp in Kenya

12:15pm on a weekday: fifteen chats ask for today's menu, delivery fee to Westlands, and M-Pesa till — while the kitchen is already twenty minutes behind. Food sellers in Nairobi lose orders to silence, not competition. Glovo takes commission; WhatsApp keeps margin if you can reply during the lunch spike. Timi sends menu, fees, and ETA from business context in seconds. You confirm quantity and dispatch when the pin arrives.

For industry overview see food delivery on WhatsApp.

What buyers need in the first reply

Hungry buyers decide fast. First message should cover:

• Today's menu or bestsellers with prices — not "what do you want?"
• Minimum order and delivery fee by zone — CBD vs Westlands vs Karen differ
• ETA — honest range ("45–60 min to CBD right now")
• Payment — till number, Paystack link, or cash on delivery policy

Timi pulls this from shop context. You confirm the order when they share quantity and delivery pin.

Sample first-reply structure

Keep it scannable — buyers are on mobile, often ordering for office lunch:

1. Greeting + today's specials (3–5 items max)
2. Delivery fee to their area if they named it; otherwise list zones
3. Minimum order and ETA
4. Ask: "Reply with items + quantity + Google pin or estate gate details"

Timi can follow this pattern from pasted context. You avoid typing the same menu fourteen times.

Capture the delivery pin early

High-intent food orders include:

• Estate or building name
• Google Maps pin or clear landmark
• Phone for rider — "call when at gate"
• Floor / apartment if relevant

Timi can ask for pin before you dispatch. Missing pins cause expensive back-and-forth — rider calls you, you call buyer, food sits cold.

On the intent ladder, pin + quantity + payment question means hand off or confirm within minutes.

Order flow from chat to rider

• Menu + fees — Timi auto-reply. "Chicken rice KES 450, delivery Westlands KES 150"
• Quantity confirm — You or Timi if in context. "2 plates?"
• Pin capture — Timi prompt or you. Google pin link
• Payment — You. Till confirmation screenshot
• Dispatch — You / rider app. Rider leaves kitchen

Adjust to your kitchen — some teams pause Timi after payment and run dispatch manually.

Peak hours vs quiet hours

Turn Timi up during 11am–2pm and 6pm–9pm. Use business hours auto-reply to set honest ETAs after kitchen close — "Orders resume 11am tomorrow" beats ghosting.

Quiet hours: still reply with tomorrow's hours so buyers save your number.

Repeat customers and "usual order"

Regulars message "usual order" or "same as last time". Options:

• Pause Timi on VIP chats — personal touch matters
• Add standing notes in your process — Timi handles new buyers, you handle regulars
• Never let automation argue with a loyal customer over a remembered preference

WhatsApp vs delivery apps

Apps take 15–30% commission and own the customer relationship. WhatsApp keeps margin if you own dispatch — Instagram + WhatsApp + one rider team works for many Kenyan kitchens without a marketplace middleman.

Trade-off: you own reply speed and pin accuracy. Timi covers speed; your dispatch discipline covers the rest.

Packaging and rider handoff

When volume spikes, chaos moves from chat to kitchen to rider. A simple handoff note in your process prevents wrong orders:

• Confirm items and quantity in chat before payment
• Kitchen ticket matches chat name + pin
• Rider gets pin link + buyer phone in one message — not scattered voice notes

Timi gets buyers to structured answers (items, pin, payment question). Your team owns the last mile. Even two minutes saved per order compounds across fifteen lunch chats.

Ads to WhatsApp for food

Promote lunch specials with Click-to-WhatsApp — not wa.me in ads. Timi tracks which ad chats pay. See CTWA tracking and WhatsApp ads overview.

Match ad creative to menu in shop context — ad shows KES 399 combo, first reply quotes KES 399 combo.

Common mistakes

• Stale menu in context after sold-out lunch item
• Quoting CBD delivery fee to Karen buyer without checking zone table
• Dispatching without pin — rider loops cost margin
• No minimum order stated — small orders kill delivery economics
• Turning Timi off entirely during rush — misses new buyers while you pack bags

FAQ

Can Timi handle menu changes daily? Yes — update business context each morning; two minutes if you keep a running doc.

Allergies and custom orders? Hand off to kitchen staff when buyer specifies modifications Timi should not guess.

Multiple locations? One WhatsApp number per kitchen line unless you centralize dispatch with clear zone rules in context.

Cash on delivery? State in FAQs; confirm on handoff when rider is en route.

Can I send menu PDF? Link in context works; keep text prices in context too for fast scan.