tstrobl

This is how I did it:

1. Create a service “blocker”. Set duration to the smallest you may need, e.g. 15min. Configure custom durations up to the max duration you may need (e.g. 2 hours). Set service visibility in the web to “off” (means you can only “book” the blocker off-line in the back-end).
2. Create a dummy customer with an easy name (e.g. first name “block”, surname “block”).
3. Whenever you want to block time slots directly from the Amelia calendar, book offline the “blocker” service. Associate it with the employee whose availability you want to block for bookings.
4. Amelia staff, should you be reading this: adding a “blocker” functionality just like above, but without the need to link it to a customer (and hence go through everything that regular customers have to do during booking, e.g. click mandatory custom fields) would be phantastic. That’s a functionality that’s often required in day-to-day-work and it should be easy to implement. And no: going to employee “special days” every time, when this is spontaneously needed, is not a practical idea.

[post script: I came to realize you can actually switch off mandatory custom fields for individual services. So, when doing that, the procedure I described above is actually a good workaround for me]

• This reply was modified 3 years, 5 months ago by tstrobl.