Recent searches
No recent searches
The Proactive messages feature does not work with Multi-conversations
Posted Mar 17, 2025
We are a financial company, and about 20% of our customers have two or more active conversations with us. For example, one ticket is at the 2nd support line and is still waiting to be resolved. And a customer has a new question. That's why we use Multi-conversations in Messaging SDKs (“Multi-conversations let your end users conduct multiple messaging conversations simultaneously in your Web Widget or mobile app, providing faster resolutions to their support issues and a more satisfying customer experience”).
We've been working to launch also proactive messages for our customers ("With proactive messaging, you can deliver targeted messages to your customers through your Web Widget or mobile SDK channel without waiting for them to start the conversation"). For example, if a customer's transfer is stuck because the wrong details were specified.
We found that the logic of the Multi-conversations feature contradicts the logic of the Proactive messaging feature, specifically, “for the proactive message to work, no active conversation with the bot or agent should be in place for the proactive message to work in SDK” (a reply from customer support ticket). And it was not clearly described in the documentation. After a long conversation with the Zendesk support team, we were told that instead of fixing the functionality, they would just include this limitation in the documentation ("This is not an issue or limitation but a designed behaviour. We will update our developer documentation to reflect this behaviour that it is not yet documented, multi-conversation will be treated the same when it comes to proactive messages, meaning no active conversation with the bot or agent can exists"). It seems to me that this is an attempt to pretend that this is not a bug but a feature.
We would like Zendesk to improve the Proactive messaging by providing for those customers who also use Multi-conversations the possibility to initiate a new proactive message.
6
2 comments
Shawna James
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
0
Onur Okutan
Hey Viachaslau,
Thank you for taking the time to engage with us!
The current behavior—where proactive messages are not sent if there’s already an active conversation—was intentionally designed based on customer input. The goal is to ensure a smooth and focused conversation experience for end users, avoiding situations where they receive messages from multiple conversations at the same time, which could lead to confusion or distraction while they are already engaged with an agent.
That said, we understand that in some cases, a proactive message can be an essential part of the support flow and should be delivered regardless of ongoing conversations. We appreciate you raising this perspective, and we’ll evaluate this feedback. We'll also keep this thread open to hear from others who might have similar use cases.
Thanks again for taking the time to share your feedback with us!
0