最近搜索
没有最近搜索

Phil Andrews
已加入2022年6月29日
·
最后活动2022年11月14日
关注
0
关注者
0
活动总数
22
投票
10
订阅
8
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Phil Andrews
Phil Andrews 进行了评论,
Thanks for the info Dainne Kiara Lucena-Laxamana!
@... I'd be looking to include the assignee in the message to a channel as a tag. So for instance whenever a ticket is assigned we send a message to a Slack channel with info on the ticket/orgnaisation and tag the assignee - we currently do this via webhook and Zapier. It would be preferable to do this via the ZD Notification instead.
We also do this because the in-page notifications in Zendesk aren't great. Using Omnichannel routing we can only notify the assignee via email but we don't use email often so that's not really useful. The notification icon in Zendesk itself also only works with Messaging chats, and not email tickets - so again we're missing a notification opportunity. Slack is the best we've found so far given how much our team are on Slack.
查看评论 · 已于 2022年11月14日 发布 · Phil Andrews
0
关注者
0
投票
0
评论
Phil Andrews 进行了评论,
Is there a way to @ mention users in Slack based on the assignee name on the ticket?
查看评论 · 已于 2022年11月10日 发布 · Phil Andrews
0
关注者
2
投票
0
评论
Phil Andrews 进行了评论,
I want to use omnichannel routing for a certain group in ZD instance. However, we have people in that group who need to be able to view tickets in that group, but I don't want them to be able to receive tickets as part of the routing - is there a way to achieve that?
For example I have a "Level 2" Group, say there are 5 agents in that group. 3 of them I want to receive tickets to serve, but the other 2 agents are only in the group so they can view those tickets if they need to. Those 2 agents can't have access to all ZD tickets though, hence they are in a group.
查看评论 · 已于 2022年9月13日 发布 · Phil Andrews
0
关注者
3
投票
0
评论
Phil Andrews 进行了评论,
Here is an additional use case for this thread:
We've rebuilt our bot flow from the ground up to improve the experience we're offering customers and to incorporate more features than the original basic flow we built. We've decided to build this in sandbox so that multiple people across the business can have input - such as copywriters. Building in sandbox allows us to test this too by pushing it live and running test chats from the sandbox help centre. There is no disruption to our agents actively working as this doesn't touch production at all. Obviously now it'll be frustrating for us to put this in to production and manually re-build this.
查看评论 · 已于 2022年7月18日 发布 · Phil Andrews
0
关注者
0
投票
0
评论