Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Nathan Purcell
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 10. Juli 2023
Folge ich
0
Follower
0
Gesamtaktivitäten
143
Stimmen
65
Abonnements
0
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Nathan Purcell
Nathan Purcell hat einen Kommentar hinterlassen
I'm 100% with Jordan Moore here.
My organisation comprises dozens of brands with hundreds of agents in teams around the world. Our agents are cross-trained so the number of queues is a multiple of the different brands AND services therein.
Zendesk shouldn't try to dictate how we use the system; they should be listening to feedback and adapting. If we choose to do so in a "non-optimal" way then that's for us to decide.
Kommentar anzeigen · Gepostet 10. Juli 2023 · Nathan Purcell
0
Follower
2
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
To echo Hamish, can more details be added on the limitations in the manifest file?
Receiving an unhelpful message that reads "The property '#/settings/0/variables/X' of type object did not match any of the required schemas" doesn't give us much to go on.
The limit will be known to you, so adding docs should take a couple of minutes, not months.
Edit to add, the length of descriptions, labels etc. is not flagged by ZAT, so I hope you can understand the frustration that a limit is only being imposed at the last step.
Kommentar anzeigen · Bearbeitet 23. März 2023 · Nathan Purcell
0
Follower
2
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
Welcome to Zendesk Cat, where the documentation is either missing, just plain wrong or there's some unusual edge case that affects 99% of the users 🤷 🙄
Kommentar anzeigen · Gepostet 16. März 2023 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
Why can we not inject dependencies to the document_head (or the out-of-reach area of the head)?
It makes adding custom styling and working with frameworks (Bootstrap, Tailwind, Foundation) incredibly difficult and leads to a massive over use of !important declarations.
Kommentar anzeigen · Gepostet 01. März 2023 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
The group to which the ticket is assigned. The "assignee" option in the left hand column.
Kommentar anzeigen · Gepostet 17. Feb. 2023 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
Nice!
Got to say though, "Automatically use the correct email sender, depending on the agent's user group" is close, but no cigar.
If you can work it based on the ticket's group then you win.
Kommentar anzeigen · Gepostet 17. Feb. 2023 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
Colleen, that CSS isn't targeting those divs as they don't have the class "block-list-item".
In your CSS, replace ".block-list-item" with ".custom-block" and it should work.
Kommentar anzeigen · Gepostet 18. Jan. 2023 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare
Nathan Purcell hat einen Kommentar hinterlassen
Salvador Vazquez can we have an update please?
Kommentar anzeigen · Gepostet 18. Jan. 2023 · Nathan Purcell
0
Follower
1
Stimme
0
Kommentare
Nathan Purcell hat einen Post erstellt
As per the title, why does the Zendesk API not offer side loading on each entity that has a FK attribute?
Working example that I noticed today: CSAT ratings.
CSAT ratings have FKs for assignee, group, requester and ticket but there is no side loading available.
Why?
This is only one example. I have personally found more, I am quite sure there are lots of others. Why not just offer side loading for everything with a relationship?
Bearbeitet 15. Nov. 2022 · Nathan Purcell
1
Follower
1
Stimme
1
Kommentar
Nathan Purcell hat einen Kommentar hinterlassen
Is there a cost to that Fredys? The only pricing I could find appeared to be for the Helpdesk product.
It's a pretty poor testament to Zendesk that such a simple request was overlooked in the first place, it's taken over a year to get to this point (which is of course, no movement), and that the next best option is what looks like a very costly third-party app.
Even a free third-party app inevitably means workarounds and unpicking said workaround when Zendesk finally come up with a solution (if one comes at all).
Kommentar anzeigen · Gepostet 07. Nov. 2022 · Nathan Purcell
0
Follower
0
Stimmen
0
Kommentare