Amie Brennan
Solutions consultant for SuccessCX - Australia's #1 Zendesk Master Partner
-
Gesamtaktivitäten504
-
Letzte Aktivität
-
Mitglied seit
-
Folge ich0 Benutzer
-
Gefolgt von0 Benutzer
-
Stimmen22
-
Abonnements242
Kommentare
Neueste Aktivität von Amie Brennan-
Hey Jesse Spalding, In general, when you make an update to a ticket field, you do then need to submit the ticket so it saves the changes you've made. Submitting the ticket normally requires the age...
-
Hi Paul Von, This very pretty disappointing to hear! The biggest outcry on the community right now and from many other customers is the lack of ability to reverse the comments since the new agent w...
-
Hi Viktor Osetrov, Some feedback - This is a half-baked release. Adding limits to products is ok, as customers we get that there has to be a line drawn somewhere. What is lacking here with this rel...
-
Hey Gorka Cardona-Lauridsen Do you have an update on when this will be released? Your latest indication was H2 2022 which has been and gone now. It would be really appreciative if you could provid...
-
Hey Zach Anthony, FYI There's no mention of the new API Key authentication listed as an auth method in the Creating webhooks guide. Might need to arrange for it to be updated. :)
-
This is amazing! Such a time saver. I only hope Zendesk build in a few more long awaited gems like this. :)
-
Hey Sam Graves, Unfortunately, there is no way to display the date in full on a ticket like you're looking for in the instance when it's less than 7 days old. This is currently by design and there'...
-
Hey Chuck Fitzpatrick First, you need to have the ticket form ready inside your Zendesk which customers will use to submit via. Second, you'll need to look at utilising the Zendesk mobile SDK to a...
-
Great idea, however, this prob won't ever happen because the "emails" which show up in the suspended tickets view are technically not even tickets yet. They have no ticket ID associated with them a...
-
Hey Joshua Nelson, Without being able to see your trigger configuration directly, to me this sounds like there is a trigger issue happening here. You could have a condition in your inbound routing...