Time off per resource — an absence without closing the whole business
Each resource can have its own time off, without affecting the others.
The problem
A sick person or a room under renovation doesn't mean the whole business grinds to a halt.
Closing the entire diary for a single absence blocks bookings that have nothing to do with it.
Without time off specific to each resource, the only option is to refuse appointments by hand, one by one.
Time off set on a resource removes its slots, and lets the rest of the business run normally.
Without Kagenda
An employee is off for a week. To stop her from receiving appointments, every request has to be refused one by one.
With Kagenda
Her week off is set once. Her slots disappear, her colleagues' stay intact.
How it works in Kagenda
Time off is set on the resource in question, for a one-off or recurring period.
- You set the periodA date, a week, or a recurrence, on the resource in question.
- Its slots disappearOnline booking stops offering this resource during the period.
- The existing diary is untouchedAppointments already booked before the time off stay visible.
Time off set on the resource
- Period blocked
- Slots removed
- Rest of team unchanged
In practice
- 1
A week off
Set on a single person, it doesn't affect anything else in the business.
Time off set1 person, 1 week - 2
A room under renovation
Closed for two days, without cancelling appointments that don't depend on it.
Room availableRoom closed 2 days - 3
A recurring day off
A practitioner absent every Monday needs only a single setting.
RecurrenceEvery Monday
Frequently asked questions
Does time off on a resource block the whole business?
No, only the resource in question becomes unavailable.
Can time off be recurring?
Yes, a fixed day every week, for example.
What happens to appointments already booked during the time off?
They stay in the diary. Time off only blocks new bookings.
Can time off be set for a room, not just a person?
Yes, time off can be set on any type of resource.
