Recipients of a side conversation can reply through email, just as they would to any other email. Side conversations retain the original formatting of incoming emails. The assignee on the ticket can also reply to a side conversation through the ticket from the Zendesk Support interface. Regardless of how a response was sent, it appears in the ticket for the assignee.
Viewing side conversations
From the ticket interface in Support, you can view a list of all the side conversations on the ticket.
To view a list of side conversations on a ticket
- Open the ticket and then click the Side Conversations bar.
A list of side conversations on the ticket displays.
To open an existing side conversation on a ticket
- From the list of side conversations on the ticket, double-click the side conversation that you want to open.
Replying to side conversations
The people on a side conversation can be inside or outside of your organization. You can create side conversations on open or closed tickets. If someone replies to a side conversation on a closed ticket, triggers won’t be run on it even if they have side conversation conditions.
To reply to a side conversation
- From the ticket interface, open the side conversation you are interested in.
- Scroll up to review earlier replies in the side conversation, if needed.
The conversation opens to the first unread reply for the agent viewing conversation. The most recent replies appear at the bottom of the side conversation.
- Update the list of recipients (if needed), add your reply and attachments, and then click Send.
Each message has its own set of recipients, which can be edited at reply time.
When you add attachments, you can select a file from your computer or include one or more attachments that already exist in the ticket. Click the attachment icon () and select From computer or From ticket.
If you changed your mind and don’t want to send the message, click the delete icon (). The delete icon () does not delete the entire thread. Once you start a thread, you cannot delete it.
All of the recipients on the side conversation receive an email notification with your message. The message being replied to is included as quoted content on outgoing emails.
This notification doesn’t automatically include the assignee of the ticket or the creator of the side conversation. See Recommendations about side conversations.
If you have an email signature set up, it is automatically inserted into the message. If you have personalized replies enabled, these settings are also included in your message. Conversations are sent from the support address associated with the ticket, and if configured, include the address name.
Rich text editing in the side conversation composer
The side conversation composer is a rich text editor that includes a toolbar with options for editing and formatting your text. Rich text editors are sometimes called WYSIWIG (what you see is what you get) editors.
The formatting options in the composer vary a little depending on the side conversation channel involved (Email, Slack, or Ticket). For example, these are the formatting options for email:
The composer for Email and Ticket side conversation includes a full array of formatting options because email supports full HTML display. The composer for Slack side conversations includes fewer formatting options because Slack uses a subset of Markdown for formatting. With Slack side conversations, you can also use Markdown-style shortcuts while typing in the composer, and they will be converted to rich text. For example, if you type bold, bold is applied to the text in composer.
This table lists the editing options that are available with different side conversation channels.
|Formatting option||Email & Ticket side conversations||Slack side conversations|
|Bullet list, Numbered list||Available||Available|
Note the following limitations with the composer:
- The composer doesn’t support inline images. You can, however, add images as attachments.
- If you paste complex rich text into the composer, you will likely lose some formatting.
- Rich text and Markdown formatting is not supported in email signatures that appear in side conversations.