Búsquedas recientes
No hay búsquedas recientes
Agent Workspace: Add "last channel used" as default reply option
Publicado 31 may 2022
Feature Request Summary:
It would be great to have the option to set the channel to default to "last channel used" within ticket settings, so that if an end user replies to a messaging conversation by email, an agent automatically has email as the default public reply channel.
Description/Use Cases:
Agent workspace allows for easy communication with customers on multiple channels, and to easily change between channels based on a customer's preferences.
Right now, the default reply channel is "messaging" if messaging has been used in a conversation. In our business, many of these change over to "email" as the continued form of communication if further follow-up is needed.
At present, it is necessary to change the channel from "messaging" to "email" every time an email is sent, and the last channel used is not persistent each time a ticket is handled by an agent.
Business impact of limitation or missing feature:
Around 30% of our messaging conversations change to email after the initial conversation is started. Having the default be messaging every time a ticket is returned to makes it so that sometimes a message is accidentally sent when the intended channel of reply is email. (Messages are sent by hitting enter, so if the channel hasn't been changed prior to typing an email, it's easy to send a message that simply is the beginning of an email.)
We utilize continuous conversations so the customer does receive a copy of the message sent via messaging, but the end user experience is different between notification of receiving an email update to a ticket vs. notification of receiving a new message in a conversation. When email updates are sent, the prior history of the conversation is present, while with the continuous conversation notification, the prior history is not present. (We have excluded "update via messaging" from our email notifications to prevent duplicate emails to end users.)
The changing back and forth between channels rather than switching from messaging to email seamlessly can be confusing for the end user and we'd like to avoid it by changing over to email as soon as the end user changes to email.
Having the default set based on last channel used would also improve agency efficiency by reducing overall handling time of a ticket.
Adding this to the ticket settings options in the form of "default public reply channel is last channel used" that was recessed under the option to have the default reply as public reply, would improve both the agent and the end user experience.
36
19 comentarios
Oficial
Amisha Sharma
Thanks everyone for taking the time to provide us your feedback.
Apologies for the delay in responding. We are unable to deliver this feature request this year due to a few technical challenges with the implementation plan for this feature. We will however continue to monitor this post and prioritize revisiting this project shortly.
In the meantime, I'll encourage you to check the Draft Mode feature: https://support.zendesk.com/hc/en-us/community/posts/5706421005978-Draft-mode-in-composer-We-want-your-feedback-
If you have draft mode turned on, pressing "enter" will not send your message to the end user. You can compose your response without worrying about sending it by mistake. Once you are ready to send, click on "send" button and confirm sending. Hope this helps!
-3
María de la Plaza
Hi there!
This is also super frustrating for my team. Is there at least the possibility to have a shortcut for toggling between messaging and email?
0
Shawna James
-1
Stephanie Platania
Are there any updates regarding this issue? It has been quite challenging to have the reply mode switch to messaging, especially when my last response was via email. I would prefer it to remain consistent with the initial mode of communication.
0
Katrine
We would love to see this feature implemented too. Do you have any updates on this?
0
Anthony Skilton
I would love to see this feature implemented. This is particularly painful and unproductive after the move from chat to messaging. Particularly as our third-party chatbot setup doesn't allow for a continuation of the messaging channel beyond the initial conversation.
1
Sarah
I'm not sure why this isn't the default expectation. We switched over to Messaging from Zendesk Chat because we are now using the Bot. It is proving to be frustrating for our team.
1
Marta Max
is there a solution to this? where a messaging ticket is now an email ticket and to allocate it else where?
0
Oficial
Amisha Sharma
Thanks everyone for taking the time to provide us your feedback.
Apologies for the delay in responding. We are unable to deliver this feature request this year due to a few technical challenges with the implementation plan for this feature. We will however continue to monitor this post and prioritize revisiting this project shortly.
In the meantime, I'll encourage you to check the Draft Mode feature: https://support.zendesk.com/hc/en-us/community/posts/5706421005978-Draft-mode-in-composer-We-want-your-feedback-
If you have draft mode turned on, pressing "enter" will not send your message to the end user. You can compose your response without worrying about sending it by mistake. Once you are ready to send, click on "send" button and confirm sending. Hope this helps!
-3
Morgan
Or at a minimum allow us to update the ticket channel via triggers so we can create workarounds until a permanent solution is in place.
3
Daniele Lecci
Sending incomplete messages to customers because we pressed "enter" is a big no-no in customer services, also considering that the cases where a conversation will switch from email to messaging are rare.
Please prioritize this fix as sending incomplete messages to our customers is putting us and our company in a bad light and does not reflect the quality we want to deliver to our customers.
4
Iniciar sesión para dejar un comentario.