最近の検索
最近の検索はありません

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
コメント