One Click, Every Market: How GuestMaker Translates a Campaign Without Losing Its Merge Tags

A marketing manager at a hotel group approves a spring campaign in Spanish, the brand's home market. Then someone has to turn it into French, German, Italian, and Portuguese before the send date arrives.

In most tools, that job looks like this: the approved template open in one browser tab, a translation engine open in another, a blank spreadsheet in a third to hold the output while it gets pasted back in, language by language. And through all five languages, one person has to keep a mental list of the handful of characters that must never change no matter what surrounds them. A guest's first name, sitting inside a merge tag like {{1}}. A booking link carrying three tracking parameters that only work if the URL survives untouched, the same parameters that later let GuestMaker follow a click through to a confirmed booking. A phone number written as +34 971 XX XX XX, not spelled out as words.

Miss one of those and the campaign either breaks outright, a literal {{1}} landing in someone's inbox where their name should be, or worse, it looks fine and fails quietly. A booking link that a well-meaning translation tool "helpfully" reformatted now resolves to nothing. Nobody notices until a guest calls the front desk asking why the German version's reservation button does nothing.

GuestMaker's template translation exists to remove that whole failure mode, on both channels a hotel group actually sends from.

One approved template, a full language family

The workflow starts from a template the marketing team has already signed off on, the finished version everyone agreed the campaign should say, in whichever language the brand writes first. On WhatsApp, that sign-off is also a product requirement: the "Add Language" action only appears once a template already has at least one Meta-approved variant, so translation always starts from wording that has already cleared review. From the template's detail page, an "Add Language" button opens a dialog where the team picks a target language from the ones not already covered, with AI translation switched on by default. Confirm, and the system translates the body, header, footer, and button text, then drops the team straight into the wizard's design step to review before anything goes near Meta for approval. Nothing skips the same submission process a template built from scratch would go through.

Email works differently, and at a different scale. There's no approval gate on the template itself, the "Translate" action on a template card works on any draft or active template, whether it was built from scratch in GuestMaker or arrived as an import from another platform, because a campaign is rarely destined for just one new market and its language family often gets drafted well before anyone signs off on the final copy. From a template card, a marketer can pick several target languages at once, not one at a time. GuestMaker creates a placeholder draft for each language immediately, then translates all of them in the background, in parallel, so the person who kicked it off is free to move on to the next thing rather than babysitting a progress bar. A banner says exactly that: the dialog can be closed, the translations keep running. Each draft updates live as it finishes, no page refresh required, and every one stays linked back to the original template it came from.

The parts that never move

What makes this more than a translation API bolted onto a template editor is what it is instructed to leave alone. The prompt behind both flows is built to preserve every merge variable, every URL, and every phone number exactly as written, while translating everything else into natural, idiomatic language rather than the stiff, obviously-machine-translated phrasing that gives AI copy away. The completeness rule goes further: every section and element in the source template has to survive into the translation. Nothing gets dropped because a paragraph looked skippable to a model doing its best.

And because a translated WhatsApp variation still has to pass Meta's approval process like any other template, it runs through the exact same compliance checks an English original would: URL buttons still have to resolve to a real HTTPS domain, phone number buttons still have to be in proper E.164 format, and a variable still can't sit in the middle of a URL path where Meta would reject it. If a translation ever did nudge something out of place, the same checks built for the original catch the variation too, before it reaches Meta at all. The same discipline decides whether a translated WhatsApp template earns Meta's approval, a separate submission with its own restrictions on where a variable can sit inside a button URL.

That name inside {{1}}, incidentally, is not a placeholder invented for the campaign. It is pulled from the same guest record that follows a person across every stay, message, and hotel in the group, which is exactly why the variable has to survive translation intact. Get it wrong in one language and that guest becomes a stranger to the campaign that was written for them.

Nothing ships until someone signs off

Translating five templates in one click is only useful if a person still gets the final say, and both flows are built around that. On WhatsApp, the wizard opens at the design step specifically so a human reviews and edits the AI's output before it's ever submitted for approval, not after. If the translation call fails for any reason, the dialog quietly falls back to the original, untranslated content and surfaces a warning, rather than silently shipping broken text or blocking the whole flow.

On email, every translated variant lands as a draft, explicitly not sent, not scheduled, not live. A marketer opens each one, reads it in context inside the same editor they'd use for any other campaign, and publishes when they're satisfied, exactly the review step a five-tab manual process was supposed to have all along but usually skipped once deadline pressure set in. It's the same checkpoint that also has to catch a discount that shouldn't reach an already-booked guest.

A wide list, deliberately not an infinite one

The language list here is curated rather than open-ended. GuestMaker doesn't claim to translate into every language spoken on Earth, and it shouldn't: a translation nobody at the hotel group can proofread is a risk, not a feature. What it does offer is a genuinely wide set spanning the markets a multi-brand hotel group actually operates in, available consistently across WhatsApp templates and email campaigns alike, so a group running properties across a dozen countries isn't stuck translating some of its channels by hand while others get the one-click treatment.

What this actually replaces

Picture a hotel group with properties across a dozen national markets, running one seasonal campaign that used to mean a shared spreadsheet, five browser tabs, and one person quietly responsible for making sure a Portuguese booking link didn't end up pointing at an English confirmation page. Now the same campaign gets approved once, in the group's working language, and a single translate action produces the rest of the language family in parallel, each version still carrying the same guest name, the same working link, the same real phone number, because those were never in play to begin with.

That's the actual value here: not the novelty of AI translation, which is common enough by now, but AI translation with a hard boundary drawn around exactly the four or five things in a hospitality message that were never meant to be translated at all. The CRM and its templates feed straight into journeys and campaigns without a second copy-paste step, so the language family a marketer approves today is what actually goes out to guests, in every market, unchanged where it has to be and genuinely well-written everywhere else.

See how the rest of GuestMaker's CRM fits together, or check pricing for your hotel group.