Agent State mappings allow you to define what it means for an agent to be in or out of adherence. These mappings will power the adherence metrics you see across Assembled, including in the Realtime Overview, the Agent Activity report, and the Team Performance Report.
What are Agent States?
Each contact platform has its own set of Agent States to describe what an agent can be doing at any given time. Some platforms (e.g. Zendesk and Intercom) provide a predefined set of states, while other platforms (e.g. Kustomer) allow you to customize your states.
How to map events and Agent States
To add or edit an Agent State mapping you'll go to settings > Agent States. Once there, you can map Agent States in two ways, Basic or Advanced.
Basic mappings are done based on how we categorize events and what channel they are associated with. As a refresher, productive events are those associated with a channel, whereas default and time-off events aren't associated with a channel and do not impact your staffing. Examples of these combinations you may see in the drop-down include, productive + channel (phone, chat, email) events, time-off events, and default events. You can choose multiple event type groupings for one Agent State mapping.
Advanced mappings are done by selecting the individual events that you want to be mapped to a specific Agent State.
You cannot map Agent States on both a basic level and advanced level. It is one or the other.
Productive Agent States should map to productive event types. I.e., If you're connected to Zendesk Talk, the productive states are "On call", "Online", and "Wrap up", these should be mapped to your group of productive phone events.
Tips for setting up mappings
For contact platforms that allow you to customize your Agent States (like Kustomer), try to mirror your Agent States with your Assembled event types. Your agents will more easily understand whether they're in adherence if the event types in Assembled are the same as the Agent States in your contact platform.
Some contact platforms will only be relevant for a certain set of events. For example, if you have Zendesk Chat connected as a platform, then you should only set up mappings to chat event types.