Búsquedas recientes
No hay búsquedas recientes

Devin Chaloux
Incorporación 12 mar 2022
·
Última actividad 01 abr 2022
Seguimientos
0
Seguidores
0
Actividad total
12
Votos
6
Suscripción
1
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Devin Chaloux
Devin Chaloux hizo un comentario,
Rohan - thank you for the update on the process. If there's anything that's the most urgent for me, it's the ability to limit access to numbers by agent/group. As I mentioned, we have four numbers and really we meant to have up to 8 but considered that untenable without this feature.
Ver comentario · Publicado 22 mar 2022 · Devin Chaloux
0
Seguidores
0
Votos
0
Comentarios
Devin Chaloux hizo un comentario,
Yanko,
I agree. My use case would be that it would allow the agent to take notes so they know how to follow up the next time. By pushing this onto the agent to create a ticket, it's leaving the opportunity open for the agent to not follow through on this. Automatic creation would solve that issue. And ideally, this is a toggle that can be turned on/off.
Ver comentario · Publicado 22 mar 2022 · Devin Chaloux
0
Seguidores
1
Voto
0
Comentarios
Devin Chaloux hizo un comentario,
Agreed Ola Timpson - we have four phone numbers and used to have more on a previous telephony system because we host several different brands. The fact that we can't assign agents to a specific number is opening the possibility for error...not to mention that several teams cannot record calls and it would be bad if they called out from a number that does record calls.
Ver comentario · Publicado 15 mar 2022 · Devin Chaloux
0
Seguidores
2
Votos
0
Comentarios
Devin Chaloux hizo un comentario,
Nick Wurm - one can only hope they'll address this soon. Lacking basic functionality for outbound service is a potential deal breaker.
Ver comentario · Publicado 14 mar 2022 · Devin Chaloux
0
Seguidores
2
Votos
0
Comentarios
Devin Chaloux creó una publicación,
We recently made the switch to Zendesk Talk as it was part of the overall Enterprise package that we are part of. However, as a primarily outbound service, we are finding that Zendesk Talk lacks several important features that are standard/basic in most other telephony tools:
Limiting agent access to specific numbers (i.e. assign agents to certain phone numbers)
We have several different support numbers. Right now, we cannot limit agents to specific numbers. This is only possible for inbound calls through routing. We should be able to assign agents and/or groups to specific numbers so that they cannot call outbound from a number they are not supposed to.
At the very least, make the Talk app in the browser be "sticky" where the last number used is the one that it defaults to for that agent.
Ability to Create Tickets for Non-Answered Outbound Calls
While there is reporting on non-answered outbound calls, we would like the ability to create a ticket for these types of calls to take notes on the call.
Ability to Turn Off Inbound - Direct to Voicemail
Since we are primarily outbound, we want the ability to have people who call inbound on these numbers to be directed to voicemail by default. Right now, there is no way to do this.
Outbound IVR (Consent to Call Recording)
Right now there is no way to get a customer to consent to a call recording before talking with an agent. (See https://support.zendesk.com/hc/en-us/community/posts/4409216995738-Zendesk-Talk-Outbound-Call-Greeting?input_string=Zendesk%20Talk%20Outbound%20Features%20Needed for more).
These are just some of the basic outbound features completely lacking in Zendesk Talk and need to be addressed ASAP, especially if Zendesk wishes to compete with other telephony systems.
Publicado 12 mar 2022 · Devin Chaloux
8
Seguidores
13
Votos
14
Comentarios