Workforce Engagement Management

If they are scheduled for a meal and have set their presence to meal, then they are in adherence. As to why the On Queue shows as out of adherence, it is probably because of their routing status - specifically their routing status might be 'Not Responding'.

What does historical adherence view show in the exceptions view when this occurred for their routing status (Status column values with On Queue will show routing status additionally)?

If you feel the routing status for the agent is one of the acceptable values noted below in footnote 2, then I would recommend opening a support ticket so we can track and investigate further.

1. The presences **must*** be mapped to activity categories as follows:
    - Available -> Off Queue
    - Away -> Unavailable¹
    - Break -> Break
    - Busy -> Off Queue
    - Meal -> Meal
    - Meeting -> Meeting
    - Idle -> Unavailable¹
    - Offline -> Unavailable¹
    - On Queue -> On Queue²
    - Out of Office³ -> Time Off¹
    - Training -> Training

    ¹ Any presence that is mapped to either "Time Off" or "Unavailable" activity category, will be deemed as being equivalent/interchangeable.

    ² Besides being in the "On Queue" presence, the agent will also have to be in either "Idle", "Interacting", or "Communicating" routing status to be in adherence for "On Queue" activity. The last routing status for concurrent interaction scenarios dictates the agent's perceived routing status.

    ³ Out of Office is not a formal presence, rather it is a flag; however, its presentation as a selectable item along with presences in the user interface makes it seem like one. When the flag is true we ignore current presence and always map to Time Off.

    ⁴ When an agent has no scheduled activities they will be considered as having an "Unscheduled" adherence status regardless of current presence.

If they are scheduled for a meal and have set their presence to meal, then they are in adherence. As to why the On Queue shows as out of adherence, it is probably because of their routing status - specifically their routing status might be 'Not Responding'.

What does historical adherence view show in the exceptions view when this occurred for their routing status (Status column values with On Queue will show routing status additionally)?

If you feel the routing status for the agent is one of the acceptable values noted below in footnote 2, then I would recommend opening a support ticket so we can track and investigate further.

1. The presences **must*** be mapped to activity categories as follows:
    - Available -> Off Queue
    - Away -> Unavailable¹
    - Break -> Break
    - Busy -> Off Queue
    - Meal -> Meal
    - Meeting -> Meeting
    - Idle -> Unavailable¹
    - Offline -> Unavailable¹
    - On Queue -> On Queue²
    - Out of Office³ -> Time Off¹
    - Training -> Training

    ¹ Any presence that is mapped to either "Time Off" or "Unavailable" activity category, will be deemed as being equivalent/interchangeable.

    ² Besides being in the "On Queue" presence, the agent will also have to be in either "Idle", "Interacting", or "Communicating" routing status to be in adherence for "On Queue" activity. The last routing status for concurrent interaction scenarios dictates the agent's perceived routing status.

    ³ Out of Office is not a formal presence, rather it is a flag; however, its presentation as a selectable item along with presences in the user interface makes it seem like one. When the flag is true we ignore current presence and always map to Time Off.

    ⁴ When an agent has no scheduled activities they will be considered as having an "Unscheduled" adherence status regardless of current presence.

If they are scheduled for a meal and have set their presence to meal, then they are in adherence. As to why the On Queue shows as out of adherence, it is probably because of their routing status - specifically their routing status might be 'Not Responding'.

What does historical adherence view show in the exceptions view when this occurred for their routing status (Status column values with On Queue will show routing status additionally)?

If you feel the routing status for the agent is one of the acceptable values noted below in footnote 2, then I would recommend opening a support ticket so we can track and investigate further.

1. The presences **must*** be mapped to activity categories as follows:
    - Available -> Off Queue
    - Away -> Unavailable¹
    - Break -> Break
    - Busy -> Off Queue
    - Meal -> Meal
    - Meeting -> Meeting
    - Idle -> Unavailable¹
    - Offline -> Unavailable¹
    - On Queue -> On Queue²
    - Out of Office³ -> Time Off¹
    - Training -> Training

    ¹ Any presence that is mapped to either "Time Off" or "Unavailable" activity category, will be deemed as being equivalent/interchangeable.

    ² Besides being in the "On Queue" presence, the agent will also have to be in either "Idle", "Interacting", or "Communicating" routing status to be in adherence for "On Queue" activity. The last routing status for concurrent interaction scenarios dictates the agent's perceived routing status.

    ³ Out of Office is not a formal presence, rather it is a flag; however, its presentation as a selectable item along with presences in the user interface makes it seem like one. When the flag is true we ignore current presence and always map to Time Off.

    ⁴ When an agent has no scheduled activities they will be considered as having an "Unscheduled" adherence status regardless of current presence.

