Skip to main content

Blocking Time From Appointments

Add busy time in the calendar to block time and avoid unexpected appointments.

Paulius M. avatar
Written by Paulius M.
Updated this week

Blocking Time

Sometimes a break, a meeting, or a quick coffee is non‑negotiable. Busy time helps block time in the calendar so appointments cannot be booked over it.

Opening calendar

First, open the calendar where busy time will be added:

  1. Go to Calendar.

  2. Use the date navigation or click Go to today to find the correct day.

Open calendar

Adding busy time

Next, add a busy time block to prevent appointments in that period:

  1. In Calendar, click the desired time slot under the correct employee.

  2. In the pop‑up, click Add busy time.

  3. Select the date and time range for the busy time. This can be a short break or several hours – whatever is needed.

  4. Choose the employee if the busy time should apply to a specific staff member.

  5. Type a short note such as “Team meeting”, “Lunch break”, or “Admin work” to remember what this block is for.

  6. Click Save.

Add busy time details

Viewing busy time

After saving, the busy time appears in the calendar so it is clear when appointments cannot be booked:

  • The busy block shows directly in Calendar under the employee’s name.

  • The time range is visually blocked, just like an appointment, but marked as busy time.

Busy time in calendar

Editing or removing

Plans change – busy time can be adjusted at any moment:

  • To edit, click the busy time block in Calendar and update the time, date, employee, or note, then click Save.

  • To remove, open the busy time and click Remove busy time (or a similar delete option) so the slot becomes available for appointments again.

Booking warnings

If an appointment is created that overlaps with an employee’s busy time, a warning message appears to show that this time is blocked. This helps avoid double‑booking and keeps the calendar closer to “calm and organized” than “surprise appointment chaos”.

Busy time warning

Did this answer your question?