(Created target blank page For Version: PSAAS:Julie) |
(Update with the copy of version: Public) |
||
Line 1: | Line 1: | ||
− | + | = Calendar Management= | |
+ | |||
+ | Workforce Management’s (WFM) unique agent-based scheduling approach enables robust agent-calendar management prior to scheduling. WFM can incorporate known obligations into agent schedules to ensure that agents can keep appointments and request adjusted shifts or working hours while WFM maximizes contact-center efficiency. By more accurately planning for known obligations, WFM can take the guesswork out of forecasting for staffing overheads, leading to more efficient use of the agent pool. | ||
+ | |||
+ | {{AnchorDiv|PSMtg}} | ||
+ | == Planning and Scheduling Meetings== | ||
+ | The Meeting Planner provides great flexibility when planning meetings. You select the meeting participants, define the range of time in which the meeting should occur, and set the duration of the meeting. You can configure recurring meetings, specifying either the number of occurrences or the start and end dates of the meeting series and the interval (weekly, for example). | ||
+ | |||
+ | The Meeting Scheduler builds the meeting into the work schedules of the participants during the scheduling process, finding the optimal times for agents’ shifts and the meeting at the same time. | ||
+ | |||
+ | The meeting is included as an exception in all attendees’ schedules. WFM displays the meeting exception in the Schedule views using the meeting short name, so you can find it easily when looking at schedules. If a sufficient percentage of participating agents is unavailable, then the meeting is not scheduled, and you receive a warning. | ||
+ | |||
+ | === Additional Functionality=== | ||
+ | '''Use the Meeting Scheduler...''' | ||
+ | *To insert meetings directly into multiple agent schedules as an exception after building the schedule. | ||
+ | *To create optimally-scheduled meetings within an existing schedule. | ||
+ | |||
+ | '''Use the Meeting Planner...''' | ||
+ | *To configure meetings that are pre-planned, such as recurring team meetings. | ||
+ | |||
+ | '''Play ‘what if’...''' | ||
+ | *To add a meeting to a schedule that has already been built, and WFM will insert the meeting into the most optimal time slot, based on the list of participants. | ||
+ | |||
+ | Supervisors can use this feature to better determine the optimal meeting times that otherwise required manual calculation or guesswork. | ||
+ | |||
+ | {{AnchorDiv|TOff}} | ||
+ | == Time Off== | ||
+ | You can use the WFM Web's '''Time Off Types''' module to configure multiple types of time off. Doing so enables you to set different characteristics for each type, define different rules for the accumulation of | ||
+ | accrued time off and distribution of awarded time off, and fine-tune your record-keeping using the Time Off Report. | ||
+ | |||
+ | Time off can be accrued or awarded. The settings for these differ slightly, but both are configured in the WFM Web’s '''Time-Off Rules''' module. You can configure separate time-off rules for each time-off type, or assign several time-off types to the same time-off rule, meaning all of the time-off types assigned to this rule share the time-off balance. | ||
+ | |||
+ | You can also associate multiple time-off rules with one time-off type. For example, you might want to have different accrual rules for agents with more seniority than for those who were recently hired. By assigning the appropriate time-off rule to each agent who receives time off of that type, you can determine the rate at which each agent accrues the time off. | ||
+ | |||
+ | Use the '''Calendar''' module in WFM Web for Supervisors to set time-off limits. You can set time-off limits for an activity, for a team, or for an entire site. You can also set different time-off limits for a specified period. For example, you might want to further limit time off because of special circumstances. | ||
+ | |||
+ | You can also set different time-off limits for various periods during the day. For example, you might permit more time off in the evening than in the busier morning. | ||
+ | |||
+ | Agents can view their balances for each time-off type and request time off in WFM Web for Agents. Agents can request both full-day and part-day time off. Supervisors can enter time-off requests into the WFM Web for Supervisors | ||
+ | '''Calendar''' module. | ||
+ | |||
+ | Requested time off can be manually approved by the supervisor or automatically approved by WFM Web, based on agent time-off balances and the limits set on the number of agents with time off per activity, team, or site. | ||
+ | |||
+ | When the Scheduler runs, all time off that has been granted is scheduled. Additional time off can be scheduled, depending on whether it meets time-off limits and scheduling optimization constraints. Once time off is scheduled, | ||
+ | agents can no longer edit or remove the time-off assignment using WFM Web for Agents. | ||
+ | |||
+ | === Time Off Wait-List=== | ||
+ | When a time-off request is made, but time off limits have already been reached, if the agent asks for the request to be wait-listed, the request remains in the WFM Calendar in a '''Preferred''' status, rather than being declined. Supervisors can view this ''wait list'' in the Calendar, sorting the time off requests by timestamp, and selectively grant time off requests. | ||
+ | |||
+ | Supervisors can grant agent time off for future periods, if the time off limits are raised, or if other agents cancel their existing requests. This improves supervisor productivity by no longer requiring them to track these requests | ||
+ | with a paper-based system. | ||
+ | |||
+ | Your supervisor can enable automatic approval (also known as ''auto-granting''), which eliminates the need for that supervisor to approve your legitimate time-off requests. | ||
+ | |||
+ | === Time Off Within Bidding Periods=== | ||
+ | You can enable Time-Off Bidding by configuring bidding periods in WFM Web and associating them with sites within your enterprise. Agents within the site can submit multiple time off requests concurrently and WFM processes them within the specified bidding period. This configuration ensures that agent requests are all granted, declined, or wait-listed on the same processing date and eliminates the possibility of some requests for a vacation period being granted, while others are not. For details, see [[TimeOffBid|Time-Off Bidding]]. | ||
+ | |||
+ | {{AnchorDiv|SchExc}} | ||
+ | == Schedule Exceptions== | ||
+ | ''Exceptions'' are additions to a schedule that are not work, but which must be taken into account to allocate agent time correctly. Examples of exceptions include meetings, training, and special projects. | ||
+ | |||
+ | ===Exception Types=== | ||
+ | You create exception types based on the needs of your contact center. These types can be extremely flexible and you can link them to other WFM scheduling features. For example, you can specify that some exception types are used in meeting planning, and that some can be converted to a day off, if necessary. | ||
+ | |||
+ | Exceptions can be full-day or part-day. You can assign multiple part-day exceptions, assuming they do not overlap or otherwise violate internal WFM consistency checks. | ||
+ | |||
+ | {{AnchorDiv|PybckExcp}} | ||
+ | === Payback Exceptions=== | ||
+ | Payback exceptions are unpaid part-day work intervals that are inserted into schedules to make up for missed time due to lateness or personal appointments. Supervisors and agents can insert these exceptions and specify payback options to recoup missed time. | ||
+ | |||
+ | Payback exceptions might not be applicable or required in all sites, business units, or contact centers. To enable this functionality, contact your Genesys representative. | ||
+ | |||
+ | For information about how supervisors and agents can use payback exceptions, see [[Documentation:WM:SHelp:MIAInsExcWthPbck|Insert Exceptions with Payback]] in the ''[[Documentation:WM:SHelp:Welcome|Workforce Management Web for Supervisors Help]]'' and [[Documentation:WM:AArkHelp:AddExcp#ExcpPbck|Inserting Payback Exceptions]] in the ''[[Documentation:WM:AArkHelp:Welcome|Workforce Management Agent Help]]''. | ||
+ | |||
+ | {{AnchorDiv|ExcpMmos}} | ||
+ | === Exception Memos=== | ||
+ | You can add Exception memos in Schedules, Calendar items, and Meetings to provide comments or additional information about Exceptions types. Exception memos can contain up to 256 characters. | ||
+ | |||
+ | {{AnchorDiv|CalMmos}} | ||
+ | ==== Memos in Calendar Items==== | ||
+ | When you create Exception memos in Calendar items, they are visible in the Schedule views after they are scheduled, and preserved if transferred between Schedule scenarios, from Scenario to Master Schedule, or from Master to Schedule Scenario. If you edit the memo in the Calendar, the schedule reflects the change without having to be rebuilt or republished. | ||
+ | |||
+ | If this same memo is in the schedule (rather than in Calendar items), it is not saved in the Calendar. Instead, WFM creates a new memo that is related to this scheduled Exception. This newly-created memo is not related to the Calendar item. Therefore, changing the original memo in the Calendar item does not affect this instance of the scheduled Exception—it is a separate memo. | ||
+ | |||
+ | {{NoteFormat|You can create an Exception memo in the schedule, even if you have created an Exception without a memo in Calendar items. Again, the scheduled Exception memo is not synchronized with the Calendar item Exception and will not reflect any modifications made to Exception memo in the schedule. See [[WMCalendar#SchdMmos|Memos in Schedule Views]].|2}} | ||
+ | |||
+ | If you delete an Exception and its memo in the Calendar, it will no longer be visible in the schedule. However, you can enter a new memo for the Exception that is not related to the Calendar item. If there are multiple instances of an Exception in multiple scenarios and/or the Master Schedule and you delete the related Calendar item, all instances become separate Exceptions. | ||
+ | |||
+ | When you change a memo in a scheduled Exception the change is reflected in the schedule audit and history. If the settings for the Exception type allow, scheduled Exception memos are swapped and traded with Exceptions. If a calendar-related memo is swapped or traded, WFM copies it to the schedule and disassociated it from the calendar. | ||
+ | |||
+ | Exception memos are displayed: | ||
+ | *In the '''Details''' bar at the bottom of the '''Schedule Intra-Day''' and '''Agent-Extended''' views. | ||
+ | *Next to the scheduled '''Exception Type Name''' in the '''Individual Schedule''' and '''Team Schedule''' reports. | ||
+ | *In the schedule details (and printed schedule details) for the Web for Agents > '''My Schedule''' view, in a manner similar to the reports. | ||
+ | |||
+ | {{AnchorDiv|SchdMmos}} | ||
+ | ==== Memos in Schedule Views==== | ||
+ | While creating new Exceptions in the Schedule Scenario or Master Schedule that are not associated with a Calendar item, you can also add and edit an Exception memo. You can edit Exception memos that have been inserted directly into the schedule and initially created without memos or those that became schedule-only Exceptions after the related Calendar item was deleted. (See [[WMCalendar#CalMmos|Memos in Calendar Items]].) However, each Exception is edited separately, even if they were inserted using the '''Insert Multiple''' wizard. | ||
+ | |||
+ | {{NoteFormat|Due to the size limitations for an entire scheduling day, the memo might not fit into the schedule if there are multiple exceptions with long memos in the same agent day.}} | ||
+ | |||
+ | Exception memos are published or extracted to and from the Master Schedule along with Exceptions, and are transferred when you create scenarios, based on data from another scenario or data taken from the Master Schedule. They are also committed (together with Exceptions) from the agent's schedule to the the Master Schedule. However, unlike Exception memos created in Calendar items, after publishing or creating schedules, the link between Exceptions is not maintained and editing one instance of a memo does not change other instances. | ||
+ | |||
+ | After the schedules are published, the memos appear in the '''Details''' bar at the bottom of the Schedule > Intra-Day and Schedule > Agent Extended views. You might not see the entire memo, depending on the length of the memo or number of characters. However, when editing the memo, the entire memo text is displayed. | ||
+ | |||
+ | {{AnchorDiv|MeetMmos}} | ||
+ | ==== Memos in Meeting Exceptions==== | ||
+ | Entering memos in Meeting Exceptions is not quite the same as adding Exception memos in the Calendar or Schedule views. In the meeting '''Properties''' settings, the '''Meeting Name''' field can include a short memo, further describing the type or purpose of the meeting. For example, <tt>exception_name, meeting_name (exception_memo)</tt>. Together with the '''Meeting Name''' and '''Exception Type''' this memo is displayed in published schedules, just as exception memos are for Calendar items and Schedule views. | ||
+ | |||
+ | === Exceptions and Preferences Hierarchy=== | ||
+ | Exceptions and preferences are ranked in a hierarchy. This means that, if multiple exceptions and preferences are assigned for an agent on a single day, Calendar Management analyzes the assignments and immediately selects the highest-priority exception for assignment, noting the others as declined. | ||
+ | |||
+ | However, declined exceptions and preferences are stored in the WFM database, in case there are changes to calendar information later. If, for example, a training session is canceled, an agent’s previously overridden day-off preference might then change status and be available for scheduling. | ||
+ | |||
+ | [[Category:V:PSAAS:Julie]] |
Revision as of 16:59, June 7, 2019
Contents
Calendar Management
Workforce Management’s (WFM) unique agent-based scheduling approach enables robust agent-calendar management prior to scheduling. WFM can incorporate known obligations into agent schedules to ensure that agents can keep appointments and request adjusted shifts or working hours while WFM maximizes contact-center efficiency. By more accurately planning for known obligations, WFM can take the guesswork out of forecasting for staffing overheads, leading to more efficient use of the agent pool.
Planning and Scheduling Meetings
The Meeting Planner provides great flexibility when planning meetings. You select the meeting participants, define the range of time in which the meeting should occur, and set the duration of the meeting. You can configure recurring meetings, specifying either the number of occurrences or the start and end dates of the meeting series and the interval (weekly, for example).
The Meeting Scheduler builds the meeting into the work schedules of the participants during the scheduling process, finding the optimal times for agents’ shifts and the meeting at the same time.
The meeting is included as an exception in all attendees’ schedules. WFM displays the meeting exception in the Schedule views using the meeting short name, so you can find it easily when looking at schedules. If a sufficient percentage of participating agents is unavailable, then the meeting is not scheduled, and you receive a warning.
Additional Functionality
Use the Meeting Scheduler...
- To insert meetings directly into multiple agent schedules as an exception after building the schedule.
- To create optimally-scheduled meetings within an existing schedule.
Use the Meeting Planner...
- To configure meetings that are pre-planned, such as recurring team meetings.
Play ‘what if’...
- To add a meeting to a schedule that has already been built, and WFM will insert the meeting into the most optimal time slot, based on the list of participants.
Supervisors can use this feature to better determine the optimal meeting times that otherwise required manual calculation or guesswork.
Time Off
You can use the WFM Web's Time Off Types module to configure multiple types of time off. Doing so enables you to set different characteristics for each type, define different rules for the accumulation of accrued time off and distribution of awarded time off, and fine-tune your record-keeping using the Time Off Report.
Time off can be accrued or awarded. The settings for these differ slightly, but both are configured in the WFM Web’s Time-Off Rules module. You can configure separate time-off rules for each time-off type, or assign several time-off types to the same time-off rule, meaning all of the time-off types assigned to this rule share the time-off balance.
You can also associate multiple time-off rules with one time-off type. For example, you might want to have different accrual rules for agents with more seniority than for those who were recently hired. By assigning the appropriate time-off rule to each agent who receives time off of that type, you can determine the rate at which each agent accrues the time off.
Use the Calendar module in WFM Web for Supervisors to set time-off limits. You can set time-off limits for an activity, for a team, or for an entire site. You can also set different time-off limits for a specified period. For example, you might want to further limit time off because of special circumstances.
You can also set different time-off limits for various periods during the day. For example, you might permit more time off in the evening than in the busier morning.
Agents can view their balances for each time-off type and request time off in WFM Web for Agents. Agents can request both full-day and part-day time off. Supervisors can enter time-off requests into the WFM Web for Supervisors Calendar module.
Requested time off can be manually approved by the supervisor or automatically approved by WFM Web, based on agent time-off balances and the limits set on the number of agents with time off per activity, team, or site.
When the Scheduler runs, all time off that has been granted is scheduled. Additional time off can be scheduled, depending on whether it meets time-off limits and scheduling optimization constraints. Once time off is scheduled, agents can no longer edit or remove the time-off assignment using WFM Web for Agents.
Time Off Wait-List
When a time-off request is made, but time off limits have already been reached, if the agent asks for the request to be wait-listed, the request remains in the WFM Calendar in a Preferred status, rather than being declined. Supervisors can view this wait list in the Calendar, sorting the time off requests by timestamp, and selectively grant time off requests.
Supervisors can grant agent time off for future periods, if the time off limits are raised, or if other agents cancel their existing requests. This improves supervisor productivity by no longer requiring them to track these requests with a paper-based system.
Your supervisor can enable automatic approval (also known as auto-granting), which eliminates the need for that supervisor to approve your legitimate time-off requests.
Time Off Within Bidding Periods
You can enable Time-Off Bidding by configuring bidding periods in WFM Web and associating them with sites within your enterprise. Agents within the site can submit multiple time off requests concurrently and WFM processes them within the specified bidding period. This configuration ensures that agent requests are all granted, declined, or wait-listed on the same processing date and eliminates the possibility of some requests for a vacation period being granted, while others are not. For details, see Time-Off Bidding.
Schedule Exceptions
Exceptions are additions to a schedule that are not work, but which must be taken into account to allocate agent time correctly. Examples of exceptions include meetings, training, and special projects.
Exception Types
You create exception types based on the needs of your contact center. These types can be extremely flexible and you can link them to other WFM scheduling features. For example, you can specify that some exception types are used in meeting planning, and that some can be converted to a day off, if necessary.
Exceptions can be full-day or part-day. You can assign multiple part-day exceptions, assuming they do not overlap or otherwise violate internal WFM consistency checks.
Payback Exceptions
Payback exceptions are unpaid part-day work intervals that are inserted into schedules to make up for missed time due to lateness or personal appointments. Supervisors and agents can insert these exceptions and specify payback options to recoup missed time.
Payback exceptions might not be applicable or required in all sites, business units, or contact centers. To enable this functionality, contact your Genesys representative.
For information about how supervisors and agents can use payback exceptions, see Insert Exceptions with Payback in the Workforce Management Web for Supervisors Help and Inserting Payback Exceptions in the Workforce Management Agent Help.
Exception Memos
You can add Exception memos in Schedules, Calendar items, and Meetings to provide comments or additional information about Exceptions types. Exception memos can contain up to 256 characters.
Memos in Calendar Items
When you create Exception memos in Calendar items, they are visible in the Schedule views after they are scheduled, and preserved if transferred between Schedule scenarios, from Scenario to Master Schedule, or from Master to Schedule Scenario. If you edit the memo in the Calendar, the schedule reflects the change without having to be rebuilt or republished.
If this same memo is in the schedule (rather than in Calendar items), it is not saved in the Calendar. Instead, WFM creates a new memo that is related to this scheduled Exception. This newly-created memo is not related to the Calendar item. Therefore, changing the original memo in the Calendar item does not affect this instance of the scheduled Exception—it is a separate memo.
If you delete an Exception and its memo in the Calendar, it will no longer be visible in the schedule. However, you can enter a new memo for the Exception that is not related to the Calendar item. If there are multiple instances of an Exception in multiple scenarios and/or the Master Schedule and you delete the related Calendar item, all instances become separate Exceptions.
When you change a memo in a scheduled Exception the change is reflected in the schedule audit and history. If the settings for the Exception type allow, scheduled Exception memos are swapped and traded with Exceptions. If a calendar-related memo is swapped or traded, WFM copies it to the schedule and disassociated it from the calendar.
Exception memos are displayed:
- In the Details bar at the bottom of the Schedule Intra-Day and Agent-Extended views.
- Next to the scheduled Exception Type Name in the Individual Schedule and Team Schedule reports.
- In the schedule details (and printed schedule details) for the Web for Agents > My Schedule view, in a manner similar to the reports.
Memos in Schedule Views
While creating new Exceptions in the Schedule Scenario or Master Schedule that are not associated with a Calendar item, you can also add and edit an Exception memo. You can edit Exception memos that have been inserted directly into the schedule and initially created without memos or those that became schedule-only Exceptions after the related Calendar item was deleted. (See Memos in Calendar Items.) However, each Exception is edited separately, even if they were inserted using the Insert Multiple wizard.
Exception memos are published or extracted to and from the Master Schedule along with Exceptions, and are transferred when you create scenarios, based on data from another scenario or data taken from the Master Schedule. They are also committed (together with Exceptions) from the agent's schedule to the the Master Schedule. However, unlike Exception memos created in Calendar items, after publishing or creating schedules, the link between Exceptions is not maintained and editing one instance of a memo does not change other instances.
After the schedules are published, the memos appear in the Details bar at the bottom of the Schedule > Intra-Day and Schedule > Agent Extended views. You might not see the entire memo, depending on the length of the memo or number of characters. However, when editing the memo, the entire memo text is displayed.
Memos in Meeting Exceptions
Entering memos in Meeting Exceptions is not quite the same as adding Exception memos in the Calendar or Schedule views. In the meeting Properties settings, the Meeting Name field can include a short memo, further describing the type or purpose of the meeting. For example, exception_name, meeting_name (exception_memo). Together with the Meeting Name and Exception Type this memo is displayed in published schedules, just as exception memos are for Calendar items and Schedule views.
Exceptions and Preferences Hierarchy
Exceptions and preferences are ranked in a hierarchy. This means that, if multiple exceptions and preferences are assigned for an agent on a single day, Calendar Management analyzes the assignments and immediately selects the highest-priority exception for assignment, noting the others as declined.
However, declined exceptions and preferences are stored in the WFM database, in case there are changes to calendar information later. If, for example, a training session is canceled, an agent’s previously overridden day-off preference might then change status and be available for scheduling.