The continuous conversations feature allows you to automatically send an email notification to customers who abandon a conversation conducted through a Web Widget, encouraging them to re-engage with your agents through their preferred channel.
This article includes the following topics:
About continuous conversations
The continuous conversations feature allows both end users and agents to leave (but not end) a messaging conversation at any time and pick it up where they left off, without the end user losing track of the conversation.
End users may choose to leave a conversation when the expected wait time is high, when your business is offline or there is a long queue, for example.
With continuous conversations activated, an email is sent to the end user informing them when an agent has left them a message in the conversation (see The end user experience). The continuous conversation email template is localized and translated based on the user's profile language in Support. See How does Zendesk set a language for a user in Support?
To use continuous conversations, you must have an account with
- Zendesk Suite OR Support + Chat (Team plan or higher).
- Messaging activated
- Agent Workspace activated. See Activating and deactivating the Zendesk Agent Workspace.
- At least one agent with Chat access. See About Staff roles in Zendesk Admin Center.
- Has set up a support email address
The end user experience
With continuous conversations activated, an end user who leaves an ongoing conversation from a website receives an email when an agent responds, allowing them to easily find and continue the conversation when they're ready. The end user can continue the conversation by responding to the email, or return to the website.
The example below describes the default experience when you activate continuous conversations. Here, an end user starts a conversation with a company that is currently offline. If the end user has provided an email, they will receive an acknowledgement informing them that email will be sent when the agent responds. If the end user has not previously provided an email, they will be prompted to provide one. Note that end user email addresses cannot contain accented characters.
Later, an agent responds to the original conversation request. If the message from the agent remains unread until the conversation is considered inactive, an email is sent to the end user with the unread agent’s response.
The end user can choose to continue the conversation by responding to the email, or return to the website to do so.
The agent experience
For agents, the entire conversation takes place in the Zendesk Agent Workspace. Continuing with the example above, when an agent returns to work, they are notified that a conversation is waiting for them in their queue, and they can respond to the conversation as usual.
If the agent leaves a message for the end user in the conversation, and the message remains unread by the end user, an email is automatically triggered. When the end user responds, their response is included in the conversation, indicating whether it was sent via email or messaging:
Working with other triggers
If you are using the out-of-office message trigger, you may want to deactivate it when using continuous conversations to prevent sending duplicate messages to the end user.
Activating continuous conversations
You can activate continuous conversations on the Ticket Settings page in Admin Center.
To activate continuous conversations
- In Admin Center, click
Objects and rules in the sidebar, then select Tickets > Settings.
- Under the Settings tab, select Switch messaging conversations to email.
This creates the following active trigger, which you can find on the Messaging triggers admin page:
Deactivating continuous conversations
If you choose to stop using continuous conversations, you’ll need to deactivate both the tickets setting and the trigger created when you activated the feature.
To deactivate continuous conversations
- In Admin Center, click
Objects and rules in the sidebar, then select Tickets > Settings.
- Under the Settings tab, deselect Switch messaging conversations through email, then click Save tab at the bottom of the page.
- In Admin Center , click
Objects and rules in the sidebar, then select Business rules > Messaging triggers and open the trigger Request email for continuous conversation.
Note: In some Zendesk accounts, this trigger is located in the Chat dashboard. Go to Chat > Settings > Triggers. - Deselect Activate this trigger, then click Save.
64 comments
Joyce
You may consider activating the continuous conversations feature for your use case. When activated, this will create a messaging trigger named Request email for continuous conversations, which can be accessed in the Chat Dashboard. This trigger prompts end users for an email address when they start a chat while your agents are offline/invisible, in order to continue messaging conversations through email.
Or you can simply create a messaging trigger in the Chat dashboard with the same conditions as the above image. The trigger in the Chat dashboard has a "Channel" option which will allow you to build a trigger for Chat, Messaging or both:
0
Moaz Magdy
In messaging, when an end user requests to speak to a human and no one is available, where could we adjust the bot message that is sent? We are currently using Messaging triggers to request email for continuous conversations. It sends out an irrelevant message in a language different from the one set up in the bot settings.
Could you guide me on where I can adjust this message? I looked into all messaging and chat settings and could not find anything I could use to edit this message.
Also, any message the end-user sends after that is added to the existing chat ticket. The ideal case would be that since no one if available to reply to them, they get back to interacting with the bot and they receive an update via email when their ticket is replied to.
2
Gintare Remeikė
I would second Moaz's request for the ability to adapt the message sent and change the language, as using the browser locale does not work for our users in most cases.
1
Ariya Sacca Utama
Can we use this for social media channel?
0