Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Florian
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 05. Aug. 2024
Folge ich
0
Follower
2
Gesamtaktivitäten
182
Stimmen
122
Abonnements
26
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Florian
Florian hat einen Kommentar hinterlassen
Makes sense! Please implement. We need that too!
Kommentar anzeigen · Gepostet 05. Aug. 2024 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Post erstellt
It seems that it is not possible to create metrics or attributes in the AI dataset that include ticket tags in the formulas.
Is there a way to add this option to the AI dataset?
It is essential for us to exclude merged tickets from the statistics, especially when we want to analyze how many tickets were solved with and without AI. If merged tickets are included with tickets without AI, the report will show inaccurate numbers.
AI dataset:
Gepostet 22. Juli 2024 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Kommentar hinterlassen
It appears that [Ticket tags]
is not supported in the AI dataset.
This is needed to create metrics or attributes like this:
IF (NOT INCLUDES_ANY([Ticket tags], "closed_by_merge")) THEN [Ticket ID] ENDIF
For example, I want to create a report that shows how many tickets used AI and how many did not, similar to the pie chart in the default dashboard. However, it is necessary to exclude merged tickets from the non-AI tickets to avoid skewing the results.
Kommentar anzeigen · Gepostet 22. Juli 2024 · Florian
0
Follower
2
Stimmen
0
Kommentare
Florian hat einen Kommentar hinterlassen
Amisha Sharma, thanks for the great news, when is this update going to be distributed?
I just checked our account, but it does not work yet.
Kommentar anzeigen · Bearbeitet 27. Feb. 2024 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Kommentar hinterlassen
Mark Leci, unfortunately, the required fields option doesn't help if something wrong is accidentally entered. In addition, Zendesk is unfortunately not that smart yet and an automatic or trigger that closes a ticket ignores the Required fields option. Of course, various tags, triggers, etc. can be used to close a ticket. However, mistakes can happen and having the option to change values afterwards makes your life much easier, especially when it comes to reporting.
Kommentar anzeigen · Gepostet 26. Jan. 2024 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Kommentar hinterlassen
Take a look at this article, as it may address what you are trying to accomplish:
https://support.zendesk.com/hc/en-us/articles/4408836523930-Printing-tickets
Thank you for the feedback. Unfortunately this is not what I'm looking for. Of course I am familiar with this simple function.
I would like to create an independent PDF document with partly static text content but also dynamic text content (based on ticket and organizational fields). The creation should be done using triggers, for example.
Kommentar anzeigen · Gepostet 10. Okt. 2023 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Post erstellt
Hi there,
does anyone have a good, easy and possibly free solution for this topic.
I would like to create a PDF form/document (e.g. a PDF template with some basic information in it) via e.g. macro or trigger and would like to add information from the ticket (ticket field content and organization field content) to this document.
Then I'd either like to download the document in order to send it to the customer or it should automatically be added to a new comment.
Is there any easy way to do that? Does anyone have experience regarding this task?
In my scenario this should something similar like a common RMA form.
Gepostet 09. Okt. 2023 · Florian
2
Follower
4
Stimmen
4
Kommentare
Florian hat einen Kommentar hinterlassen
A big plus for this feature. Would be good for us to have this too, as we still have some customers not using mail adresses trying to call us only.
Kommentar anzeigen · Gepostet 05. Okt. 2023 · Florian
0
Follower
1
Stimme
0
Kommentare
Florian hat einen Kommentar hinterlassen
I'd give this request a big thumps up.
At the moment I have a annoying workaround via trigger and webhook.
Kommentar anzeigen · Gepostet 05. Okt. 2023 · Florian
0
Follower
0
Stimmen
0
Kommentare
Florian hat einen Kommentar hinterlassen
We have the same problem and also need to ban only one specific IP address.
I think Zendesk should be able to implement something easily.
Would be great if Zendesk would stop to ignore their customers valid requests.
Kommentar anzeigen · Gepostet 24. Aug. 2023 · Florian
0
Follower
3
Stimmen
0
Kommentare