최근 검색
최근 검색 없음

Eski Admin Hesabı
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2021년 10월 23일
팔로잉
0
팔로워
1
총 활동 수
27
투표 수
4
플랜 수
12
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Eski Admin Hesabı
Eski Admin Hesabı님이 에 게시물을 만듦
Hello,
We have different departments and have different teams in all of them. We need sub groups for each department (Group) in order to manage Chat and Ticketing system. The main purpose is; restricting agents in different groups (Deps) to see each others' tickets.
Actually, we are creating chat groups, different gorups for each department's team. They have to see each others' tickets in the same department for ticket history but should not see other departments' tickets.
Creating sub groups will solve all of the problems.
2021년 8월 12일에 게시됨 · Eski Admin Hesabı
13
팔로워
27
투표 수
23
댓글
Eski Admin Hesabı님이 에 댓글을 입력함
Why don't we have sub groups which will help us manage to restrict agents to see other groups' tickets?
Is there a way to do this?
댓글 보기 · 2021년 8월 12일에 게시됨 · Eski Admin Hesabı
0
팔로워
2
투표 수
0
댓글
Eski Admin Hesabı님이 에 댓글을 입력함
We have a social media group dealing with social media messages.
We want to route Instagram DM to these groups, but we couldnt find any documentation except then Chat Module Routing.
We dont want this group to chat but we want them specificly answer Instagram DMs. So we dont want to use Chat Routing system, as we have other triggers are set for segmentation also.
How can we route Direct Instragram Messages? We tried Support Triggers but not working as desired, the request is distributed randomly.
댓글 보기 · 2021년 7월 08일에 게시됨 · Eski Admin Hesabı
0
팔로워
0
투표 수
0
댓글
Eski Admin Hesabı님이 에 게시물을 만듦
We need to prevent admins to give other staff admin roles due to our security issues. Creating custom roles are not suitable because custom roles doesnt have capabilities of and admin.
The need is simple; There should be a new role, "power admin" who has all rights and admins (Current role) who all admin rights except granting other staff for admin or power admin role. If its not possible; a granting option for preventing customly created role (for example clone admin) to give other staff or end users admin role will be great.
Thanks.
2021년 7월 06일에 게시됨 · Eski Admin Hesabı
2
팔로워
6
투표 수
3
댓글
Eski Admin Hesabı님이 에 게시물을 만듦
APı's are used for sharing data with other applications and 3rd parties. Projects worldwide are genarally depends on outsourcing some services.
In Zendesk, whenever you authenticate another application, the API shares all the information accountwide. This is unacceptable for Cyber Security and GDPR issues.
The demand is, Zendesk should find a solution to restrict all data sharing or give admins of their customers to restrict shared data on Zendesk.
Thanks.
2021년 6월 17일에 게시됨 · Eski Admin Hesabı
0
팔로워
1
투표
0
댓글
Eski Admin Hesabı님이 에 게시물을 만듦
Hello,
Tokens are created on Zendesk accountwide which creates Cyber security issues whenever we want to integrate any application or any other institution. This situation abondon us to make new projects.
Our demand is, every API should have its own token especially for Cyber Security issues. A token shouldn't give authorization to open all the gates for all API's in Zendesk. Prioritized Tokens for specific API is a must in today's world. Zendesk must find a way for this problem.
Have a nice day.
2021년 6월 17일에 게시됨 · Eski Admin Hesabı
0
팔로워
2
투표 수
1
댓글
Eski Admin Hesabı님이 에 댓글을 입력함
Hey,
Is there a way;
1- to limit agents not to download the attachments without redaction or deleting? Security issues are very strict nowadays because of GDPR in every country.
2-to limit agents workspace not to show the attachments to a specific role when the ticket is closed? Our goal is "to show attachements to admins or another specific role (teamleaders) "
Thanks
댓글 보기 · 2021년 6월 03일에 게시됨 · Eski Admin Hesabı
0
팔로워
0
투표 수
0
댓글
Eski Admin Hesabı님이 에 게시물을 만듦
I would like to stamp Today's date on custom created User Field in order to see when the form was created or a ticket field is updated.
Is there a way for us to choose @today, @yesterday, @tomorrow to be used in a custom date field on the action side of a trigger or automation. Most of the applications are capable of doing this including explore the reporting tool. So I think the selection for a date field should be relative also.
Thanks.
2021년 2월 04일에 게시됨 · Eski Admin Hesabı
13
팔로워
13
투표 수
5
댓글