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).
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 email, they will be prompted to provide email. 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 for 10 minutes, 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 Admin Center's tickets settings page.
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 through
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.
56 Comments
I like the continuous conversations feature. It should even be better if you could make the company's name clickable with a redirect to the website where the widget lives. 🚀
There has been delay in rolling out this capability to all of our customers. Ingrid and Julio, I will create tickets for you and get this enabled for your account.
- Prakruti
Hi Francis,
I will reach out to you.
- Prakruti
Hello,
I'm hoping this is the right place to ask this. My client is a lawyer and wants her ticket flow to basically works like this: chat bot collects info > creates email notifying my client of the chat along with the info collected (name, email, legal issue) > she then can respond via email directly back to the person who started the chat to their email (not within the live chat). This is because she and her team rarely have time to hop into a live chat but still see a chat option as a superior way to get people's information vs. a contact form.
As I understand continuous conversation, this should be possible.
But right now, someone starts a chat with the bot, my client receives an email notification of the chat but there's no collected information within the email and no way to respond to the person who initiated the chat without going into Zendesk.
Question on this note: "The continuous conversations feature is only available when using messaging through the web channel, and is not available on mobile devices."
I assume this means I enable messages for web SDK? When I enable this, flowbuilder is set live immediately. Is there another way to enable continious conversation trigger before end-users can see flowbuilder and start using it? Or do we just need to be quick to set this trigger or set it on a quiet moment?
Other questions:
- When will we be able to change the conversation that is now automatically set? Eg 'was this a useful answer' and whatever comes after end-user says 'no'.
Prakruti Hindia
I don't see this feature is online?
In addition, is there a way to enable opening a ticket to support using the bot, but disabling the chat using the widget and enabling only other channels?
I'd like to know when it'll become available too
Hi, maybe a note in the future would be great!
Hi Francis,
Great to hear that you wanted to test out this capability. This feature is being rolled out in a phased manner. It will be available to all accounts over the next three weeks.
Hi Ayushi,
You will need to enable Messaging for your account. You do not need to explicitly enable Answer Bot / Flow Builder for this functionality. Once Messaging is enabled, Answer Bot is enabled by default and will be the first responder to new conversations.
- Prakruti
-Hi, in the future it will be possible to change this message "Talk to a human"?
- Also sending files like photos, which is crucial for me.
Is there an estimated date for these two points?
@Prakruti I'd like to be entered in the feature right now. It's unfortunate but we've launched in early March with high expectations for this feature and it keeps being delayed. Please contact me by ticket and have this specifically deployed on my instance. I've already announced the delay for this feature 3 times now to my team, and right now again for today's deployment...
Hi Ingrid,
Yes, that's correct. It did refer to the web SDK. This feature focuses on improving the experience when your customers contact outside of business hours. With this feature, you can set expectations on response time and collect email from the customers. The customers will receive an email notification when the agents respond.
This trigger to set expectations and collect email will fire at the point of handoff to the agent. The order of execution will be Answer Bot followed this trigger.
Answer Bot / Flow Builder is good way to help customers self-serve their questions / issues , when the agents are offline.
Hi team, I still cannot find the "Continue conversations through email" option under setting, may I know if it has go live or not? Looking forward to it! Thanks.
Pakruti, You may want to check the Zendesk schedule associated with the business hours flow that is triggering. It may be associating a different schedule than what you are using for operating hours.
Camden Wiest, maybe this could help you: https://docs.smooch.io/guide/business-systems/#email. I guess that with Zendesk Sunshine Conversation, you could make an integration between your channels (like chat) and this Business System: #Email and respond them by email with all collected information.
There's no way to do that with Continuous Conversation.
Hi @...
No, sorry, I'm not referring to the web widget. I'm referring to a web page that has the Contact Us form (create new ticket form) embedded onto it. I'm aware that the widget would default to flows but the page where we have the form to submit a new ticket on it - how is that affected?
Thanks
Fiona
Hi David,
Thank you for writing in. Ability to change 'Talk to human' and enable end-users to send attachments is on the roadmap.
You will be seeing some of these capabilities in second half of this year.
Reporting for Messaging can be found in Explore. Learn more.
- Prakruti
I can't see the reports of the tickets created in with flow builder
Hi Dane
In the article, it says that enabling continuous conversations causes a chat trigger to be created.
My question, though, was what is the "duplicate message" that the article refers to?
Is it referring to the offline message shown in the screenshot where the email address is collected, along with the out of office trigger that people may have set up?
I am hoping to switch to messaging tomorrow and I would like the following to happen:
The customer follows an answer bot through the steps I set up, which end in a step where the person is transferred to an agent after collecting their email and other info. I have a business hours condition set up that will show a different message depending on if we're online or not.
scenario 1: we're online and the customer is still online so the reply is sent through the widget
scenario 2: we're online and the customer closes the web page so the reply is sent by email (presumably with a 10 min delay)
scenario 3: we're offline and the customer closes the web page so the reply is sent by email when we're back (the customer knows this already due to the message shown at the business hours step of the answer bot)
how can i make sure this happens without duplicate messaging occurring?
Thanks
Thank you @... :)
Yep, I guess so :(
I don't have any other idea that could match this.
@AMIE Zendesk uses a custom Sunshine integration for the chat widget, I'm not sure this feature is compatible with that, that would explain why
Francis, the language used for the message depends on the end-user's browser locale. The message is sent only for web and mobile messaging, not for Facebook Messenger.
Sara, the offline message is sent based on the status of your agents. It is sent only when all your agents are offline. You can manage the trigger which send the message from Chat > Settings > Triggers. The name of the trigger - Request email for continuous conversation can be found in this article.
- Prakruti
I'd like some clarification around:
"If you are using the out-of-office message trigger, you may want to disable it when using continuous conversations, to prevent sending duplicate messages to the end user."
As far as I can see in this article and the one about the OOO trigger, the customer would see a message in the widget to say the company is offline and then, when a reply is sent by the company, the customer would see the message in the widget (and then 10 mins later get an email if they hadn't seen the widget). Where is the duplicate message coming from? In the screenshot example above, it shows the OOO trigger message (under The End User Experience). Would the two things not work in tandem to cover both the company's availability and the customer's?
The notification is a system rule in place for all messages that were not read in 10 minutes. It's not associated to any triggers.
It can be disabled.
@Prakruti, please open a ticket then, because I have a screenshot of the message being sent to the Facebook Messenger channel and that is not expected
Hi Ashley,
Thank you for writing in. This feature is being rolled out in a phased manner. I will drop a note on this thread when the rollout is complete.
- Prakruti
My laptop is in French. I've tried it with both brands (one is French and the other one is English)
These are two independent entities, and they don't interact with each other in any sort of way, it would depend solely on your workflow and whether you want your end users to create tickets via the form you have implemented, or rather use the Web Widget for Messaging to offer more interactive contact with them.
Based on your needs and goals, you could create different flows to deflect the number of tickets by suggesting articles and offering a more conversational way of contacting your business, here are the available steps for the Flow Builder that can be used within Messaging widget to build a bot.
Please sign in to leave a comment.