Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Nils Odlund
Beigetreten 22. Apr. 2022
·
Letzte Aktivität 21. Juli 2022
Folge ich
0
Follower
1
Gesamtaktivitäten
9
Stimme
1
Abonnements
3
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Nils Odlund
Nils Odlund hat einen Kommentar hinterlassen
My apologies. It appears that I misunderstood the error report from the agent. After highlighting the button, it's still required to press Ctrl+C to copy the number. Apparently, for a while it did not work, but then the functionality returned.
Kommentar anzeigen · Gepostet 21. Juli 2022 · Nils Odlund
0
Follower
0
Stimmen
0
Kommentare
Nils Odlund hat einen Kommentar hinterlassen
We've experienced the same issue. Is there any info we can provide that might be helpful?
EDIT: I was able to resolve the issue by changing the order of the links in the macro.
Kommentar anzeigen · Bearbeitet 27. Apr. 2022 · Nils Odlund
0
Follower
0
Stimmen
0
Kommentare
Nils Odlund hat einen Post erstellt
Feature Request Summary:
There should be a way for Views to exclude/include Closed tickets based on whether a Follow-Up ticket has been created or not.
Description/Use Case:
In the past, when a customer contacted us to ask if we could restore their farm (this is for a computer game) our answer was "no - we cannot restore your farm."
Recently, circumstances changed, and our answer to their question became "yes - we will be happy to restore your farm."
We now want to contact all of the customers that previously received "no" as an answer and let them know that we're able to help.
To do this, we have created a View that shows all past tickets where a customer asked for their farm restored. This view includes roughly 250 Closed tickets.
Our agents are going through the tickets in this view, one by one, and contacting all of the customers that received "no" to let them know we're now able to say "yes" (as well as performing the actual restoration of the farm).
Unfortunately, our agents have no way of knowing whether a customer's case has been handled or not, without opening up the Closed ticket and checking manually for each case whether a new ticket has been created by us and the farm restored.
If we could filter the View to not included Closed tickets that have had Follow-up tickets created, this would speed up the process significantly, as our agents wouldn't have to manually click through tickets until they find one that's not been processed.
Business impact of limitation or missing feature:
Significant.
Gepostet 27. Apr. 2022 · Nils Odlund
1
Follower
3
Stimmen
0
Kommentare
Nils Odlund hat einen Kommentar hinterlassen
This appears to have been a temporary issue, and it's now working again. :)
Kommentar anzeigen · Gepostet 25. Apr. 2022 · Nils Odlund
0
Follower
0
Stimmen
0
Kommentare
Nils Odlund hat einen Post erstellt
Feature Request Summary:
Allow users to click the Ticket ID tab (button) to copy the ticket number.
Description/Use Cases:
At the top of each ticket there are three buttons (Organization, user (email), and Ticket ID), and up until just recently it was possible to click the Ticket ID button to copy the ticket ID to the clipboard. This is no longer possible, and some of our agents are annoyed that a convenient feature they were used to has been removed.
This button:
Business impact of limitation or missing feature:
The removal of this feature is an inconvenience to agents who used it as part of their regular workflow (but it's not critical to our business as a whole).
Other necessary information or resources:
Gepostet 22. Apr. 2022 · Nils Odlund
7
Follower
10
Stimmen
9
Kommentare