Side conversations are spaces in a ticket where agents can have a side conversation with a specific group of people, or discuss a specific area of concern or course of action. You can use them to organize information about a ticket.
Advantages of using side conversations
Problems often consist of multiple parts, and solving them often consists of conversations with different people. It gets confusing for everyone involved when all of the questions and answers are mixed together in one place without any kind of organization.
For example, let’s say you need to discuss something with your Legal team, but don’t need or want other people involved.
- Find, organize, and manage information about a specific part of an issue
- Have a conversation with the right people
- Find specific questions, answers, and replies. Ensure conversations happen outside of the main conversation with the requester
- Have multiple standalone conversations that are separate from each other
- Get outside help without pulling others into the main ticket directly
Recommendations about side conversations
- The assignee should create and manage side conversations in the tickets they're responsible for. This allows administrators to create triggers based on the assignee role, and enables easier handoff between agents.
- Set up triggers to take advantage of the side conversation event conditions to fully integrate them into your workflows and to keep agents on top of the activity within them. See Setting up trigger conditions for side conversations.
- Create trigger conditions for side conversations to make sure that assignees know when a side conversation is created, closed, replied to, and reopened. Without them, the agent assigned to the ticket (ideally, this person is also the creator of the side conversation) may have a hard time knowing what’s going on with a particular issue.
- Remember that the creator of the side conversation doesn't automatically receive email replies to side conversations. That’s not the default behavior. Also sending side conversations to your own support address is not supported and will result in those side conversations ending up in the Suspended tickets view.
About side conversation channels
When you create a side conversation, you can choose to have the side conversation in one of these channels:
- Email: Creates an email-based side conversation (see Creating side conversations).
- Microsoft Teams (if enabled): Creates a Microsoft Teams-based side conversations (see Using Microsoft Teams in side conversations).
- Slack (if enabled): Creates a Slack-based side conversation (see Using Slack in side conversations).
- Ticket (if enabled): Creates a side conversation child ticket
(see Using side conversation child
tickets).Note: Side conversation child tickets can be routed by omnichannel routing. See About omnichannel routing with unified agent status.
In the Agent Workspace, side conversations are created from the context panel. In the standard agent interface, side conversations are created from Side conversations at the top of the ticket conversation pane.
|Agent Workspace||Standard agent interface|
About support addresses used to send side conversations
Side conversation notifications are sent from the support address associated with the ticket that the side conversation is on (for example, email@example.com). If you have multiple brands and support addresses, side conversation notifications come from each of your support addresses (for example, firstname.lastname@example.org).
Optionally, you can use the Select an Address app to control the email address that side conversation notifications are sent from. For example, the app allows you to change the default support address associated with a ticket.
If you have internal email routing rules (for example, in Microsoft Exchange), we recommend that you include references to each of your unique support addresses. Otherwise, email notification for side conversations will not be routed correctly. Check your allowlists and blocklists.