// FOR RESTAURANTS, HOTELS & VENUES
Help guests feel at home.
What time is breakfast? Can we bring the dog? Is there parking nearby? ChatGenius uses your property information, menus, and policies to help guests find the details they need. Offer web chat or a connected messaging channel, with a route to your team for requests that need a person.
// WHAT IT HANDLES
The practical details, without the search.
Menu, hours & policies
Give guests a way to check opening times, menu details, dress code, and pet policies. Keep the source information current when your hours or offerings change.
Booking requests
Collect dates, party size, and the details your team needs. Confirming or changing a reservation depends on a connected booking system and the actions it allows.
Finding their way
Share arrival instructions, parking options, and map links from your venue information. Include the right entrance and accessible routes where available.
Conversations in their language
Help guests ask in a language they’re comfortable using. Test your main guest languages against your own content, especially local names and property-specific terms.
Voice notes
Some guests would rather speak than type. Where supported by the channel and setup, voice notes give them another way to ask. Check the available response formats during setup.
A person when it matters
Set up handoffs for complaints, special requests, and questions outside your content. Your team gets context for the follow-up; response times depend on who is available.
// FOR YOUR TYPE OF VENUE
Your place. Your guests. Your information.
Hotels & B&Bs
Help guests prepare for their stay with check-in instructions, breakfast times, amenities, and local recommendations. Keep private access details separate from general property information.
Restaurants
Share your menu, hours, and private-dining details, and explain how to request a table. For allergies or dietary safety, direct guests to staff for confirmation rather than relying on a chat answer.
Venues & event spaces
Make room capacities, facilities, catering options, and load-in details easier to find. Collect the event date and requirements so your team can follow up on availability and a quote.
// EVERYDAY GUEST QUESTIONS
Questions that sound familiar.
"Is your kitchen still open?"
Use your published kitchen hours and last-order time, including any exceptions you’ve added. Live service status needs a connected source or confirmation from the restaurant.
"Do you have gluten-free options?"
Point guests to the options listed on your current menu. Ask them to confirm allergies and preparation requirements with staff; the chat should not guarantee that a dish is safe.
"Can I check in at 11pm?"
Explain your late-arrival policy and how to contact reception. Any arrangement that needs approval should go to your team before the guest treats it as confirmed.
"Where's the closest parking?"
Share your recommended parking, a map link, and directions to the entrance. Keep restrictions and access notes up to date in your venue information.
"Do you have a highchair? Crib? Cot?"
Explain which family amenities you offer and how to request them. Availability should be checked with your team or the relevant connected system.
"My flight lands at 2am. Any advice?"
Share the arrival and transport information in your guest guide, including how to reach the property after hours. Send private access instructions only through your approved guest-verification process.
"Can I book a table for 8 on Friday?"
Collect the date, time, and party size. Check a connected booking system where available, or send the request to your team. A request is not a confirmed reservation.
"Wi-Fi password please 🙏"
Provide the guest-network instructions you’ve approved for sharing. Keep staff networks and private credentials out of the public chat content.
// A NIGHT AT THE FRONT DESK
A late-night question. A place to start.
Guests make plans outside reception hours too. Chat can help with check-in times, amenities, and other details you’ve provided. The example below illustrates a booking conversation; checking availability and holding a room require a connected booking system that supports those actions.
Questions before you get started.
Do we need a phone number for WhatsApp?
WhatsApp needs an appropriate phone number and account for the connection you choose. We’ll review the setup and account requirements before connecting it. Website chat works separately and does not require a WhatsApp number.
What if the chat doesn’t know the answer?
Define when the chat should ask for clarification or pass a question to your team. AI can still make mistakes, so test common and unusual questions before launch and review conversations afterwards. Sensitive requests should have a clear route to a person.
Can we set different rules outside business hours?
Discuss the hours your team is available and which requests should wait for a follow-up. The chat can be configured around those rules, with clear expectations for guests. Confirm and test the after-hours behavior as part of your setup.
Does it work with our PMS or POS?
Tell us which property-management, point-of-sale, or booking system you use. Access to availability, orders, and guest records depends on its API and permissions. We’ll check the specific integration and required actions before confirming support.
Can it confirm a booking?
It can collect a booking request. Confirming a table or room requires a connected reservation system that supports the action. We’ll agree what counts as a confirmed booking and test the confirmation flow before guests use it.
Let’s talk about your guests.
Bring a menu, a guest guide, or a few questions your team answers every day. We’ll look at where chat could help and what needs connecting to make it useful for your property.