Modules · Meeton Calendar · Steps 3 and 4
Who & when
Which members host, how invitees combine, and the hours, buffers and notice that decide which slots a visitor is offered.
Step 3 · Who
| Invitee mode | Rule |
|---|---|
| All | All of them are invited. A time is offered only when everyone is free. |
| Any | One of them is invited. A time is offered when at least one is free; round-robin picks who. |
| Split | One person from each list is invited. A time needs someone free in every list, for example one from sales and one from solutions. |
Each host connects their own calendar so free and busy time is real: Google Calendar, Microsoft 365 or Garoon. Meeton reads invitees' free times and creates the event in that calendar. Without a connection, Meeton offers your bookable hours and records the booking.
Step 4 · When
Availability is read live at the moment the visitor looks; nothing is cached beyond the request.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Fewer slots than expected | Buffers before and after, the slot interval and the minimum notice all subtract from the window | Loosen one at a time and check the visitor's view. |
| A host is never picked | Their calendar is disconnected, or their working hours do not overlap the booking window | Reconnect under Integrations; check the availability calendar's hours. |
| Holidays are not skipped | The availability calendar has no region, or the wrong one | Set the region per availability calendar. |
Frequently asked questions
Does each host need their own connection?
Yes. Free and busy time is read from each host's own Google, Microsoft 365 or Garoon calendar, and the event is created there.
Is availability cached?
No. It is read live at the moment the visitor looks, so a meeting added seconds ago already blocks its slot.