Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

DMKT
Beigetreten 10. Nov. 2022
·
Letzte Aktivität 29. März 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
42
Stimmen
13
Abonnements
24
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von DMKT
DMKT hat einen Kommentar hinterlassen
Adding my comment to further increase the visibility of this much-needed feature update. Please include agent survey feedback as I'm sure there are more users out there that would love to see this gets implemented.
Kommentar anzeigen · Gepostet 04. März 2024 · DMKT
0
Follower
1
Stimme
0
Kommentare
DMKT hat einen Kommentar hinterlassen
Would love to see more than 10 personal views available... Our users (and I imagine other Zendesk users too) that require this function usually manages a bit more than that. Maybe if we can have 40 views maximum displayed like Zendesk has currently planned, but instead of a fixed amount for each views we let the users decide how many shared views and how many personal views they want to display as long as they don't go beyond 40? That way we have more flexibility on deciding which views to utilize for different team needs.
Kommentar anzeigen · Gepostet 09. Aug. 2023 · DMKT
0
Follower
1
Stimme
0
Kommentare
DMKT hat einen Kommentar hinterlassen
Is it possible to include a customized "pre-preform" for this link to fire up when clicked? For a bit of context, we need to show customers who clicked on this link a preform within the widget to acknowledge using our services. We have this function on our websites if they contact us from there, but I'm not sure if there's a link that can do the same. (we still use phase1 chat links however we are using the latest chat accounts)
Kommentar anzeigen · Gepostet 09. Dez. 2022 · DMKT
0
Follower
0
Stimmen
0
Kommentare
DMKT hat einen Post erstellt
I absolutely understand this is common practice for all customer support SaaS systems, however it would still benefit our users if this feature could be implemented. Having multiple main receivers being addressed directly and equal ownership to the same ticket is very helpful. I suppose if the feature could be toggled on/off like CC it shouldn't impact others that don't need the complication.
Just wondering if this is more of a system limitation concern? (Need to update tickets for everyone whenever any requester respond to the ticket, creating issues for Guide datasets etc.)
Gepostet 29. Nov. 2022 · DMKT
0
Follower
3
Stimmen
2
Kommentare
DMKT hat einen Kommentar hinterlassen
More granular control over which fields are hidden for which agent groups would be quite helpful as we have a lot of different teams using different "internal fields" and hiding them separately will prevent errors being made editing fields.
Kommentar anzeigen · Gepostet 18. Nov. 2022 · DMKT
0
Follower
0
Stimmen
0
Kommentare