Multilingual booking
One booking calendar, every customer's language.
Set the locale and texts per event type, and Zaptime renders dates, weekdays and labels the way that customer expects. Time zones are detected automatically, and every email shows the meeting in the attendee's local time.
Switch the language and zone. This is the calendar your customers see.
What you get
Four layers, each under your control.
Locale, texts, time and week, emails. Set once per event type, applied to every booking that comes through it.
1. Locale
Pick one of 17 locales per event type: English, German, Spanish, Italian, Portuguese, Dutch, Swedish, Finnish, Polish, Czech, Slovak, Romanian, Turkish, Japanese, Korean, Chinese, Vietnamese. It drives month names, weekday names and date formats in the calendar.
2. Texts
Every string on the booking page is a field you can edit: headline, "pick a time", "confirm booking", form labels, add guest, back. Write them in the language of the page. Weekday headers can be overridden too.
3. Time and week
Choose the first day of the week per event type. The clock follows the visitor's device, with a 12h / 24h toggle on the page. Slots are shown in the visitor's detected time zone, with a searchable picker to change it.
4. Emails
The attendee's time zone is saved on the booking. Confirmation, reminder, reschedule and cancellation emails show the meeting in that zone with the zone name spelled out. An .ics invite is attached to every confirmation, so calendar apps place it correctly.
Per event type
A German page and an English page, side by side.
Locale and texts belong to the event type, not the account. Create "Beratung (30 Min.)" in German for your DACH customers and "Consultation (30 min)" in English for everyone else. Both connect to the same calendars, the same availability rules and the same team. Share different links, or embed different calendars on different language versions of your site.

Kate Novak
Beratung (30 Min.)
30 Minuten · Europe/Berlin
zaptime.app/kate/beratung

Kate Novak
Consultation (30 min)
30 minutes · your time zone
zaptime.app/kate/consultation
Time zones
The moment stays the same. Only the clock changes.
Availability is defined in your own zone per schedule, so a 9 to 5 in Prague stays a 9 to 5 in Prague when daylight saving flips.
Detected from the browser
No "please select your time zone" step. Visitors see slots in their own zone straight away.
Overridable
A searchable picker, by city or zone name, sets the zone the attendee will actually be in on the day.
Kept for good
The zone is stored with the booking. Emails, the cancel page and the invite all agree.
Attendee emails
Write the template once per language.
Email templates are visual, with merge tags for first name, last name, date, time zone, location, event name, duration and a cancel link. Create a template per language and attach it to the matching event type through Workflows, so German bookings get German emails and English bookings get English ones. Built-in subjects and wrappers ship in English, Czech and Polish. The template body can be in any language.
Czech names get proper vocative declension in greetings: "Ahoj Tomáši", not "Ahoj Tomáš".
Embed
Locale is a config key.
The Vue and vanilla SDKs take locale, week start and text overrides as configuration. Render one calendar per language route on your site, or switch the config from your own i18n setup at runtime. Time zone and clock format are picked up from the visitor's device.
<ZaptimeCalendar
:config="{
token: 'YOUR_TOKEN',
locale: {
preset: 'de',
startDayOfWeek: 'mon',
texts: {
introduction: 'Online-Termin mit Kate',
chooseDate: 'Datum wählen',
pickTime: 'Uhrzeit wählen',
},
confirmationForm: {
buttons: { confirmBooking: 'Buchung bestätigen' },
},
},
}"
/>Included in Free.
Localised formats, editable texts, time zone detection and attendee emails are on the free plan. Reminders, custom sending domains and Workflows are on Professional.
Frequently asked questions
Is the booking page translated into 17 languages?
The calendar's dates, month and weekday names are, from 17 locales. The page's own labels ship in English and are fully editable per event type, in whatever language the page needs. Translated defaults for every locale are on the roadmap.
Does Zaptime detect the customer's language?
No. The locale is fixed per event type, which keeps each booking page predictable. To serve several languages, create one event type per language and share or embed the matching one.
How does the customer's time zone get detected?
From the browser, using the device's time zone setting. The visitor can change it on the page. The final zone is stored with the booking.
Can I send emails in the customer's language?
Yes, by creating a template per language and attaching it to the matching event type in Workflows. The body is fully yours. Built-in subjects and wrappers are available in English, Czech and Polish.
Which languages does the Zaptime dashboard come in?
English and Czech. The booking page and emails your customers see are independent of your dashboard language.
Do time zone and locale work in the embedded calendar too?
Yes. The embedded calendar and the hosted booking page share the same engine and configuration.
Can my AI assistant create localised event types?
Yes. Through the MCP server on paid plans, a prompt like "create a 30-minute consultation in German, Berlin time" sets the locale and schedule for you.