Start with message purpose and permission
When choosing hotel guest-messaging software, test why a message is sent and how the guest agreed before comparing the number of channels. Seeing reservation, arrival, or service messages beside marketing campaigns does not mean they share the same permission. WhatsApp Business policy says businesses need permission to contact people on WhatsApp and must respect requests to stop or block messages. Public SMS setup guides from vendors also show that number types, registration, and approval can vary by country. These are platform- and product-specific rules, not a replacement for all communication law in Turkey. Make the buying decision around how the product demonstrates your workflow, not as a substitute for legal advice.
Inspect the permission record
First ask where and how permission records are kept. A guest may provide a phone number for a reservation, but that alone does not show consent to every kind of message. You should be able to see the purpose, whether the channel is WhatsApp or SMS, how the business is identified, and when the preference was recorded. What happens if a guest declines marketing or optional messages? Who can view the refusal? Can you export evidence? Ask the vendor to demonstrate a step-by-step flow in a test account, not just show a slide. Different providers may use the word ‘consent’ for different steps, so inspect the definition and fields with a sample record that contains no real guest data.
Test opt-out end to end
The second test is whether a stop request reaches every team and channel. In a test account, if a guest asks to stop by SMS or WhatsApp, do sales, reception, and the night shift see the same preference? Can another user later start a campaign to that guest? WhatsApp policy explicitly says businesses must respect requests to block, stop, or reject communication. Whether the software automates a step or supports a channel must be demonstrated for the current product and plan. This article does not determine legal obligations by country; seek local advice about privacy and communications rules. Do not ask only ‘does STOP work?’ Ask who owns the refusal record, who can see it, and how later workflows use it.
Confirm country and channel coverage
Confirm country and channel support with the team that will operate the system. SMS number types, registration, delivery, and supported countries can differ. A supplier’s U.S.-specific A2P process should not be assumed to apply in Turkey. Ask for written setup steps for your property country, guest phone country, and every channel. Then test which booking fields are carried over: reservation reference, language preference, message purpose, and permission status. Use a fictional booking that contains no personal data. If a supplier says it maps those fields, test what happens after a reservation change or duplicate guest record. Do not assume an integration is available in every country or plan merely because it appears in a public product guide.
A decision plan after the demo
Add total cost and exit planning to the demo scorecard. Ask whether fees are per user, conversation, message, or channel, and whether setup, number, local support, or retention have separate costs. Check how those charges are defined in the quote and contract. Can reservation data and message history be exported, in what format, and how long do they remain after access ends? Can an open conversation, assigned owner, last response time, and unresolved issue move from one shift to another? These are procurement questions, not claims that a specific product has the feature. In your comparison table mark each item ‘demonstrated,’ ‘written confirmation needed,’ or ‘out of scope.’ This makes the choice depend on tested workflows, permission records, and team handover rather than a sales presentation’s channel count.
Do not decide from the feature list alone. Define the pilot team, message types, how guests grant permission, and where the record is retrieved. Use synthetic records rather than real personal data for consent, opt-out, wrong-number, shift-handover, and outage scenarios. Agree on an owner, training, export format, and stop conditions. Evaluate observable processes, and confirm legal, privacy, and platform requirements with qualified advisers.