Agenda
Everything about the agenda that is the same for the whole company
Only an administrator can change the company agenda settings.
The booking rules
These apply to every calendar - a colleague cannot set them for themselves. Saving here writes them onto every existing agenda straight away.
Whether a booking made by a client waits for a yes or no.
The same for every colleague. It also sets the step between the moments a client is offered.
Reminder moments
Which of the two reminders a visit gets is decided per appointment type. These are the moments they go out at.
The reminder for tomorrow's appointments goes out at this hour, not exactly 24 hours before - predictable for the client and never at night.
How long before the visit the short reminder goes out. 60 minutes by default.
Appointment types
Each type carries its own length, colour and travel time.
Regions
Postcode ranges decide which inspectors a client is offered first. Ranges may overlap.
Try a postcode
See exactly who a client at that address would be offered, and in which order.
Public holidays
Imported automatically every week. Your changes here are never overwritten.
Online booking
Lets a visitor of your website pick a free moment with an inspector. Every booking from outside the CRM arrives as a REQUEST in the Agenda inbox - nobody fills your morning without your yes.
A copy of every website booking. Empty = the company address. The inspector is always notified separately.
A booking by somebody we do not know yet creates a lead - this is who owns it.
How the appointment types and the inspectors look on the public form. In their own colour means every card wears the colour it has in the agenda.
Comma-separated, scheme included (https://example.be). Empty = the widget refuses to render anywhere but here.
Embed on your website
Paste this where the booking form should appear. Add ?lang=nl or &postcode=2000 to the script URL to pre-set language and area.
API key (server-to-server)
Sent as the X-Api-Key header on POST /api/booking - that caller skips the CAPTCHA. Keep it server-side only, never in website code.
Copy it before saving - afterwards it is stored encrypted and shown masked.
Google Calendar
Two-way synchronisation with Google Workspace: appointments land on a colleague's phone within seconds and their own Google events block the moments clients can book. This card is the company key only - every colleague still connects their own calendar under Agenda settings - Phone & sync.
The whole key file of a Google Cloud service account with domain-wide delegation for the scope https://www.googleapis.com/auth/calendar.events. Stored encrypted and shown masked afterwards. A value that is not a key file is refused.
"primary" is the colleague's own main calendar. Change it only if everyone uses a separate work calendar with the same id.
Google echoes this back on every push notification, which is how the CRM knows the call is genuine. Needed only with live push on.
Whatever the push does not deliver is picked up by the CronJob "Google Calendar synchronisation" every few minutes - that is also the only path on an installation without a public https address.