
Tom Rees
-
Gesamtaktivitäten19
-
Letzte Aktivität
-
Mitglied seit
-
Folge ich0 Benutzer
-
Gefolgt von0 Benutzer
-
Stimmen1
-
Abonnements6
Aktivitätsübersicht
Neueste Aktivität von Tom Rees-
Tom Rees hat einen Kommentar hinterlassen
Grant Schuemann I found that for people struggling, uploading the company logo as a profile picture to their zendesk profile helped differentiate between end-user and agent messages.
-
Tom Rees hat einen Kommentar hinterlassen
Rina might be worth setting up macros to assign them to the correct teams rather than letting the agent select the group.
-
Tom Rees hat einen Kommentar hinterlassen
Does anyone know of a way to get this working for a Whatsapp ticket that is on messaging to message the customer?
-
Tom Rees hat einen Kommentar hinterlassen
We often sort views when we have a large number of tickets to check for duplicates, so this would make this task a lot more difficult.
-
Tom Rees hat einen Kommentar hinterlassen
Matt Taylor You're welcome. Took me a while to get it to work too!
-
Tom Rees hat einen Kommentar hinterlassen
Matt Taylor In the username don't put the actual token, but put the word token after the /. The password is where you paste the API token
-
Tom Rees hat einen Kommentar hinterlassen
Matt Taylor We use Okta and I have this working. The username I use is in the following format email.address@example.com/token and then I use the API to get a token and use this as the password
-
Tom Rees hat einen Kommentar hinterlassen
Hello,If a ticket is closed, I assume that deleting a group won't affect this and should still be able to be reported on? Best Wishes
-
Tom Rees hat einen Kommentar hinterlassen
Thanks Lou.It's saying '"error": "Couldn't authenticate you"' at the bottom. I've tried resetting the password and still have the same issue. I will try on my production instance when most agents h...
-
Tom Rees hat einen Kommentar hinterlassen
LouIf I test I get 'Error during transmission: HTTP client call failed', but still active without, it just doesn't run. Definitely only need the URL target and the trigger, nothing else in the back...