Switching Guest Messaging Providers Without Losing Your History

The hotels most likely to switch guest messaging providers are the ones who have learned what matters by living with the wrong product. This is for them, and it starts with the question that decides whether switching is even possible.

First: who owns the number

Everything else depends on this.

WhatsApp for business runs on a WhatsApp Business Account registered to a legal entity. If that account is in your hotel's name, the number, the verified business name and the approved templates all belong to you, and they move with you. If the account is in the outgoing vendor's name, the number stays with them, and the day you switch, every guest who saved it is messaging a dead channel.

Check before anything else. Log into the business manager, or ask the vendor in writing whose name is on the account. If it is theirs, the migration starts with a negotiation rather than a plan, and the leverage is on their side.

This is the reason to insist on owning the account when you first buy. If you did not, it is the reason to raise it now, before you need it.

Second: export before you give notice

Three things live in the old system and may not survive the move:

Conversation history. Every guest exchange, which is also every guest preference the assistant learned. Export it in full - ideally as structured data, at minimum as readable text - before the relationship changes tone.

Approved templates. The exact text of every proactive message - pre-arrival, check-in link, departure reminder. You will need to resubmit these under the new provider, and having the approved wording saves a round of rejections.

The knowledge base. Everything the assistant was told about the property. This is yours in every sense, and it is the largest part of the value you are moving. Get it out as text.

Ask the vendor in writing which of these they will provide, in what format, by when. A good vendor has done this before and answers in a day. A reluctant one is telling you what the next month will be like.

Third: the things that take calendar time

Migration is mostly waiting. Plan for it.

Account transfer on WhatsApp's side takes days and needs the old vendor's cooperation if they held any part of the setup.

Template re-approval. Every template is resubmitted under the new provider and reviewed by Meta. A provider with a library of approved patterns cuts this substantially.

PMS API access. If the old vendor held the credentials, the PMS vendor issues new ones, and that is a ticket in someone else's queue.

Two to four weeks for a single property is realistic. Groups scale roughly with the number of PMS instances, not the number of rooms.

Fourth: run both for a week

Cut over gradually. Point a subset of traffic - one channel, or one property - at the new system while the old one still runs, and read the escalations from both.

What you are looking for is the questions the new assistant cannot answer that the old one could. Those are gaps in the migrated knowledge base, and they are far cheaper to find with 10% of guests than with all of them.

Then cut over fully, and keep the old export somewhere you can search it for a quarter.

When switching is the wrong fix

Not every frustration is a reason to move.

Rising cost at rising volume is a pricing conversation. Every provider's costs scale with conversations; ask for the number at your volume before assuming a competitor's will be lower.

A poor knowledge base is usually the property's to fix. An assistant that gives stale answers is reflecting stale information, and it will do the same on a new platform.

Missing features are worth a direct question first. The category moves fast and the feature may exist.

The reasons that do justify switching are product failures: escalations landing nowhere, the assistant improvising instead of handing over, guests being told things that are not true, or a vendor who cannot answer whose name is on the account.

The checklist

1. Confirm who owns the WhatsApp Business Account. 2. Export conversations, templates and the knowledge base. 3. Get the old vendor's handover commitments in writing. 4. Sequence the waits: account transfer, template approval, PMS access. 5. Run parallel on a subset for a week, read both escalation streams. 6. Cut over, keep the export searchable.

And on the way in to the next provider: own the account, keep an export routine, and ask what leaving looks like before you sign. The best time to plan a migration is the day you buy.