Guide · Messaging · 14 minutes

Setting up WhatsApp Business API for your property.

WhatsApp is the messaging channel with the highest read rate in hospitality, ahead of email and SMS by a wide margin. Guest Talk uses Meta's WhatsApp Business API (not the free WhatsApp Business app) so that messages fit inside the same unified inbox and audit trail as every other channel. This guide walks through the setup: Meta Business Manager verification, phone-number certification, template pre-approval, GDPR-compliant opt-in, and the seven templates every property should have on go-live.

What the WhatsApp Business API is (and is not)

The WhatsApp Business API is Meta's paid, API-driven access to the WhatsApp messaging network for businesses. It is not the free WhatsApp Business app that installs on a phone; that app is fine for a two-person team but has no API, no unified inbox with other channels, and no message-template governance. The API-based flow requires business verification, uses templated messages for outbound communication, and charges per conversation (billed by Meta, invoiced by Guest Talk in the same currency as your subscription).

Prerequisites

• A Meta Business Manager account for the legal entity that operates the property.
• A dedicated phone number that will belong to WhatsApp Business for this property. It can be a landline, mobile, or virtual number, but must be able to receive an SMS or voice call for verification and must not currently be attached to any consumer WhatsApp account.
• Company registration document and, if the entity is less than two years old, a utility bill in the entity name.
• Domain ownership of your marketing website (used to verify business identity via a DNS TXT record).

Step-by-step

Step 1: create a Meta Business Manager. If your property already advertises on Facebook or Instagram, use the same Business Manager. Otherwise create one at business.facebook.com; enter the legal entity name and address exactly as they appear on the company registration certificate.

Step 2: verify the business. Meta requires business verification for API access. Upload the registration certificate and complete the domain verification via a TXT record on your marketing domain. Guest Talk provides the DNS record content in your workspace; your web host or IT partner adds it. Verification typically takes 1-5 working days.

Step 3: connect the phone number. Provide the WhatsApp phone number to Guest Talk. Guest Talk requests certification from Meta; you receive a one-time verification code by SMS or voice, which you paste into the workspace. On success the number is bound to your WhatsApp Business Account.

Step 4: display name. The display name shown to guests must exactly match the property brand and cannot be a promotional tagline. Meta reviews the requested display name; approval usually completes within a day.

Step 5: request the phone-number quality rating. Meta grants a starting tier of 250 conversations per day per number; as your quality rating improves over 30 days of clean sending, the tier automatically increases to 1,000, 10,000 and unlimited.

Templates and pre-approval

Outbound messages that are sent more than 24 hours after the guest's last inbound message must be templates. Templates are submitted to Meta for pre-approval, typically returned within 24 hours, and can be re-used indefinitely with variable substitution. Guest Talk ships a starter library of 20 templates already pre-approved in the six most common European guest languages; you can copy and modify these or submit fresh ones.

The seven templates worth having on day one

1. Booking confirmation. Sent immediately after a direct booking, or after Booking.com passes the reservation. Includes property name, arrival date, check-in time and a link to the pre-arrival information page.
2. Pre-arrival check-in. Sent 48 hours before arrival. Asks for approximate arrival time and any dietary preferences. Includes the online check-in link if you use one.
3. Arrival day welcome. Sent at 09:00 on the arrival day. Includes the Wi-Fi password (if you deliver it by message), the arrival location, and a phone number for late arrivals.
4. Mid-stay check-in. Sent on the second morning of stays longer than three nights. A single question: "How is your stay so far?"
5. Departure reminder. Sent at 19:00 the evening before departure. Reminds check-out time, offers late check-out where available with a price, and asks whether a taxi is needed.
6. Post-stay thank-you and review request. Sent 24 hours after check-out. Templated in accordance with the review-guideline policies of Booking, Google, TripAdvisor and Airbnb.
7. Payment link (utility). Used for follow-up payments, incidentals or damage charges. Includes a secure Stripe-hosted link and expires in 48 hours.

GDPR-compliant opt-in language

Guests who book through Booking.com, Expedia, or your direct booking engine provide their phone number for the purposes of managing the reservation. This is a lawful basis for transactional messages such as booking confirmation, pre-arrival check-in and departure reminder. It is not a lawful basis for marketing messages such as newsletters or promotional offers; those require explicit opt-in.

The Guest Talk booking engine collects opt-in for marketing separately with a clearly-labelled checkbox that is unticked by default. Booking.com and Expedia integrations flag the marketing consent status the guest gave on the OTA (usually "not given"); Guest Talk suppresses marketing templates automatically for guests without consent. The upshot: you do not have to remember which guest opted in; Guest Talk enforces the rule inside the messaging module.

Operational routines after go-live

The messaging inbox needs a daily rhythm. Guest Talk defaults to notifying the on-shift user of any inbound message that has not been read within 15 minutes during working hours (09:00 to 21:00 in your property's time zone) and automatically responding with an "out of hours" template outside that window if you enable it. The inbox also supports triage by tags (VIP, complaint, upsell opportunity) that route to different staff members if you have a larger team.

Weekly, run the messaging report: number of conversations opened, average time to first response, share of conversations handled by templates versus free text, and sentiment distribution. Guest Talk highlights any template with a high opt-out rate; these are usually templates that guests find pushy or repetitive.

What can go wrong

Business verification stalls. Most commonly because the legal entity name in Meta does not exactly match the company registration certificate. Fix: update Business Manager to the exact registered name and reupload.

Number quality drops. If enough guests report the number as spam, Meta drops the quality rating and lowers the daily conversation limit. Fix: audit the templates for tone, ensure marketing templates only reach opted-in recipients, and stop any bulk send that could look like unsolicited outreach.

Display name rejected. Meta rejects display names that are generic ("Hotel"), promotional ("Best Rate Hotel"), or misleading. Use the exact registered brand name.

Template rejection. Meta rejects templates that read like promotional broadcasts, contain excessive emojis, or use terms flagged by the anti-spam classifier. Fix: rephrase and resubmit; approval usually comes within a day.

Checklist

• Meta Business Manager account created with exact legal entity name.
• Business verification submitted with registration certificate.
• Domain verification TXT record deployed.
• Phone number selected and confirmed not attached to any consumer WhatsApp account.
• Display name matches the property brand.
• Seven starter templates enabled in guest languages.
• Marketing opt-in checkbox visible on the direct booking engine.
• Out-of-hours template configured for after 21:00.
• Inbox notification routing configured to on-shift user.
• Weekly messaging report scheduled.