Help Center Bookings Connecting Timely to your clinic app
← Help CenterBookings

Connecting Timely to your clinic app

Connecting Timely does two things: it lets your app send patients to your Timely booking page, and it brings your Timely appointments into Front Desk so reception can see them and check patients in. This article explains how it works and what to expect.

Important

The Timely connection is a read-only calendar sync. We read your Timely appointments so they show up on Front Desk and match automatically to the right patient (by the email or phone on the booking) — but nothing is ever written back to Timely. Your booking system stays exactly as it is.

Why the connection matters

With it connected, tapping "Book" on a treatment in the app takes patients straight to your Timely booking page, and reception sees the day's Timely appointments right there on Front Desk when the patient checks in — no separate lookup.

Patients stay in your existing Timely booking system. Nothing changes in how you manage appointments, send confirmations or take deposits.

How it's set up

Connecting Timely is not self-serve — there is no dashboard screen for it. The Clinic App team sets it up for you directly, as part of your build. There's nothing to paste in or configure yourself.

Once it's connected, appointments booked in Timely appear automatically on Front Desk. There are no per-appointment links to manage and nothing for you to keep in sync — the read-only feed does that for you.

What patients see when they tap "Book"

Patients are taken to your Timely booking page to pick their appointment. There's no deep link to a specific already-booked appointment in Timely — rescheduling or cancelling an existing booking is always handled through Timely itself, the same as today.

If something looks wrong

If a booking link looks broken, or a Timely appointment isn't showing up correctly on Front Desk, message the Clinic App WhatsApp group and we'll sort it out — this is one of the things we look after for you, not something to troubleshoot yourself.

Was this article helpful?