What’s new in Retime: booking on your own website

June was about what happens after someone books. The last two months were about where the booking happens.

A Retime link works well when you can send it. It works less well when someone is already on your site, or in your shop, and asking them to leave feels like a step backwards. So we spent July and August putting the booking page where your customers already are.

Here is what is new.

Put your booking page on your own website

You can now embed a Retime booking page directly in your own site.

Add your website under your organisation settings. Retime issues an embed key and only accepts the domains you list, so nobody else can use your booking page inside their own pages. Then drop one script tag on the page where you want it. Guests pick a time and confirm without ever leaving your site.

If you are on a paid plan, you can set the widget’s accent colour to match your brand, and turn off the “Powered by Retime” mark.

A Retime app for Shopify

Merchants can install Retime Booking from their Shopify admin and place a booking block into any theme section.

The block configures itself once the store is connected, so there is no key to copy or paste. You can see a real preview inside the theme editor while you position it, and set the accent colour there too. It suits anyone selling something that needs a conversation first: fittings, consultations, installations, repairs.

Two more calendars: Apple iCloud and Zoho

Retime now connects to Apple iCloud Calendar and Zoho Calendar.

Both work the way Google Calendar and Office 365 already do. Retime reads them to know when you are busy, and writes each booking back so the event lands on the calendar you actually look at. Apple connects with an app-specific password from your Apple account, and Zoho routes through your own data centre region.

We also gave every stored calendar credential encryption at rest, so a connected calendar is a connected calendar and nothing more.

Retime in Persian, on the Shamsi calendar

Retime now speaks Persian.

Switch the interface language from your account, and the whole app follows: menus, settings, plan names, time zones, and emails. Dates are shown on the Shamsi calendar for accounts that prefer it, and prices appear in Toman.

Your guests get the same choice. A public booking page can be viewed in either calendar system, so a guest can pick a time in the calendar they think in, even when you do not share it.

Build on Retime

Two things landed for anyone connecting Retime to their own tools.

You can create a personal API key from your account settings, so a script or an automation can hold a long-lived credential instead of borrowing your session. And there is now a bookings feed you can poll, which is the shape that tools like Zapier and Make expect when they check for new work.

The booking webhooks from June also carry more of the booking in each payload, so fewer integrations need a second call to fill in the details.

A dashboard that shows up fast

This one is hard to photograph and easy to feel.

The dashboard used to wait for its whole JavaScript bundle before it drew anything. Pages now render on the server, so content appears while the rest loads behind it.

• First paint went from 2 to 4 seconds down to under half a second.
• Shared JavaScript went from 623 kB to 311 kB.
• The average page went from 899 kB to 385 kB.

Fonts are subset and modern-format only, analytics and error replay load after the page is idle, and heavy tools like the rich text editor, the image cropper, and the spreadsheet exporter only download when you actually reach for them.

Bookings you can trust

The least visible work, and some of the most important.

• Two guests can no longer take the same slot. Booking now takes a lock on the slot and on the host, so a race between two people finishes with one booking and one honest “that time just went”.
• Public booking pages are protected against bots, with rate limits kept separate per surface so a flood in one place cannot starve another.
• Google Calendar got stable event ids, request timeouts, and retries that only repeat what is safe to repeat. A calendar that briefly disconnects is now detected and retried once it returns, instead of quietly falling behind.
• Every booking change is recorded in an append-only trail, so “who moved this meeting” has an answer.
• Small things: duplicate an existing booking link instead of rebuilding it, see at a glance whether a link’s calendar is syncing, and apply a promotion code at checkout.

Where a booking link belongs

The thread this time is placement.

A booking page is most useful at the moment someone decides they want to talk to you. That moment usually happens on your website, in your shop, or inside a tool you already run your day in. Every release above moves the booking closer to that moment, and tries to make it faster and harder to break once it gets there.

Create your next booking link and put it where your customers already are.