Recherches récentes
Pas de recherche récente

Bobby Koch
Adhésion le 03 nov. 2021
·
Dernière activité le 17 févr. 2025
Suivis
1
Abonné
1
Activité totale
332
Votes
76
Abonnements
114
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Bobby Koch
Bobby Koch a ajouté un commentaire,
need to be able to send more than 1 of these per ticket…
Afficher le commentaire · Publication le 17 févr. 2025 · Bobby Koch
0
Abonnés
1
vote
0
Commentaire
Bobby Koch a ajouté un commentaire,
Is there a way to change this from saying “Zendesk”

Afficher le commentaire · Publication le 13 févr. 2025 · Bobby Koch
0
Abonnés
0
Votes
0
Commentaire
Bobby Koch a ajouté un commentaire,
adding my two cents - not speaking for Chris.
We would like to see something like you both said, where we can either solve a ticke/mark as abanonded, or if the user leaves the session before an agent responds, deprioritize it or add it back to the queue should they go active again
Afficher le commentaire · Publication le 10 févr. 2025 · Bobby Koch
0
Abonnés
0
Votes
0
Commentaire
Bobby Koch a ajouté un commentaire,
+1
Afficher le commentaire · Publication le 04 févr. 2025 · Bobby Koch
0
Abonnés
0
Votes
0
Commentaire
Bobby Koch a ajouté un commentaire,
Liia just disable it and create a trigger. Should work, I do it that way in my sandbox account.
Afficher le commentaire · Publication le 03 févr. 2025 · Bobby Koch
0
Abonnés
0
Votes
0
Commentaire
Bobby Koch a créé une publication,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
Nested fields (i.e., Pizza Toppings - Cheese::Mozzerella, Cheese::Cheddar) are a great way to route tickets in GUIDE. In messaging, the nested front-end does not work, and instead you see the values you enter in admin. This is a horrrible customer experience.
What problem do you see this solving? (1-2 sentences)
Feature parity. This is not a “problem” this is a must have and frankly unacceptable today.
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? (3-4 sentences)
Today. There are two options:
- Create a second field for nested questions (defeats the whole purpose)
- Create separate fields for your messaging experience and your web portal experience. This causes disjointed data, and is also a bad option.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
Yes, I have to create separate fields and not use the ultra convenient nested fields.
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Just make it work. This is not a suggestion, it's basic functionality that works in one plac eand not in another.
Publication le 30 janv. 2025 · Bobby Koch
0
Abonnés
1
vote
1
Commentaire
Bobby Koch a créé une publication,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
With complex workflows, we have adopted many custom statuses now. However, the limitation can be confusing when you have many custom statuses in the same category. It's confusing for support agents and engineers to quickly use the status they should.
What problem do you see this solving? (1-2 sentences)
Faster time to resolution, similar answer to above.
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? (3-4 sentences)
Every day. There are certain workflows that are status dependent, and if someone clicks the wrong one, it can cause a ticket to be orphaned or solved slower.
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
No
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Just give a color selector/hex code field for us to set whatever color we want. If Zendesk is stuck on the colors for categories being consistent, at least give us different hueues/shades of the colors to pick from, within each status category.
Publication le 30 janv. 2025 · Bobby Koch
3
Abonnés
5
Votes
5
Commentaires
Bobby Koch a ajouté un commentaire,
what is the ETA for being able to customize this page with our design requirements?
Afficher le commentaire · Publication le 27 janv. 2025 · Bobby Koch
0
Abonnés
0
Votes
0
Commentaire
Bobby Koch a ajouté un commentaire,
when can we see this in explore? we'd like to store summaries (the last one generated) we see immense value here
Afficher le commentaire · Publication le 26 nov. 2024 · Bobby Koch
0
Abonnés
1
vote
0
Commentaire
Bobby Koch a créé une publication,
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)
Copying text from zendesk ticket should be formatted, not unformatted
What problem do you see this solving? (1-2 sentences)
clarity for the team on the receiving end of the ticket
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? (3-4 sentences)
every day, it slows down our engineers working on tickets created from customer problems
Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)
no
What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)
Just use the formatted text placeholers instead of the unformatted
Publication le 16 oct. 2024 · Bobby Koch
1
Abonné
1
vote
1
Commentaire