Original Summary

Every WhatsApp order bot I've used is a phone tree in disguise so I built one that just understands you You know the drill. Reply 1 for menu. Reply 2 for locations. Reply 9 to scream into the void. It's a phone tree wearing a chat bubble. I wanted to see if I could skip all of that no keywords, no numbered replies, just talk to it like you'd talk to the shop's actual staff. So for a juice delivery shop I'm working with, I built a WhatsApp assistant that: Understands plain language (and code-switching "niaje", "sasa", mixed English/lingo all work) Knows the live catalogue — flavours, sizes, prices — pulled straight from the shop's own site Takes a typed address or a dropped pin and works out the delivery fee itself Builds a cart, totals it, and lets you confirm with a word or a tap — both paths hit the same cart state Fires an M-Pesa STK push for checkout, or falls back to pay-on-delivery if that fails or you'd rather Posts the finished order into the shop's actual backend with an order number, no human re-typing anything on their end The part that surprised me most wasn't the NLU, it was how much of the friction in these bots isn't language understanding — it's state. Cart contents, payment retries, delivery address parsing all have to survive a conversation that jumps around, gets interrupted, comes back a day later. Screenshots of a full order below. Curious what this sub thinks of the flow — anywhere it feels like it's fighting the user instead of helping them, I want to know.   submitted by   /u/Hakuna_marara [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/19 19:44:13