Slot blocking — a closed hour, without inventing a fake client
Block a slot to close it to booking, without creating a fictitious appointment.
The problem
Closing an hour — a break, something unexpected — often requires inventing a fake appointment to fill the slot.
A fake client clutters the statistics and can, by mistake, receive a notification that makes no sense.
Blocking closes the slot without creating a client, without a notification, and without entering the revenue.
Without Kagenda
To close an hour, you have to create a fake appointment with an invented client.
With Kagenda
A block closes the slot directly, with no fictitious client or notification.
How it works in Kagenda
You block a slot directly from the calendar, like an appointment, but with no client.
- You select the slot to closeFrom any calendar view.
- You block it, with no clientNo client file gets created.
- The slot disappears from online bookingNo one is notified, nothing enters the revenue.
A block, not an appointment
- No client created
- No notification
- Slot closed
In practice
- 1
An unexpected break
The slot closes instantly, with no fake appointment.
BlockNo fictitious client - 2
Nothing in the statistics
The block never enters the revenue.
StatisticsNot affected - 3
No one is notified
No notification is sent for a block.
NotificationNone
Frequently asked questions
Does a block create a client file?
No, no file is created.
Does the block enter the revenue statistics?
No, it's completely excluded from them.
Can a slot be unblocked afterwards?
Yes, at any time, it becomes bookable again.
Does the client see why the slot is closed?
No, they simply see that the slot isn't available.