If they are scheduled for a meal and have set their presence to meal, then they are in adherence. As to why the On Queue shows as out of adherence, it is probably because of their routing status - specifically their routing status might be 'Not Responding'.

What does historical adherence view show in the exceptions view when this occurred for their routing status (Status column values with On Queue will show routing status additionally)?

If you feel the routing status for the agent is one of the acceptable values noted below in footnote 2, then I would recommend opening a support ticket so we can track and investigate further.

1. The presences **must*** be mapped to activity categories as follows:
    - Available -> Off Queue
    - Away -> Unavailable¹
    - Break -> Break
    - Busy -> Off Queue
    - Meal -> Meal
    - Meeting -> Meeting
    - Idle -> Unavailable¹
    - Offline -> Unavailable¹
    - On Queue -> On Queue²
    - Out of Office³ -> Time Off¹
    - Training -> Training

    ¹ Any presence that is mapped to either "Time Off" or "Unavailable" activity category, will be deemed as being equivalent/interchangeable.

    ² Besides being in the "On Queue" presence, the agent will also have to be in either "Idle", "Interacting", or "Communicating" routing status to be in adherence for "On Queue" activity. The last routing status for concurrent interaction scenarios dictates the agent's perceived routing status.

    ³ Out of Office is not a formal presence, rather it is a flag; however, its presentation as a selectable item along with presences in the user interface makes it seem like one. When the flag is true we ignore current presence and always map to Time Off.

    ⁴ When an agent has no scheduled activities they will be considered as having an "Unscheduled" adherence status regardless of current presence.

Do you have 'Activity Equivalency' enabled (Configuration | Management Unit | Adherence)? Having that enabled basically means we only look at On Queue scheduled activities and what the agent is doing and for every other scheduled activity we treat as being adherent. More information at bottom of reply.

Are Breaks and Meals configured as 'Ignore for Adherence' (Configuration | Management Unit | Adherence)? If they are then we ignore for all adherence determination.

https://help.mypurecloud.com/articles/configure-historical-adherence/:

1. To consider non-On Queue activities equivalent for adherence calculations, toggle the Activity Equivalency switch to Yes. To ensure that non-On Queue activities are not considered equivalent for adherence calculations, toggle this switch to No.
   Example: If you set activity equivalency to Yes, then an agent scheduled for Break whose actual presence is Meal is considered in adherence. If you set this option to No, then the agent is considered out of adherence.

If they are scheduled for a meal and have set their presence to meal, then they are in adherence. As to why the On Queue shows as out of adherence, it is probably because of their routing status - specifically their routing status might be 'Not Responding'.

What does historical adherence view show in the exceptions view when this occurred for their routing status (Status column values with On Queue will show routing status additionally)?

If you feel the routing status for the agent is one of the acceptable values noted below in footnote 2, then I would recommend opening a support ticket so we can track and investigate further.

1. The presences **must*** be mapped to activity categories as follows:
    - Available -> Off Queue
    - Away -> Unavailable¹
    - Break -> Break
    - Busy -> Off Queue
    - Meal -> Meal
    - Meeting -> Meeting
    - Idle -> Unavailable¹
    - Offline -> Unavailable¹
    - On Queue -> On Queue²
    - Out of Office³ -> Time Off¹
    - Training -> Training

    ¹ Any presence that is mapped to either "Time Off" or "Unavailable" activity category, will be deemed as being equivalent/interchangeable.

    ² Besides being in the "On Queue" presence, the agent will also have to be in either "Idle", "Interacting", or "Communicating" routing status to be in adherence for "On Queue" activity. The last routing status for concurrent interaction scenarios dictates the agent's perceived routing status.

    ³ Out of Office is not a formal presence, rather it is a flag; however, its presentation as a selectable item along with presences in the user interface makes it seem like one. When the flag is true we ignore current presence and always map to Time Off.

    ⁴ When an agent has no scheduled activities they will be considered as having an "Unscheduled" adherence status regardless of current presence.