최근 검색
최근 검색 없음

Nathan Purcell
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2023년 7월 10일
팔로잉
0
팔로워
0
총 활동 수
143
투표 수
65
플랜 수
0
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Nathan Purcell
Nathan Purcell님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 7월 10일에 게시됨 · Nathan Purcell
0
팔로워
2
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 3월 23일에 편집됨 · Nathan Purcell
0
팔로워
2
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
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 🤷 🙄
댓글 보기 · 2023년 3월 16일에 게시됨 · Nathan Purcell
0
팔로워
0
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 3월 01일에 게시됨 · Nathan Purcell
0
팔로워
0
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 2월 17일에 게시됨 · Nathan Purcell
0
팔로워
0
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 1월 18일에 게시됨 · Nathan Purcell
0
팔로워
0
투표 수
0
댓글
Nathan Purcell님이 에 댓글을 입력함
Salvador Vazquez can we have an update please?
댓글 보기 · 2023년 1월 18일에 게시됨 · Nathan Purcell
0
팔로워
1
투표
0
댓글
Nathan Purcell님이 에 게시물을 만듦
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?
2022년 11월 15일에 편집됨 · Nathan Purcell
1
팔로워
1
투표
1
댓글
Nathan Purcell님이 에 댓글을 입력함
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).
댓글 보기 · 2022년 11월 07일에 게시됨 · Nathan Purcell
0
팔로워
0
투표 수
0
댓글