Suite | Professional, Enterprise, or Enterprise Plus |
Support with | Collaboration add-on |
作为基于电邮的协作快捷对话的替代方法,专员可使用工单中的协作快捷对话来发起和参与Slack讨论串。您发起的Slack协作快捷对话在工单和Slack应用程序中可见。与电邮对话一样, Slack协作快捷对话也会被记录为工单活动日志,并用 作工单触发条件。
使用Slack创建协作快捷对话
创建协作快捷对话时,您可以选择使用电邮或使用Slack。
使用Slack创建协作快捷对话
- 在工单中,打开背景信息面板,单击协作快捷对话图标 (
),然后单击加号 (+)。
- 选择 Slack 作为对话类型。
- 输入Slack频道和您的消息。还可以添加附件。
有关撰写区的更多信息,请参阅 协作快捷对话撰写区中的富文本编辑。
您每次可以在一个Slack频道中开始协作快捷对话。您无法合并Slack和电邮对话。如果您有很多Slack频道,可能需要一些时间才会显示可用频道列表。
如果您有多个Slack工作区连接到Zendesk Support,该工作区将显示在渠道名称之后。例如:#support - 工作区 A、#general - 工作区 A、#support - 工作区 B、#general - 工作区 B 等。
- 完成撰写消息后,单击 发送。
Slack频道中的团队可查看您的消息并直接回复讨论串,而无需登录Support。
Slack回复将自动包含在工单的协作快捷对话中。
对话可以根据需要来回继续,直到获得所需的信息。
- 协作快捷对话完成后,单击工单中的 标为已完成 以 关闭协作快捷对话。
删除Slack协作快捷对话
要删除Slack协作快捷对话,您必须是创建Slack协作快捷对话的专员或管理员。当您删除时,协作快捷对话将从工单和Slack中移除。在Slack中编辑或删除的协作快捷对话消息也会反映在工单上。
删除Slack协作快捷对话
- 在工单中,打开 背景信息面板 ,然后单击协作快捷对话 (
)图标。
此时会显示工单的协作快捷对话列表。
- 选择您要删除的协作快捷对话。
您只能删除Slack协作快捷对话。您无法删除电邮协作快捷对话。
- 单击选项菜单图标 (
),然后选择 删除。
- 当出现确认消息时,单击 删除 以确认删除。
关于限制和断开Support与Slack之间的链接
- 只有 1000 个字符或更少字符的工单评论才可以插入Slack协作快捷对话。
- 支持Slack @提及,但不能自动完成。您必须在尖括号中输入用户的Slack成员 ID。例如
<@U1H63D8SZ>
更新。要查找专员的Slack成员 ID,请前往Slack中专员的个人资料。单击选项菜单 (
),然后选择 复制成员 ID。
或者,您也可以添加 @这里,以通知每个当前登录的人,或添加 @渠道,以提醒每个渠道成员。
- 在协作快捷对话撰写区中输入的富文本格式和Slack Markdown 文本 可能无法始终如预期在Slack中显示。
不支持以下Slack功能:
- 私信
要解决此问题,管理员可以设置只有一名成员的私密Slack频道(例如 #lkelly- private),并将其添加到用于 Zendesk 整合的Slack中。
- 表情符号反应
- 打字指示器
如果 Zendesk 和Slack之间的链接断开,例如,如果管理员从Slack频道移除了 Zendesk 应用,或者存档或删除了您用于协作快捷对话的Slack频道,您仍然可以在工单,但您无法再使用该Slack频道发送或接收协作快捷对话更新。
翻译免责声明:本文章使用自动翻译软件翻译,以便您了解基本内容。 我们已采取合理措施提供准确翻译,但不保证翻译准确性
如对翻译准确性有任何疑问,请以文章的英语版本为准。
54 条评论
Marrit Jansma
Hello, does anyone know about the possibility, or existing feature request, to be able to link existing Slack convo's. This because we always check whether someone has already asked the question, and if so, we follow/link the existing Slack conversation instead of repeating the questions that overflood our internal channels.
Thanks a lot for thinking along/letting me know!
0
Ashok Gangwar
There seems to be nasty bug in this feature.
If a Side Slack Conversation is revived i.e let's say the Zendesk case is closed and after 3-4 months someone replied on that Slack Thread from Slack itself the Zendesk will open a followup case. Which is very bad.
We have stopped using this now.
0
Joselo Torres Landa
Hey 1263797803409, Im using it exactly as you mention on your comment. I open a side conversation within Zendesk, type my message. Slack received it on the appropriate channel (the one I configured). within slack someone respondes to the message and it get to Zendesk, twice.
0
Amjid Khan
Doesn’t sound right.
Our use of side conversation is from within the Zendesk ticket open a side conversation to a slack channel. Then within the ticket all messages appear within one single comment and no duplicates. It works really well.
You’ve not been clear on how your using it maybe that might help and Zendesk can help.
1
Joselo Torres Landa
I'm in the process of implementing my zendesk instance and one feature we are excited about is the slack side conversation, however while testing it, every message gets duplicated on the Zendesk ticket.
Is this how its supposed to work?
0
Sebastián Paredes
¿Nadie tiene problemas con las menciones? estoy copiando y pegando cuidadósamente el @XXXX que tienen los usuarios en Slack y no los menciona de ninguna forma
0
Paolo
You need to initiate the side conversation from a Zendesk ticket to Slack. Side conversations can't be initiated from Slack to Zendesk. More information here.
Best,
Paolo | Technical Support Engineer | Zendesk
0
Jed Hollander
Apologies if this was asked / answered but, can a side conversation be initiated from Slack to Zendesk, or can it only be done from Zendesk to Slack?
thanks
0
Paolo
This is the expected behavior. When a Slack side conversation that belongs to a closed or archived ticket receives a reply, a follow-up ticket is automatically created. The new ticket will have the side conversation in it and keep the original assignee and group value. The new ticket will be able to run triggers so it can show up in the appropriate views. Unfortunately, there is no workaround for this yet. This would be a good product feedback though.
I encourage you to create a new post in the General Product Feedback topic in our community to engage with other users who have similar needs and discuss possible workarounds. Conversations with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
Best,
Paolo | Technical Support Engineer | Zendesk
0
Mems Benipayo
Hello! This is a question on the “mark done” button in slack side conversations, mentioned by Amjid and Lydia.
Context
- tickets would move to open status when a reply comes in via slack side convo initiated within a ticket
- agents are instructed to “mark done” slack side convos when the convo related to the ticket is concluded under the assumption that this would prevent the ticket from reopening
- at this point, the ticket is solved and would move to closed status in about 24hrs
- there are times that the same side convo thread would be used for later scoping and review
Issue
- Regardless if side convo is marked done or not, replying in the thread creates a new ticket via a follow up ticket (“follow up to ticket xxx” linked to the original where the side convo thread was created)
Impact
- causes confusion and floods the inbox with follow up tickets which we have to keep open since subsequent replies would continue to create follow ups
Question
- how do we make sure that marking done breaks the link between slack and zendesk side conversation?
Thank you!
0
登录再写评论。