Configuring a location
Localization and design
Two related jobs: making the product speak your customers' language and use your industry's words, and making your public pages look like your business rather than like software.
Languages and region
Location settingsLocalization. Set per branch, so a bilingual shop and a monolingual one in the same chain can differ.
20 languages are offered, and a branch can support more than one — the first is its primary. Your customer messages can then have wording per language rather than forcing a choice.
Currency is chosen from GBP, EUR and USD, matching what the product can bill in. It is what service prices are shown in.
Saying it your way
“Customer” is wrong in a lot of businesses. A clinic has patients, a hotel has guests, a law firm has clients. Rather than making you live with our vocabulary, the words are yours to change, in three groups:
Business terms
The nouns the product uses about your world — customer, visit, party and the rest. Change them once and they change everywhere the customer sees them.
Each term is stored with its singular and plural forms rather than one word with an “s” bolted on, so languages with more complicated plural rules than English are handled properly.
Customer journey terms
The wording on the public pages themselves — the join page, the status page, the booking flow. This is where you change “Join the waitlist” into whatever your customers would actually say.
Email terms
Wording used in the surrounding furniture of your emails, so a branded template does not undercut itself with generic labels.
Change the nouns before you rewrite every message
A lot of what reads wrong in the default messages is one noun. Renaming “visit” to “appointment” or “customer” to “patient” fixes it everywhere at once, which is less work than editing eighteen messages.
Custom design
Account settingsCustom design controls how your public pages look: colours, fonts, button style, background and layout.
- Colour — a ready-made palette, or your own brand colour.
- Font — from a set of web-safe families.
- Button style — including corner rounding, from square to fully rounded.
- Layout and background — how the page is aligned, and what sits behind it.
Design is account-level, not per branch
The Custom designentry under location settings is a placeholder and does not configure anything yet. Every branch shares the account's design, which is usually what a chain wants anyway.
Check the result on a phone. Almost every customer sees these pages on one, and a colour that works on a monitor can be unreadable in daylight on a handset.
Display settings
Location settingsDisplay settingsis about your team rather than your customers: which details appear against each person on the waitlist, and which appear in today's activity list.
The two lists are configured separately, because they answer different questions. The live board wants the few things needed to call the next person; the activity list can afford more detail.
Three of the options — tags, booked time and assigned staff — are accepted but never drawn, because there is nothing behind them yet for a walk-in. Switching them on changes nothing rather than showing you blanks.
Less is usually better here
A row with eight details on it is slower to read at a busy counter than a row with three. Start with a name and a wait, and add only what your team actually asks for.
Account-level localization
Localization under account settings is a placeholder and does not configure anything yet. Set languages, currency and terminology per branch instead.