Most people searching for a WhatsApp chatbot for restaurants are thinking about orders: the guest says hi, gets the menu, builds the order and pays. For that, the honest answer is that an online ordering page or your delivery app beats any chat, because an order is a form, and forms are faster than conversations.
But a restaurant's WhatsApp is not only orders. It is the booking for twelve on Saturday, the quote for a company dinner, the supplier saying the delivery is late, the guest whose food arrived cold, and the managers' group across locations. That part does not fit in a menu, and that is where WACrew comes in.
Split orders from conversations
| type of message | best route |
|---|---|
| everyday order | online menu or delivery app, linked in the greeting |
| booking, event, large order | a conversation with a person, in the house tone |
| complaint | a person, quickly, with no canned reply |
| suppliers and staff | internal chat, sorted by who is waiting |
How WACrew helps with the conversation part
One queue by wait time. Bookings, events and complaints land in one list, longest wait on top. Chats that ended in "ok, thanks" drop off on their own.
AI in the house tone. The AI reads the conversation and drafts in the writing style of whoever answers, measured from real messages. A review in code blocks robotic phrasing and repeated apologies, the two things that annoy a guest who is already unhappy.
You approve first. In Confirm mode, the default, nothing goes out without someone's OK. Auto mode can be turned on only where it fits, such as confirming a booking request arrived.
Voice notes transcribed. The guest's two-minute audio about what went wrong arrives as text.
Team access per chat. Each location's manager gets their own login and sees only the chats you grant.
Install
git clone https://github.com/sumioshi/wacrew && cd wacrew
PANEL_USER=admin PANEL_PASS=change-me docker compose up -d
Link the number at /config. Other ways to install are on the home page.
Honest limits
- No ordering or payments. There is no menu, cart or delivery-platform integration. Keep orders in the delivery tool you already use.
- Not for mass promotions. The connection is unofficial (Baileys) and is meant for replying to people who contacted you. Broadcasting to thousands of numbers gets accounts banned; the official API is the route for that.
- Very high order volume needs another tool. If hundreds of orders a night come through WhatsApp, the bottleneck is the ordering flow, not the conversation.
FAQ
Can I run a free WhatsApp ordering bot? Yes, with flow builders and online menus. WACrew is not one of them; it handles the conversations that need a person.
Can the AI handle complaints by itself? It can, but we do not recommend it. A complaint needs someone from the house deciding what to offer. The AI drafts, you approve.
Does it work across several locations? Yes, one collector per number. Each location with its own number runs its own, and one MCP server can serve them all through the conta parameter.



