Creating Non-WO Events
All Day Non-WO Event
You can create an All-Day non-WO event for a technician when they are unavailable for the entire working day. You can create this event for the technician from DC, SFDC, or from the Service Board. Schedule Optimization does not assign WOs during the time span of the All-Day events for technicians.
Example: If a technician has a medical appointment and is unavailable for the entire day, you can create an All-Day non-WO event for them. This ensures that Schedule Optimization does not assign any work orders to the technician on that day.
* 
Make sure to enable the All-Day checkbox while creating an all-day event.
Multi-Day Non-WO Event
You can create a Multi-Day non-WO event that spans across multiple days (e.g., from Day 1 at 10 am to Day 2 at 12 pm). You can create this event for a technician from DC, SFDC, or from the Service Board. Schedule Optimization does not assign WOs during the time span of the multi-day event, but it assigns WOs before and after the event within the technician's working hours.
Example: If a technician is attending a training session from 10 am on Monday to 12 pm on Tuesday, you can create a Multi-Day non-WO event. This ensures that Schedule Optimization does not assign any work orders to the technician during this period, but it can still assign work orders before 10 am on Monday and after 12 pm on Tuesday.
Non-WO Events With or Without Location
You can create non-WO events to block a technician's calendar for a considerable amount of time in a day. Schedule Optimization does not assign WOs during the time span of a non-WO event, but it assigns WOs before and after the event within the technician's working hours.
* 
If a technician's working hours are from 10 am to 6 pm, you can create a non-WO event for any duration within these hours. However, you should not create a non-WO event from 10 am to 6 pm. In such cases, you must create an All-Day event.
You can also provide a non-WO event with a geo-location (latitude/longitude or address). In such cases, the drive time is calculated for the event.
Example: If a technician has a meeting from 2 pm to 4 pm, you can create a non-WO event for this period. This ensures that Schedule Optimization does not assign any work orders to the technician during the meeting time, but it can still assign work orders before 2 pm and after 4 pm.
Was this helpful?