Búsquedas recientes
No hay búsquedas recientes

Ethan Smith
Incorporación 16 oct 2021
·
Última actividad 10 oct 2023
Seguimientos
0
Seguidores
0
Actividad total
20
Votos
4
Suscripciones
4
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Ethan Smith
Ethan Smith creó una publicación,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue
When we soon add the messaging widget to our application and to the help center, I need end users who are already authenticated in the help center to also be authenticated in the web widget in the Help Center. As it is today, a user who is already logged into their end user account in the help center is not authenticated in the messaging widget in the help center, so they can't see their past conversations or any of the other benefits of being logged in.
What problem do you see this solving?
Without this, I can't show the messaging widget to customers on the help center. Them not automatically being authenticated in the messaging widget when they are already logged into the Help Center seems like the most basic thing that needs to be supported by Zendesk. As it stands today, it would be such a horrible and confusing user experience that I am forced to not show the messaging widget on the Help Center.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
Zendesk is starting to really roll out messaging and I imagine we are getting close to being forced to move to messaging. As we've been working through the configuration and technical implementation, we realized it isn't even authenticating/recognizing users who are already logged into the Help Center.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
We just aren't going to show the messaging widget in the Help Center. We'll have it in our app, but I want it in both for a cohesive and consistent user experience, but that isn't possible.
What would be your ideal solution to this problem? How would it work or function?
It's simple. If I log into the Help Center and then launch the messaging widget there, I should be authenticated in the messaging widget.
Publicado 10 oct 2023 · Ethan Smith
37
Seguidores
37
Votos
22
Comentarios
Ethan Smith hizo un comentario,
@... hey nicole. I saw you commented on my last feedback once I posted it and just wanted to tag you here for visibility as well. this "if text is present" logic seems like it's present other places in zendesk and it would be extremely helpful to have it on conditional fields as well
Ver comentario · Publicado 21 ago 2023 · Ethan Smith
0
Seguidores
0
Votos
0
Comentarios
Ethan Smith creó una publicación,
Feature Request Summary:
I want to use a text field as a condition, but I need to be able to select "if text is present". Currently I have to enter a specific string to use as the condition, but that is too restrictive. I just need to know if there is any text in that field, and if so, I want to consider the condition met
Description/Use Cases:
We have an optional text field that, depending on if it was filled out or not, would dictate if I show a subsequent field to my agents. However, I don't care what the value of the field is, I just want to show my agents the next field if there is any text in this field, not a particular string.
Business impact of limitation or missing feature:
I can't leverage conditional fields in this situation so my view of fields for my agents is more confusing because I always have to be showing the 2nd field, even if it doesn't apply at all to them.
Editado 16 ago 2023 · Ethan Smith
0
Seguidores
2
Votos
1
Comentario
Ethan Smith hizo un comentario,
this happens to me from time to time. I just refresh the screen and the tickets generally sort themselves back out into the typical tabs so they aren't all collapsed into the "more" tab. does refreshing work for you when this happens?
Ver comentario · Publicado 01 jun 2023 · Ethan Smith
0
Seguidores
0
Votos
0
Comentarios
Ethan Smith hizo un comentario,
Alex McFarlane where are you seeing this? I still see the requester's name in the tab
Ver comentario · Publicado 07 mar 2023 · Ethan Smith
0
Seguidores
0
Votos
0
Comentarios
Ethan Smith hizo un comentario,
Maurice Asuncion I've already got a post asking for this feature, so feel free to add your feedback there. there is already a lot of support for the idea on my post
Ver comentario · Publicado 28 sept 2022 · Ethan Smith
0
Seguidores
1
Voto
0
Comentarios
Ethan Smith hizo un comentario,
@... or @...
Any update from zendesk on this? If there are no plans to revert this change (or at least give users the choice), can you please provide any bit of rationale as to how or why names are better than ticket titles? Or, if you're still trying to figure out how to address this, please just let us know that you don't have any real update at this time, but something is better than nothing at this point. The names in place of titles continue to be a hurdle more than anything for our teams working in Zendesk
Ver comentario · Publicado 16 may 2022 · Ethan Smith
0
Seguidores
10
Votos
0
Comentarios
Ethan Smith hizo un comentario,
Hi @... and @...,
can you please shed any light on potential implementation of this feature (changing back to the old format)? If it doesn't sound like this change is being prioritized right now, can you please explain what user feedback and user perspective was used when deciding that using requester names was actually better than ticket titles? If this isn't going to be changed back for the time being, I'd like to at least understand why it was changed from title to requester in the first place.
Ver comentario · Publicado 20 abr 2022 · Ethan Smith
0
Seguidores
8
Votos
0
Comentarios
Ethan Smith hizo un comentario,
Thanks Lisa Kelly for the reply. To clarify, as much as I would like this feature to be implemented, I do understand that roadmaps need to be developed and that features do need to be desired by a large number of customers (generally). I was mostly frustrated at the delayed communication here on this thread and the fact that no one on this thread was advised to open a feature request elsewhere for 12 months. Thanks for getting back to us on this thread now.
Ver comentario · Publicado 02 mar 2022 · Ethan Smith
0
Seguidores
1
Voto
0
Comentarios
Ethan Smith hizo un comentario,
I'd like to voice that I'm not very thrilled with the way this was/has been handled. Decent amount of activity on this post for the last 12 months, and we're just now being asked to log this as feedback somewhere else. Seems like that is 12 months of lost time of having any chance of this change being prioritized.
I've logged this as a feature request and would appreciate if others would go vote for this idea so that it can get some more attention from the Zendesk product team.
Ver comentario · Publicado 02 mar 2022 · Ethan Smith
0
Seguidores
4
Votos
0
Comentarios