When a customer message is displayed in the Help Desk, there will be a small icon indicating the channel the message was sent from.

A message sent in the web Messenger will have a Messenger icon. One sent in a mobile app will have an Apple or Android icon. An email will have an envelope, and an SMS message will have a phone icon. Messages sent from a social media platform (WhatsApp, Facebook, Instagram), will have the logo of that platform.

Here’s an example of where to find the channel icon in a message shown in the Help Desk 👇

This feature is called teammate presence. It allows you to see if another teammate is looking at a conversation or ticket. This helps you avoid potentially working on the same conversation or ticket and helps you collaborate with other teammates.

This feature can be turned on/off from your Help Desk Settings: Help Desk > Teammate Presence:

If you need to share a conversation, or keep a record of it, you can easily download its transcript.

Just go to a conversation and click the three dots to see options, then click Export conversation.

The conversation transcript will now download as a .txt file.

Your users and leads can also download a conversation transcript while they chat to you in the Messenger:

Conversation transcripts are only available on desktop in the Messenger.

What’s included in the transcript?

Your conversation transcript includes:

What’s not included?

The file does not include:

Images, attachment, GIFs, articles and apps will be labelled as text in the file, like [GIF] and [Article - article name], for example.

You can't export multiple conversation transcripts from your workspace but you can use our API to do so using our Conversations API.

Troubleshooting steps you can try if...

User is seeing funny characters in their downloaded transcript. It can happen that users on old machines (outdated versions of Mac, Windows or Linux) will download a transcript that has unicode characters (e.g. new emojis) not present in their outdated OS. These characters will shows as random letters/numbers and not what they see in the browser. This is a problem on the user’s end rather than ours and we can’t fix it. Afflicted users need to update their OS (or update their character sets) or view the transcript on another machine. Other people they send the transcript to will not have the same problem, they will see the correct characters (unless they’re on the same outdated OS/machine).

Part of the conversation isn't included in the transcript. If a chunk of the conversation isn't included in the transcript it's likely because the conversation is over the visible comment limit of the transcript, which at the moment is set to 200 lines. If the conversation is over the 200 line limit then the transcript will include the first line of the conversation and then will skip the conversation until it's within the 200 comment line limit.

Yes, it's easy to share a specific reply in a conversation with a teammate. Just hover over the reply and click on the three dots:

Then, click Copy link to selected conversation part.

This link will copy to your clipboard. Now, when you share the link with a teammate, it will bring them straight to that specific reply in a conversation.

If a customer is part of multiple companies, currently, there isn't a default method to see which company they were logged in for when they started a conversation in the Messenger.

To track this, you could record the company the customer is logged in for on a custom person attribute, when they are loaded in the Messenger. You would need to edit your Messenger installation to set the value for this attribute.

Then you can use a workflow to add a note to the conversation that references that custom attribute, when a customer starts a conversation in the Messenger.

For example, you could create a custom person attribute called Current Company.

Then create a "Customer sends their first message" workflow that sends on the channels you have your Messenger installed (Web, iOS, and Android), and select the "Add a note" action.

Finally, add the Current Company custom person attribute to the note.

Once live, this workflow will add a note with the name of the company the customer is logged in for when they start a conversation in the Messenger.

You can view the source URL of a conversation by going to the initial message and hovering over the chat icon. 👇

View inbound email data and reporting by going to your Conversations report and click + Add filter then select a message Channel (email).

View details about potential duplicate users from the Help Desk right sidebar and access better context across those potential duplicate’s other conversations.

Teammates will see a warning in the User Data section of the right sidebar when potential duplicates are present. Clicking the warning will show details of those potential duplicates including the ability to open each of those user's profile pages in a new tab.

An alert icon beside the Potential Duplicate’s Phone, Email and/or WhatsApp number will show what attribute they matched on.

Potential duplicates are identified by:

Yes, you can view the details of each potential duplicate and their matching attributes from the conversation Details panel in the inbox.

If the conversation is with a lead and the detected duplicate is a user, you can click Merge Lead into User. This will refresh the conversation in the inbox with the details of the newly merged user, so you can see previous conversations etc.

Yes, you can delete a reply you’ve sent to a user in error. For example, if you include sensitive information in a reply, you can delete it so the user will no longer see it.

You can also delete replies your user has sent to you.

To delete a reply via the Help Desk, click the three dots next to the message.

Then select Delete message.

You’ll be asked to confirm your choice. This helps ensure you don’t delete a message by accident.

Your user will now no longer see the message. Here’s how it will appear to them in the Messenger:

Here’s how the deleted message will appear to you in the inbox:

Yes, you can delete a note on a conversation. Deleting a note works in the same way by clicking the three dots beside the note and pressing delete message.

Here’s how the deleted note will appear to you in the inbox:

When your customers CC people into a conversation it can cause your company’s support addresses (e.g. support@exampleapp.io) to be included in the conversation as a lead. To prevent this from happening you’ll need to mark these addresses as ‘company addresses’ to let us know to ignore them.

In your email forwarding settings, you can add as many company addresses as you’d like us to ignore. Once added, they won’t appear in group conversations.

Yes, when you’re chatting to a customer, you can loop another customer into the conversation.

This is useful if you’re chatting to a customer and they need to get a colleague’s input on a specific issue, like pricing for example.

Simply click next to Reply in the composer and then select the current contact to add another contact as a participant by typing their name or email address.

Learn more about managing group conversations here.

Initiating conversations with multiple people via email

You can also initiate an email conversation with multiple people via the Help Desk. Start a conversation from the top-left and then select Conversation

Set the channel to Email:

Add multiple users into the To field:

By default all users will be added as participants into the same conversation. If you want to create separate conversations for each user, you can toggle on the Send Separately option:

Yes, we've shipped a feature that lets you create an automation Workflow to close conversations when they match certain criteria.

You can only delete conversations in the Help Desk if you archive or delete the user attached to the conversation.

To delete a user and their conversation(s), you can use any of these methods:
​
1. Archive or delete the user attached to the conversation. Archiving acts as a soft delete, and if the person returns, all data, including associated conversations, will be restored.

2. To permanently remove all data associated with a user or lead, go to Settings > [Workspace name] Data > Deleting people data and enter their user ID or email address to delete them individually.

3. Alternatively, use Intercom's REST API to delete users in bulk, which will also delete their associated conversations.
​

The differences between the webhook events are as follows:

To set up webhooks for creating and deleting conversations in Intercom, use the following events:

A red exclamation mark error typically appears in messages when the sender has configured their Reply-To address in their email settings to be different from their From address.

This is an email header used by the sender to specify which email address should receive replies. This issue is due to a setting on the end-user's side and cannot be changed within Intercom.

Intercom uses the From field of an email to identify the sender, but sometimes, with contact forms or some email forwarding configurations, the sender may be changed to the account doing the forwarding, instead of the original sender.

However, it also serves as a bit of a catch-all "errors and issues" notification to warn you of potential bad actors. For example, is an email is not verified, or if it was forwarded several times before reaching your Inbox.

​

So this is not necessarily an indicator that the end-user is a bad actor, just that the risk score applied was higher than our threshold for a completely legitimate email.

Links in inbound emails will show tooltips on hover:

Linked images in inbound emails will show tooltips and orange overlay that disappears on hover:

First, try clearing cache/cookies, using an incognito window, or trying a different device/network. If the issue persists, it might be related to Content Security Policy (CSP). Send a recording of trying to copy and paste, along with the console errors that show. Alternatively, you can provide a support agent with access to your website as an end user to test the issue on their end.