The 'Transfer to agent' step is crucial for initiating a handoff in Zendesk messaging. When this step is triggered in an automated bot, the conversation is handed off to an agent. The agents are notified of the pending support request based on the account's routing flow, and the bot can no longer respond to the conversation. The agent remains the first responder until the associated ticket is closed.
This process ensures that complex issues can be handled by a human agent, providing a more personalized support experience.
Handoff and handback are key processes in managing conversations in Zendesk messaging.Handoffis when the bot is removed as the first responder, and an agent takes over the conversation. This happens through the 'Transfer to agent' step in the…
A handback event in Zendesk messaging is triggered when the status of a ticket changes from Solved to Closed. Once this happens, the bot becomes the first responder again when a customer starts a new conversation. However, the bot does not…
Managing the timing of handback events in Zendesk can be done by adjusting the default automation or creating a trigger. By default, a Solved ticket is automatically updated to Closed after four days. You can edit this automation to change the time…
There are several additional settings to consider for optimizing handoff and handback in Zendesk. Out-of-office triggers can set customer expectations for when a live agent might engage. Continuous conversations allow email notifications to be sent…
When a message is sent outside business hours and the 'Transfer to agent' step is included in the bot flow, a ticket is created and placed in the unassigned tickets queue. A notification is also visible on the Support page, indicating a new ticket….
Yes, Zendesk can handoff a conversation to another bot solution. This is possible because Zendesk Messaging runs on the Sunshine Conversation engine, allowing integration with other bot solutions through the Smooch API. This flexibility enables…