最近搜索
没有最近搜索

Lindsay A
已加入2021年4月15日
·
最后活动2022年7月11日
关注
0
关注者
0
活动总数
14
投票
8
订阅
3
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Lindsay A
Lindsay A 进行了评论,
Lindsay A 进行了评论,
We have been using this app for years and it's worked great for 1 slack channel updates. We recently tried to use the app to post to 2 different channels in 1 slack workspace and it appears that we can't customize the app to post different tickets to the different channels. Is there a way to do this?
Example: #ticket-notifications: This should post tickets that are new or updated for our advanced support team.
#solved-by-basic: This should post tickets that are solved by the basic support team.
Thanks!
查看评论 · 已于 2022年7月11日 发布 · Lindsay A
0
关注者
0
投票
0
评论
Lindsay A 进行了评论,
In the Zendesk policy it even mentions that someone on the team can access those soft-deleted users:
"Deleting users from your account soft deletes them, and that means that the users are still in the Zendesk database and accessible on a limited basis only to Zendesk employees with certain database privileges."
If someone on the Zendesk team can still access the information in the database, why can't they recover the deleted users when requested by the account owners? This is a shady practice to allow Zendesk access to these users but not the account owners who request this data. Why does Zendesk need it? What are they doing with it?
This is not a "soft delete" if the data can't be restored and it is CLEAR that people are asking for this in times of a mistake being made. Holding client data hostage is not a great policy.
查看评论 · 已于 2022年5月06日 发布 · Lindsay A
0
关注者
1
投票
0
评论