A member is choosing between two hotels. One of them is part of the group they collect points with, which makes it worth more to them than the rate difference suggests. Before booking they want to know whether this particular rate earns, what their tier gets them and whether they have enough points to use instead.
If those answers are behind a login, the booking often goes elsewhere.
What members ask
They usually ask how points are earned and on what spend, what a typical stay is worth, which rates qualify, whether third-party bookings earn, how to redeem, whether redemptions can be combined with cash, what each tier includes, how to reach the next tier, whether points expire and whether stays can be claimed retrospectively.
Which rates earn is the decisive question
Members regularly discover after the fact that the rate they booked earned nothing. Publishing which rates qualify, and stating plainly that bookings through third parties usually do not, prevents a complaint and pushes bookings to the direct channel where they are worth more anyway.
Example conversations
These scripts use information a group might publish. Your answers should come from your own pages.
Member: Does this rate earn points? Assistant: The loyalty page explains which rate types earn and which are excluded, including third-party bookings and certain discounted rates. Booking directly on the group site is the route that earns. Would you like me to point you to the rate details for the hotel you are looking at?
Member: What do I get at the next tier? Assistant: The tiers page lists the benefits at each level, including room upgrades where available, late checkout, breakfast and any welcome amenity, along with the nights or spend needed to reach each one.
Member: How many points do I have? Assistant: Your balance is in your account, and signing in shows it along with your tier progress. The page explains how to reset a password if you cannot get in.
Tier benefits need honest wording
Upgrades subject to availability are not upgrades in a member's mind unless that is said clearly. Publishing what is guaranteed and what depends on availability avoids arrival-desk disappointment, which is the expectation problem described in what guests ask before they book a hotel room.
Redemption is where members lose patience
Whether a redemption night is available, what it costs in points, whether taxes are payable and whether points and cash can be combined. Publishing a points chart is more useful than any promise about value.
Expiry and inactivity
Members with dormant balances are the most easily annoyed group. Publishing expiry rules and how activity resets them is better than a balance quietly disappearing.
Retrospective claims
Members forget their number at booking. Publishing how far back a stay can be claimed, and what is needed, recovers goodwill cheaply.
Consistency across the estate
Different hotels answering differently is exactly the failure described in brand consistency across hotel websites and assistants, and international members raise the language questions in multilingual guests and the questions they ask before arrival.
Account data stays out of chat
Balances, personal details and account changes need proper authentication, which is among the things to ask about in AI chatbot security questions to ask a vendor.
Getting started
Publish earning rules, tier benefits, redemption and expiry, then answer at any hour before the booking decision. SpideyChat for hotel groups answers from your published pages and never touches account data. Try SpideyChat on your own site, or read about answers on the features page.