Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Simon
Beigetreten 28. Mai 2021
·
Letzte Aktivität 27. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
8
Stimme
1
Abonnements
3
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Simon
Simon hat einen Kommentar hinterlassen
"First one was easy, I just put the code in there."
Seems to be working that way for everyone except me. No idea what I've done wrong.
Kommentar anzeigen · Gepostet 25. Juni 2019 · Simon
0
Follower
0
Stimmen
0
Kommentare
Simon hat einen Kommentar hinterlassen
@Chuck Yocum
How did you get to the first alert (the one just inside
Kommentar anzeigen · Gepostet 19. Juni 2019 · Simon
0
Follower
0
Stimmen
0
Kommentare
Simon hat einen Kommentar hinterlassen
Hi all,
I've been reading through this thread today, as it looks to do almost exactly what I wanted (I wanted to put the ticket group on the requests list page, but a custom field seemed like it would be as close as I could get).
I'm using the code below, inserted into the body, but the results are just blank. I've checked the api call using cURL and can see the custom field in there just fine. I've added in the alert texts, but it doesn't seem to do anything within the section. Can someone please help point me in the right direction?
Kommentar anzeigen · Gepostet 31. Mai 2019 · Simon
0
Follower
0
Stimmen
0
Kommentare
Simon hat einen Kommentar hinterlassen
I agree - we have a first response target of 2 hours for most tickets, but 15 minutes on urgent ones; if all agents are active within other tickets, these can be overlooked when the automations only account for an hour intervals.
Kommentar anzeigen · Gepostet 16. Nov. 2015 · Simon
0
Follower
4
Stimmen
0
Kommentare