Overview

When running a high performing support organization, it's important to measure agents and teams against the right and accurate metrics. Furthermore, especially if live channels constitutes one of your primary support channels, it's important to ensure that the teams are following their schedules in order to ensure that you hit your SLA and offer your customers the best experience possible. 

To that end, Assembled supports automatic and manual overriding statuse for agents in Zendesk and uses that data to surface insights about agents and teams in the Team performance, Agent scorecard, Realtime and other reports.

In this article we'll go over : 

• How it works
• Setting it up
• Advanced configuration

  • Manually override statuses (a.k.a. aux codes)

  • Track work outside of Zendesk against ticket work

• FAQ

How it works

Once set up, Assembled automatically tracks what agents are working on in Zendesk and uses this information to display the status, derived metrics and whether or not the agent is adhering to their schedule in various reports.

Realtime

In the Realtime dashboard the status will appear for each agent on Zendesk and whether or not that status is in adherence with their schedule.

Team performance

In the Team performance report you will have access to new metrics:

• Adherence
• Hours in adherence
• Cases solved per actual hour
• Actual hours worked
• Utilization
• Total hours worked

Furthermore, if you have manual overriding enabled, you will also have access to the following metrics:

• Non-productive hours worked
• Conformance

Agent scorecard

When inspecting individual agents in the Agent scorecard, the user's state will show up in the timeline and also be used to compute adherence metrics over time.

Setting it up

Initial configuration

To start tracking agent statuses in Zendesk, follow these steps:

1. Ask your agents to install the Assembled Zendesk application from the Zendesk marketplace
2. In the Assembled application, under Settings > Integrations > Assembled App for Zendesk select I'VE COMPLETED THE INSTALLATION OF THE APP and USE THE APP FOR ACCURATE ADHERENCE CALCULATIONS.
3. Configure the Zendesk states to map to the proper schedule events (more here)

Once you've selected USE THE APP FOR ACCURATE ADHERENCE CALCULATIONS you will see more granular agent states in Settings > Agent states. Here is a list of those statuses and their descriptions:

• Online (Tickets) - the agent’s primary tab (in a visible window) is on a Zendesk ticket page.
• Online (Zendesk Dashboard) - the agent’s primary tab (in a visible window) is in Zendesk but not on a ticket page.
• Online (not Zendesk) - the agent’s primary tab is not on Zendesk at all, but the Zendesk tab is still present in the background.
• Offline - Zendesk is not open.

Advanced configuration

You have additional, advanced configuration options at your disposal by contacting your Customer Success Manager or support@assembledhq.com.

Manually override statuses (a.k.a. aux codes)

If you would like agents to explicitly select an event to override task tracking, this feature provides the agents with a list of the available Events configured in Assembled for them to pick from. If no event is selected, Assembled uses the Zendesk status, but if the agent selects an event to override, Assembled will use that until the agent ends the event override.

Note: agents will stay in the manual state until they manually stop event override 

If agents manually override task tracking, certain additional metrics listed above will be available in Assembled (eg. Conformance).

In Assembled, there will be an additional row called Manual Tracking in agents' Agent scorecard reports that will reflect these manual changes. 

Set up: 

• Reach out to support@assembledhq.com to enable this feature on your instance.
• Configure which events are made available to agents to select from in the dropdown from Settings > Event types.
  • Select the event that you want to display or hide in the dropdown, select Edit, and then select the option you want under Zendesk time tracking.

• • This option is also available when creating new events, and by default new events will only show in the dropdown if they're default (a.k.a. non-productive events like Lunch) and will not show up for time off or productive events.
• All events that you have selected for manual time tracking will show up as a new agent state in Settings > Agent states. To ensure that adherence is properly accounted (or not accounted) for, make sure to map these new agent states to Assembled events. 

Track work outside of Zendesk against ticket work

Automatically track Zendesk ticket work even when the agent is not in Zendesk. When this option is enabled, if agents navigate to different browsers tabs to complete tickets (eg. they need to access an internal tool or dashboard), that time continues to be tracked as work time for that ticket.

For example, if the agent opens a new ticket that is assigned to them for 30 seconds to read the message, opens another tab to do work for that ticket (eg. internal tool, dashboard) for 5 minutes, then goes back to that tickets for 30 seconds to respond, Assembled will track that as a total of 6 minutes worked on that specific ticket, rather than just the 1 minute when the agent is actually on the tab with that ticket. 

In this scenario, agents can be in any of the following states:

• Online (Tickets)
• Online (Zendesk Dashboard)
• Offline
• The manually selected aux code

Time for that ticket will start counting from the first time the agent views an open ticket, until one of the following action happens:

• The agent logs out of Zendesk or Assembled
• The agent select a manual state if this option is available
• The agent closes the last open ticket they viewed

Generally speaking this option provides a more accurate view of time agents spend on tickets if agents have to do a lot of work outside of Zendesk to resolve issues. However, using this configuration option generally means that mores hours of worked will be tracked by agent, which in turn affects certain metrics such as, but not exclusively: Adherence (Agent scorecard and Team performance) and Actual hours worked and Cases solved (per actual hour) (Team performance). As a general rule of thumb, we recommend mapping Online (Tickets) to a productive state and Online (Zendesk Dashboard) to a default state when you have this configuration set up. Without this, the agent will be in adherence anytime they're logged in to Zendesk during scheduled work hours unless they've manually selected an aux code. You can find more information on the metrics in Assembled which are impacted by time tracking in the List of Metrics and Definitions. If you wish to change which agent states count towards productive time, please visit the Configuring Agent State Mapping page.

FAQ

• Agents are showing up as Offline in Assembled but are actively logged into Zendesk. What should I do ? 
  • Have the agent open the Assembled app in Zendesk --> are there any errors ? If so reach out to support@assembledhq.com.
  • Hard refresh their Zendesk page. Still not working ? Reach out to support@assembledhq.com.
• Agents are showing up as Logged in in Assembled but have USE THE APP FOR ACCURATE ADHERENCE CALCULATIONSenabled. What should I do ? 
  • Have these agents ever logged into Assembled ? If no, have them login for the first time as this should link their Zendesk account to Assembled. If yes, have them login and logout of Assembled. Still having issues ? Reach out to support@assembledhq.com.