HelpNotificationsWording & merge fields
Wording & merge fields
The words your visitors read are yours to write — on both WhatsApp and email, in each language you support, and differently per branch if you want.
Here's how, and the two small rules that stop a message going out broken.
Editing your wording
- Open the WhatsApp or Email page and pick a moment.
- Rewrite the message in your own voice. A live preview shows the result with sample details filled in.
- Save. Use Reset to default to go back any time — separately for each language you support.
The WhatsApp wording
- It has its own message, edited without touching email.
- Switching a moment off here does not silence email. The two are separate all the way through.
The email wording
- It has its own message, and its own subject line.
- It is headed by your business name, with your logo once you have uploaded one — on the trial as well as on a paid plan.
Merge fields
Drop a merge field in curly braces and turnda fills it in per visitor. Pick them from the chips above the editor rather than typing them.
| Merge field | Fills in with | Example |
|---|---|---|
| {{business_name}} | Your business name | Luxe Hair Studio |
| {{ticket_number}} | The visitor's ticket number | A-12 |
| {{area}} | The area they're in | Reception |
| {{station}} | The counter or chair called | Chair 2 |
| {{slot}} | The booking time | 3:30 pm |
| {{track_url}} | Their tracking link | turnda.tv/abc123 |
| {{booking_url}} | The page where they can change or cancel that booking | turnda.tv/b/abc123 |
| {{booking_ref}} | The booking's own reference | BK-4821 |
| {{review_url}} | Your Google review link, used by the review request | g.page/r/your-shop/review |
Mistype a merge field and saving is refused. The mistake is named, so a message can never reach a customer with a blank where a detail should be.
One business, different branches
Write the message once and every branch uses it. If one branch needs different words, open that location and edit it there — the rest carry on with the business-wide version.
Delete a branch's version to put it back on the business-wide one; nothing is retyped.
The two things you can't do
| Rule | Why |
|---|---|
| You can't remove the tracking link. | In any message carrying {{track_url}}, it has to stay — a message without it looks fine and quietly leaves the visitor stranded. The same goes for the review link in the review request. |
| There's a length limit of 1,000 characters. | Plenty for anything a queue message needs — the longest one turnda ships is under 200 — with room left for the details filled in at send time. |
Wording is set by the owner. Only the owner (or an account-wide manager) edits it — a location-scoped manager sees it read-only. It keeps your voice consistent across branches.