This topic describes how Zendesk administrators work with the Zendesk Agent Workspace.
Other than enabling or disabling the workspace and mapping Chat departments to Support groups, there are no special Chat, Talk, or Support settings required to administer the agent workspace. For example, business rules for routing, triggers, automations, and macros that you set in Support are enforced; Chat agents receive incoming chat requests based on the settings you selected for chat routing; and, if all Talk agents are away, incoming calls continue to be queued and the values you have set for maximum queue size and maximum queue wait time are in effect.
For Social Messaging, there are special configuration tasks for the Zendesk Agent Workspace that differ from configuration tasks for Support. See Social messaging tasks for administrators for details.
Support tasks for administrators
To use the agent workspace, make sure Support is set up on your account. This includes:
- Add email addresses.
Use the Email administration page to add any additional email address you want to use on your site, set email preferences, or customize your email templates. For more information, see Getting started with email.
- Add Support agents.
Use the People administration page to add and manage Zendesk users, groups, and organizations. Each new agent you add receives a welcome email and verification link. For more information, see Adding agents and administrators.
Chat tasks for administrators
To use Chat in the agent workspace, make sure Chat is set up on your account. This includes:
- Set up the Web Widget.
Set up and embed the Web Widget. To use Zendesk Chat with the Web Widget, enable Chat on the Web Widget and configure Chat settings. For more information, see Configuring components in the Web Widget and Setting up Chat in the Web Widget.
- Add Chat agents.
Make sure Chat is enabled for agents who serve chats. See Setting roles and access in Zendesk Admin Center. Also, make sure your agents are upgraded for both Chat and Support. The agent workspace does not support agents with Chat only or Contributor roles.
- Set up operating hours.
Set up chat operating hours for your agents. See Creating a schedule with operating hours (Professional and Enterprise).
- Enable Chat ratings (optional).
Set up Chat ratings for your account. To allow visitors to rate their chats with your agents, open the Chat dashboard and select Enable satisfaction ratings from Widget > Settings. See Enabling and viewing Chat ratings.
- Enable Chat departments.
Make sure any Chat department with agents that need to send or receive transfers is enabled on the Chat dashboard. To enable a Chat department, open the Chat dashboard and select Settings > Departments to edit the department.
- Enable authenticated visitors (optional).
Talk tasks for administrators
To use Talk in the agent workspace, make sure Talk is set up on your account. This includes:
- Select a phone number.
To use Talk, you'll need to purchase a phone number from Zendesk. You can purchase this number from directly within Talk. For more information, see Adding Zendesk Talk numbers.
- Enable Talk on the Web Widget.
To use Zendesk Talk with the Web Widget, create a configuration that defines how to handle Talk requests that originate from the Web Widget. For more information, see Configuring Zendesk Talk settings for the Web Widget.
- Manage Talk settings.
Once your number is set up, you can configure or change Talk settings. For details about all of the things you can do with Talk, see Zendesk Talk resources.
- Add Talk agents.
Make sure Talk is enabled for agents who take calls. See Controlling access to Zendesk Talk.
Mapping Chat departments to Support groups
For Chat transfers to work properly, make sure the Chat departments in your account are mapped to Support groups. Use the Agent Workspace migration wizard to automatically do the mapping when you first enable the agent workspace. For more information, see Migrating to the Zendesk Agent Workspace. Also make sure any Chat department that needs to send or receive chat transfers is enabled on the Chat dashboard. You can enable Chat departments before or after migration.
Social messaging tasks for administrators
To configure support for social messaging in the Zendesk Agent Workspace, do the following:
- Verify you have a Zendesk Support Suite account or an account with the Social messaging add-on.
- Migrate your account to the Zendesk Agent Workspace and enable the workspace.
- Add one or more social messaging channels to the Zendesk Agent Workspace.
Unlike social messaging channel setup for a standard Support account, social messaging channel setup for the Zendesk Agent Workspace is done through Admin Center.
- Enable Chat for each agent that will participate in social messaging conversations and assign the agent a Chat role. See Setting roles and access in Admin Center.
- To work with social messaging conversations, agents only need a paid seat for Support and a Chat Agent (limited) role. The Chat Agent (limited) role allows agents to serve social messaging conversations without requiring a paid Chat seat.
- To use the Agent (limited) role, assign the Agent (limited) role to one of your Chat agents, then you can assign this new role to any agent with a Support only role.
- Organize your agents into groups. For example, you can create a group of agents who handle specific channels, such as WhatsApp, or you can create a group of agents who handle all types of social messaging tickets. See Adding agents to groups.
Agents with new Agent (limited) role will be treated as Chat agents and will start getting both the chat and social messaging conversations.
If broadcast routing mode is enabled in Chat, you can avoid routing Chats to social messaging agents by creating a new group (department) for agents who only serve chats and create a trigger that assigns chats to this new group.
- Use Support triggers to assign social messaging tickets to groups (optional).
This is useful when you have agents dedicated to handle social messaging channels. For more information, see Setting triggers, automations, and views for social messaging.
- Set up Chat routing to control how social messaging tickets are routed to your agents.
Routing for Social messaging is based on the Chat routing rules defined for your agents. This includes:
- Social messaging tickets created when agents are online are routed via the Accept button in the ticket interface.
- Social messaging tickets created when agents are offline are sent to the Unassigned tickets view or the agent’s Group view.
- Offline social messaging tickets can be assigned to agents as part of triaging or they can be manually picked up by agents themselves.
- Configure Chat limits settings on the Chat dashboard to control how many active social messaging tickets and live Chat tickets your agents receive. Also, configure Chat operating hours to manage your social messaging business hours.
A social messaging ticket is Active if the ticket conversation has been updated in the last 10 minutes.
In addition to these steps, administrators can use Chat file sending options to manage what types of attachments agents can send. Some of these file types (for example, .mov) are not enabled by default.
Setting triggers, automations, and views for social messaging
To help you route social messaging conversations to the correct group of agents, you can use the Channel conditions in Support triggers and automations to set up the routing. For example, when you create a trigger or automation, add a Channel is condition, then choose the social messaging channel you want to include. You can pick a specific social messaging channel type, or add multiple channels. See example below.
Trigger name, description, and conditions
If there are multiple accounts defined for the same channel type (for example, WhatsApp), tickets can be routed by only by channel type, not by a specific integration account.
You can also use Channel conditions to create social messaging views for agents to share. You can pick a specific social messaging channel, or add multiple channels. See example below. For more information on creating views, see Creating views to manage ticket workflows.
About the agent experience
When the Zendesk Agent Workspace is enabled on your account, the change applies to all your agents. Here's what your agents will see:
- Agents with Support, Chat, and Talk enabled will see a fully-unified conversation experience. They have access to all existing Support features, but they can also use Chat, and Talk controls directly from the Support ticket interface. For more information, see About the Zendesk Agent Workspace.
- Agents with Support and Chat enabled will see a fully-unified conversation experience, but without the Talk controls. They have access to all existing Support features, and they can also use Chat controls directly from the Support ticket interface. Chats are served from the agent workspace, instead of the Chat dashboard.
- Agents with only Support enabled will see a standard ticket interface - with two exceptions. For ticket comments, the most-recent replies appear at the bottom of the conversation, instead of the top. This change is necessary to keep conversation flows consistent across chats and emails. Also, the customer context information appears on the right side of the ticket interface, instead of the left.
- The workspace does not support agents with Chat only or Contributor roles. You need to upgrade these agents for both Support and Chat. Light agents cannot serve chats in the agent workspace. They need to be upgraded to agents.
- Markdown formatting is not supported in conversations. It has been deprecated in the Zendesk Agent workspace. Instead, agents can use the rich text features available in the Composer window to format messages.
- If you set up Social Messaging for the agent workspace, agents with Support and Chat enabled will be able to receive and send social messages directly from the conversation interface. (See Receiving and sending social messages in the Zendesk Agent Workspace.) Support agents can serve social messaging conversations if they have a Support Agent role and a Chat Agent (limited) role (or a full Chat agent role).