최근 검색
최근 검색 없음

Jamie Noell
가입한 날짜: 2021년 10월 26일
·
마지막 활동: 2025년 1월 31일
팔로잉
1
팔로워
0
총 활동 수
94
투표 수
19
플랜 수
40
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Jamie Noell
Jamie Noell님이 에 게시물을 만듦
Are any plans for trigger deployment that include an email address (which typically shows as a conflict since the sandbox domain differs)? With a similar product, Salto just looks at what's before the @ for the comparison.
Example:
help@abc.com
help@abc-sandbox.zendesk.com
Because both have help@, then ideally Deployment feature would deploy the trigger. We have to migrate our email routing triggers since Zendesk is doing a full email address comparison.
2025년 1월 16일에 게시됨 · Jamie Noell
2
팔로워
4
투표 수
2
댓글
Jamie Noell님이 에 댓글을 입력함
Overall, I really like the triggers/automations deployment except for 2 points, and we use this feature a lot. Excited for the new changes announced in the EAP!
Issues:
1. The over-notification of updated triggers due to trigger placement changes as described above.
2. I'll submit in product feedback but also want to check here if there are any plans for trigger deployment that include an email address (which typically shows as a conflict since the sandbox domain differs). With a similar product, Salto just looks at what's before the @ for the comparsion.
Example:
help@abc.com
help@abc-sandbox.zendesk.com
Because both have help@, then the trigger would deploy. We have to migrate our email routing triggers manually due to this issue.
댓글 보기 · 2025년 1월 16일에 편집됨 · Jamie Noell
0
팔로워
0
투표 수
0
댓글
Jamie Noell님이 에 댓글을 입력함
Our use case is that another system sends automated emails, and we set the reply-to address for those emails to a Zendesk support address. This way, any reply threads back into Zendesk. The original requester is the system sending the automated emails, and if a real person replies, we want to change the requester from that system to the real person. I'm working on a webhook to update the requester, but it would be really helpful (and prevent the possibility of a webhook collision if there were a trigger condition of “Set requester” to “Current user.”
댓글 보기 · 2025년 1월 11일에 게시됨 · Jamie Noell
0
팔로워
0
투표 수
0
댓글
Jamie Noell님이 에 댓글을 입력함
It seems like your documentation is out of date.
In an Explore dashboard that you have previously shared, copy the URL of the dashboard from your browser address bar (you'll need it later), then click Schedule.
should be
- Click the drop-down arrow by the Share button.
- Select Schedule delivery.
“Schedule” is no longer visible in the new dashboard builder.
댓글 보기 · 2025년 1월 02일에 게시됨 · Jamie Noell
0
팔로워
0
투표 수
0
댓글
Jamie Noell님이 에 게시물을 만듦
The Deployment feature is a good start, but it would save time if…
1. If we only have one Premium Sandbox, it would be nice to just assume this is the one we want to deploy.
2. I wish we could deploy more than one trigger at a time (like Salto allows).
3. I wish we could run a report comparing all triggers and automation configuration (like an audit) to know where we have unintentional differences between our environments (like Salto offers).
4. I wish we could migrate macros - because we cannot, we usually just configure in production, but we use our sandbox for training courses, so it would be ideal to have our key macros in sandbox for training purposes. We just don't have time to maintain them manually in both.
2024년 10월 24일에 편집됨 · Jamie Noell
1
팔로워
1
투표
1
댓글
Jamie Noell님이 에 댓글을 입력함
Similar to Jasmine's question, can you at least advise if this feature will be in the core product or require the Advanced AI (or other) add-on?
댓글 보기 · 2024년 10월 09일에 게시됨 · Jamie Noell
0
팔로워
0
투표 수
0
댓글
Jamie Noell님이 에 댓글을 입력함
Our request conversations can be quite lengthy as it is. The MCE format has helped a lot in showing the boundaries of comments with the new colors, but the one remaining issue is when simplified email threading does not work for certain clients' email.
PLEASE :) prioritize fixing this to help us make our agents happy and enable them to respond to our clients more efficiently.
댓글 보기 · 2024년 7월 16일에 게시됨 · Jamie Noell
0
팔로워
0
투표 수
0
댓글
Jamie Noell님이 에 게시물을 만듦
We have a lot of team-to-team tickets, so with MCE, all comments are from agents and hence, have a gray background. It would be nice if the agent requester's comments were green to differentiate the resolver comments from the requester comments.
2024년 7월 12일에 게시됨 · Jamie Noell
1
팔로워
2
투표 수
2
댓글