Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Lucas Moreira (Eteg)'s Avatar

Lucas Moreira (Eteg)

Beigetreten 09. März 2023

·

Letzte Aktivität 28. Juli 2024

Certified Zendesk Support Expert

Folge ich

0

Follower

0

Gesamtaktivitäten

7

Stimmen

0

Abonnements

4

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von Lucas Moreira (Eteg)

Lucas Moreira (Eteg) hat einen Kommentar hinterlassen

Community-Kommentar Português do Brasil Comunidade

Olá Pedro Rodrigues, tudo bem?

Temos alguma atualização dessa métrica? Preciso identificar no Explore os tickets que estão com o SLA ativo e o tempo restante antes da violação de SLA.

Kommentar anzeigen · Gepostet 21. Juni 2023 · Lucas Moreira (Eteg)

0

Follower

0

Stimmen

0

Kommentare


Lucas Moreira (Eteg) hat einen Kommentar hinterlassen

Community-Kommentar Q&A - Reporting and analytics

I have more details bellow: 
In this case, the ticket is created without the requester switch I mentioned earlier.


At 2022-08-16T13:41:36 we have the requester update below:

But, we dont have this update in requester last update by requester atribute:


Kommentar anzeigen · Gepostet 09. März 2023 · Lucas Moreira (Eteg)

0

Follower

0

Stimmen

0

Kommentare


Lucas Moreira (Eteg) hat einen Post erstellt

Post Q&A - Reporting and analytics

Hello there, i need some help to get a data in Explore.

I need to identify tickets where the requester didnt asnwer. Im think about create a atribute where i get the ticket requester update (timestamp) and check if is different than ticket created (timestamp), but it didint works.

I have a point in my Zendesk setup, where i change the requester after ticket creation, so when the new requester send any message, the system didnt identify this update by the new requester as a ticket requester update.

Im using messaging tickets in live chat dataset, and i made the following atribute: 

IF ([Ticket requester updated - Timestamp]!=[Ticket created - Timestamp])
THEN "1"
ELSE "0"
ENDIF

Theoretically the code should work, but since there is no record of the update of the new requester, the current value of the update remains the same as the value of the creation of the ticket.

Gepostet 09. März 2023 · Lucas Moreira (Eteg)

0

Follower

3

Stimmen

2

Kommentare