Take the order without the customer leaving the chat

A real cart, built inside the chat

The version of WhatsApp ordering most businesses end up running is a person typing back and forth. The customer sends a paragraph, somebody reads it, asks two clarifying questions, gets a reply twenty minutes later, and eventually writes the order on a pad. It works at five orders a day and collapses at fifty.

Here the order is structured data from the first message. Items, modifiers, and variants are captured properly and assembled into a real cart the customer can see and check, rather than a wall of text somebody has to interpret at the pass. That is what makes a missing "no onions" impossible rather than merely unlikely.

The money is exact too. Totals are handled in integer cents throughout, so what the chat says and what the customer pays are the same number.

• A structured cart with modifiers and variants, not free text
• The customer sees and checks the order before it confirms
• Money handled in integer cents, so totals are never approximated
• You get a receipt on your phone the moment an order confirms

Nobody installs an app to buy lunch

Ordering apps and ordering pages both ask the customer to go somewhere else. For a big chain that is a reasonable ask, because the customer orders every week and the icon earns its place on the home screen. For a neighbourhood business it is usually the point where the order stops happening.

WhatsApp asks for none of it. The customer is already in the app, already logged in, already has your thread in their list from the last time. They type what they want and the order happens. Nothing to download, no account, no password, no checkout page that renders badly on an older phone.

• No app to install and no account to create
• Your thread is already in their chat list from last time
• No checkout page to load on a phone with two bars of signal
• The same ordering also runs on text, web chat, and a live phone call

Tap instead of type

Typing an order out is slow and it is where mistakes come from. Tappable option chips render inside WhatsApp itself, so choices are presented as things to press: sizes, variants, pickup times, the confirmation at the end.

That does two things at once. It speeds the customer up, and it removes the ambiguity that free text creates, because a tapped option is unambiguous in a way that "the medium one I think" is not.

• Option chips rendered inside WhatsApp for choices and confirmations
• Faster for the customer and unambiguous for the kitchen
• Questions about the menu answered mid order, from your own information

The confirmation arrives in the same thread

Outbound runs on WhatsApp as well as inbound, so the confirmation and any pickup reminder land in the same conversation the order was placed in. The customer does not have to go and find an email, and the reminder does not arrive as a text from a number they do not recognise.

Pickup time is resolved rather than guessed, and every order is scored for risk with reminders queued to match, on the same model as bookings. That is what gets the food that was made actually collected. The details are on the booking and no-show prevention page.

• Confirmations and pickup reminders in the original thread
• Pickup time resolution rather than a vague soon
• Order risk scoring with reminders queued to match
• Opt-out enforcement applies on WhatsApp as on every channel

An order that came from a post arrives already attributed

A deep link into WhatsApp carries a tracking reference, so when a customer taps through from a post or a campaign, the conversation is attributed the moment it opens. You find out which content produced orders rather than which content produced likes.

Because the order is a real order on a real customer record, that attribution runs all the way to revenue, and the revenue is frozen at the moment the order is created so the reporting cannot drift later. See marketing and attribution.

• Deep links carry a tracking reference into the chat
• The chain from post to order to repeat customer stays traceable
• Revenue frozen when the order is created, so reporting cannot drift

Questions owners ask