Schedule Adherence for agent productivity in Amazon Connect
Contact center supervisors or managers track schedule adherence to understand when agents are following the schedule that you have created. This helps ensure you achieve your service level targets, while improving agent productivity and customer satisfaction.
Amazon Connect begins generating schedule adherence automatically as soon as a published
schedule starts that has shift activities where Adherence = yes.
Adherence for a given shift activity is determined using the Default or Custom methods.
-
The Default method uses the Productive/Non-productive flag on shift activities.
An agent is considered adherent when they are scheduled for Productive activities and have the "Available" status, or when they are scheduled for Non-Productive activities and have the "Offline" status or any custom status.
For example, when an agent is scheduled for the Productive activity "Back-office work" and their status in Amazon Connect is "Offline," they are considered non-adherent to their schedule.
-
The Custom method enables you to map specific shift activities to agent statuses for determining adherence.
An agent is adherent when their current status matches any of the mapped statuses for their scheduled activity.
For example, if you map the "Back-office work" activity to both the "Back-office work" and "Offline" statuses, an agent is considered adherent when they are in either of these statuses during their scheduled "Back-office work" activity. Any unmapped agent status (such as "Available" in this example) is considered non-adherent.
For examples that show how Adherent and Non-adherent time are calculated, see Examples of Agent Adherence calculations.
You can view Schedule Adherence metrics on the Historical metrics and Real-Time metrics pages. The Schedule Adherence metrics are:
The following image shows an example of choosing Schedule Adherence metrics to appear in a historical metrics report.
Get started
-
Schedule Adherence requires that schedules are created and published. For more information, see Scheduling in Amazon Connect.
-
Ensure you have the right permissions to access metrics and scheduling information. For more information about the required permissions, see Assign permissions.
What happens when ....
-
An agent starts working before their schedule starts
If an agent does not have a schedule, we do not track adherence for that time. This means that if an agent starts working 5 minutes before or 5 minutes after their schedule, it will not count against their adherence. However, if they decide to leave work 5 minutes early because they started 5 minutes early, they would be considered non-adherent for that 5 minute interval.
-
An agent flips to offline when they are supposed to be a non-productive state
This would be considered non-adherent because the agent state is offline, rather than Non-Productive Time.
-
An agent leaves training to answer contacts because of high contact volume
In this scenario, the agent would be marked as non-adherent. However, if leaving training is intended, you can adjust the schedule retroactively and adherence will be re-calculated with the new shift.
-
A historical schedule is changed
If an agent's schedule is changed within the last 30 days from the current date (not the date of the schedule), adherence is re-calculated with the new schedule. This allows you to make real-time adjustments to an agent's shift and correctly evaluate their adherence.
