Calendars and bookings
Schedule events next to the work — several calendars, five views, bookable time slots and meeting links.
Calendars keep the week in the same app as the customer, the case and the task. Open them from the calendar icon in the top bar, or from Calendars if your organisation has the feature switched on.
Views and calendars#
Switch between five views: Month, Week, Day, Agenda and Year — Agenda lists the next two weeks. Create a calendar for each person, room or service — one per advisor, one for the clinic's rooms, one for site visits — and use New event to add something.
How service teams use them#
| Business | What goes on the calendar |
|---|---|
| Insurance and wealth advisory | Renewal reviews, portfolio reviews, claim surveys, callbacks |
| Clinics | Check-ups, follow-up appointments, room bookings |
| Real estate | Site visits and handovers |
| Agencies | Client reviews, workshops and deadlines |
Pair a calendar with a flow: when a card reaches Quote discussion, book the review; when the review is done, move the card on.
Bookings#
Bookings put clients into time slots for a service — a consultation, a check-up, a site visit. They're part of the Store feature: switch it on in Settings → Features, create a bookable product with its availability in a store, then book slots from the store's Bookings tab. Each store shows its bookings as a list or on a calendar.
Meeting links and apps#
klerc can create a meeting link for a call — see Through the API below. Google Calendar, Calendly, Cal.com, Zoom and Google Meet are all in the integrations catalogue; see Integrations for connecting them.
Reminders#
Workflows can send reminders ahead of the dates on your records — a check-up tomorrow, a review next week — from approved WhatsApp, SMS or email templates, and raise a task when a call works better.
Through the API#
Calendars live under /docs/api/calendars:
- list, read, create, update and delete calendars;
- list, read, create, update and delete events within a calendar;
POST /calendars/meetingcreates a meeting link.
Create an event with a title and its start and end:
POST /api/v1/calendars/{id}/events{ "title": "Renewal review — Ananya Rao", "start": "2026-09-18T12:00:00+05:30", "end": "2026-09-18T13:00:00+05:30"}The reference types start and end as strings; ISO 8601 timestamps with an offset, as above, are the safest choice. Reading needs calendars:view; changes need calendars:use. The reference doesn't document the request body for meeting links — see /docs/api/calendars.