최근 검색


최근 검색 없음

Yavor Ivanov's Avatar

Yavor Ivanov

가입한 날짜: 2024년 9월 02일

·

마지막 활동: 2025년 2월 27일

Senior Software Engineer — Community Experience

팔로잉

0

팔로워

0

총 활동 수

17

투표 수

7

플랜 수

5

활동 개요

님의 최근 활동 Yavor Ivanov

Yavor Ivanov님이 에 댓글을 입력함

댓글Global security and user access

Redaction suggestions should not be part of an addon in my opinion. Some of the features listed above are more quality of life and don't make much sense to be part of an addon. Please consider bundling them more appropriate with enterprise or even other tiers.

댓글 보기 · 2025년 2월 25일에 게시됨 · Yavor Ivanov

0

팔로워

0

투표 수

0

댓글


Yavor Ivanov님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

Thanks for taking the time to reply Gaurav. If you need anymore feedback or examples don't hesitate to contact us.

댓글 보기 · 2025년 1월 27일에 게시됨 · Yavor Ivanov

0

팔로워

0

투표 수

0

댓글


Yavor Ivanov님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Admin Center

We have basic cases for this. For instance, we want to add an internal note based on specific conditions to draw the attention of our agents that a ticket is originating from an engineer conducting testing.

We also have more complex cases where we want to add a note if a ticket is transferred from certain groups to others, enabling agents to promptly identify the change and take appropriate action without having to manually review the ticket events to ascertain the sender and reason for the transfer.

Lack of fundamental control over triggers merely shifts the burden of implementing these missing features onto our backend engineers.

댓글 보기 · 2024년 12월 11일에 게시됨 · Yavor Ivanov

0

팔로워

2

투표 수

0

댓글


Yavor Ivanov님이 에 댓글을 입력함

댓글Workflow best practices and recipes

Hm adding an internal note should not be an AI only feature in my opinion. Most of our use cases that require this are not based on AI cases. It needlessly overcomplicates backend integration with API or Ultimate.

댓글 보기 · 2024년 12월 11일에 게시됨 · Yavor Ivanov

0

팔로워

0

투표 수

0

댓글


Yavor Ivanov님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

We also have a similar case where agents are starting the tickets first instead of the customer.

 

We would love to be able to prefill the fields so that an agent clicking on a link in our system would get redirected to Zendesk with the requester, title and maybe a few other fields (brand, group, priority, type…) already prefilled in. Ideally we would also love to have a macro preselected or used already so that the agent can edit if they want or just send it as it is after double checking. I can also see a case where suggesting a list of macros by ids would be useful.

 

Our use case is that we want our agents to contact customers in certain predefined scenarios and currently this requires a complex solution using the API to achieve or require a lot of manual work for agents where you copy/paste a bunch of stuff and remember or look up different cases.

댓글 보기 · 2024년 12월 09일에 게시됨 · Yavor Ivanov

0

팔로워

1

투표

0

댓글