Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

dschmidt
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 06. Dez. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
62
Stimmen
31
Abonnements
23
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von dschmidt
dschmidt hat einen Kommentar hinterlassen
Unfortunately we are on Professional; multiple schedules would probably work if we were on an Enterprise plan. It would be nice if that was an a la carte add-on.
Kommentar anzeigen · Gepostet 24. Aug. 2023 · dschmidt
0
Follower
0
Stimmen
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
This is a challenge for us as well. Our approach is for admins to manually add and remove agents from the groups that correspond to the different numbers depending on coverage requirements. One issue with this is that when you remove an agent from a group, they lose ownership of any non-closed tickets they may have in that group, which can affect metrics.
Kommentar anzeigen · Gepostet 24. Aug. 2023 · dschmidt
0
Follower
0
Stimmen
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
This warm transfer functionality is highly desired by our teams too.
Kommentar anzeigen · Gepostet 17. Nov. 2022 · dschmidt
0
Follower
0
Stimmen
0
Kommentare
dschmidt hat einen Post erstellt
When personalized replies are enabled (Enabling personalized email replies – Zendesk help), the setting applies to both end users and agents. Including the support address name after the end user name in the From: line on email notifications can falsely imply that the end user is a member of the support team associated with that support address.
I would like the option for this setting to apply only for agents, so email notifications triggered by end users do not include the support address name. Alternatively, the appended support address name for email notifications triggered by end users should include "reply via" or another customizable string.
For example:
From: Agent Name (Support Address Name)
vs
From: End User Name
alternatively:
From: Agent Name (Support Address Name)
vs
From: End User Name (reply via Support Address Name)
Gepostet 23. Aug. 2022 · dschmidt
0
Follower
1
Stimme
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
Has anyone else seen an issue recently with the Assignment Control app where it activates immediately upon viewing a ticket, instead of only when the assignee drop-drown selection box is opened?
The result is that when viewing a ticket that is already assigned to a hidden group (by trigger, macro, etc), the assignee field is changed to blank ("-"), and the ticket cannot be updated without reassigning it to a non-hidden group.
This is happening for me in both Chrome and Edge.
Kommentar anzeigen · Gepostet 11. Juli 2022 · dschmidt
0
Follower
0
Stimmen
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
Agreed. It should be possible to limit playback of call recordings to Admins and Team Leads. It is bad enough that full Agents can listen to each other's recorded calls, but it especially complicates the rollout of Light Agents.
Kommentar anzeigen · Gepostet 26. Mai 2022 · dschmidt
0
Follower
6
Stimmen
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
I agree. It should be possible to enable automatic recording of inbound calls without requiring manual customer opt-in, while automatic recording of outbound calls remains disabled.
Kommentar anzeigen · Gepostet 26. Mai 2022 · dschmidt
0
Follower
0
Stimmen
0
Kommentare
dschmidt hat einen Kommentar hinterlassen
I suggest you add app.pendo.io to this list. I had problems with transfers / conferencing until I added that to my exceptions.
Kommentar anzeigen · Gepostet 29. Apr. 2022 · dschmidt
0
Follower
1
Stimme
0
Kommentare