Hotel and guesthouse guests write on WhatsApp at three moments: before booking ("any rooms for the long weekend?", "are pets allowed?"), before arriving ("what time is check-in?", "is there parking?") and during the stay ("could I get another towel?"). Searching for WhatsApp automation for hotels usually means covering that volume without someone on duty around the clock.
A menu flow handles closed questions, like check-in time and address. It breaks on the questions that change a booking: flexible dates, large groups, special requests, complaints. That is where guests decide whether to come back.
What a chatbot does well and what it ruins
| situation | menu chatbot | a reply in the front desk's tone |
|---|---|---|
| check-in time, address, Wi-Fi | works | works |
| booking request with details | gets stuck | works |
| an unhappy guest | annoys | works |
| groups, events, travel agents | does not fit | works |
How WACrew helps
One queue by wait time. Booking questions, in-house guests and travel agents land in one list, longest wait on top.
AI in the front desk's 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 before anything is sent.
Nights and weekends. Auto mode, turned on per chat, lets the AI answer what is already settled (hours, address, pet policy) and leave the rest for the morning shift. In Confirm mode, the default, nothing goes out without someone's OK.
Staff per shift. Each receptionist logs in with their own account and sees the chats you grant. Every message records who sent it, so a shift change does not lose the thread.
Voice notes transcribed, calendar in the panel. Guest audio becomes text, and the Google Calendar shows up in the panel for whoever books transfers or tours.
Install
git clone https://github.com/sumioshi/wacrew && cd wacrew
PANEL_USER=admin PANEL_PASS=change-me docker compose up -d
Link the hotel's number at /config and create front desk logins at /equipe. Other ways to install are on the home page.
Honest limits
- No booking-engine integration. Availability and rates stay in your PMS or booking engine. The AI answers what you already told it and does not confirm bookings on its own.
- Not a campaign tool. The connection is unofficial (Baileys) and is meant for replying to people who contacted the hotel. Sending promotions to your whole guest list gets numbers banned.
- Needs a server that stays on. WACrew only sees what arrives while it runs, so covering the night means running it on a VPS or in the cloud.
FAQ
Can the AI confirm a booking by itself? Not without you. It can answer questions and collect the request details; confirmation depends on your booking system and someone at the front desk.
Can it answer guests in the middle of the night? Yes, with auto mode on the chats where it makes sense. It answers what is settled and leaves the rest for the team.
What if a guest asks whether it is a bot? The AI does not lie. It stops replying and hands the conversation back to the team.
Is there a monthly fee? No. It is open source. You pay for the server and the AI provider, if you use one.



