Skip to content

Intercom ​

Overdesk connects to Intercom with an access token from a developer app in your own workspace. It reads your conversations, learns from your past conversations, macros and Help Center articles, and posts each draft on the conversation as an internal note for your team to review. For the overview of Overdesk with Intercom, see the Intercom page on overdesk.io.

Connect Intercom ​

You need to be an owner or admin in Overdesk.

  1. In Intercom's Developer Hub, create an app for your own workspace.
  2. Open the app and copy the access token from Configure, then Authentication.
  3. In Overdesk, open Integrations, choose Intercom, and paste it into Access token.
  4. Choose Connect.

Overdesk writes to Intercom as the teammate the access token belongs to, so internal notes, and replies once sending is on, appear under that name.

Give the app permission to read contacts. An Intercom conversation names its customer only through their contact, so Overdesk reads the contact to check your excluded senders and the customers you have erased. If your list has any entry, or you have erased anyone, and Overdesk cannot read a conversation's contact, because the app lacks that permission or the contact no longer exists, it does not draft, nudge, classify or answer @Overdesk on that conversation, since it cannot tell whether the customer is on your list or one you erased. With an empty list and no erasure it does not read the contact to check anyone, but it still reads it to know whom a reply is for, on every draft. Before it sends a reply on its own, it also reads the contact of anyone else in the conversation, to check them against your excluded senders, your rules' customer lists and the people you erased, and a contact it cannot read keeps the reply for your team.

Triage, analyses and reports read the contact the same way when your list has any entry, and leave out a conversation whose customer is on it. A conversation whose contact Overdesk cannot read is left out of them too, since Overdesk cannot tell whether its customer is on your list.

What joins your knowledge base ​

  • Past conversations, through Sync past conversations, every night at 03:00.
  • Macros, imported as saved replies alongside your conversations.
  • Help Center articles, through Sync help desk docs, every night at 04:30. Only published articles are imported. If your Intercom app is not allowed to read articles, the Knowledge base page says "Intercom would not let Overdesk read your Help Center articles". Check the permissions on your app in the Developer Hub, then choose Sync now on that page to confirm the fix took.

Drafting also needs a docs site address in Settings → Knowledge base, even if your Help Center is where your docs live. See Point Overdesk at your docs.

Where drafts appear ​

Every draft arrives on the conversation as an internal note, which your customer never sees. Intercom has no API for filling in the reply composer, so the unsent draft reply option in Where drafts go stays with Help Scout, and your team keeps receiving notes.

If you edit or discard a draft from its page in Overdesk, Overdesk adds a note to the conversation saying what changed. Each draft on the Agent drafts page has an Open ticket button that takes you to the conversation in your Intercom inbox. If Overdesk cannot reach Intercom to work out your workspace, the button is left off and you can find the conversation by its number.

Sending replies ​

Once your workspace turns sending on, Overdesk sends the replies your guardrails approve as the teammate your access token belongs to. It sends on Messenger conversations and on email conversations. A WhatsApp, SMS, phone or social conversation waits for your team. Replying assigns the conversation to that teammate, and Intercom adds the teammate's signature and "We run on Intercom" to what your customer receives.

After a reply Overdesk closes the conversation, as a second step, unless you choose Leave as is under After Overdesk sends a reply, someone has written in the conversation since the reply, or Overdesk cannot confirm its reply is the newest message, in which case it stays open. If the customer writes again, Intercom reopens it. In our testing, closing a conversation this way did not send the customer a rating request.

Overdesk cannot see a teammate who is part-way through a reply, so if a teammate answers at the same moment as an automatic reply, your customer can get both.

A reply that promises a person will follow up can be sent, as on the other help desks: it leaves the conversation open, and Overdesk assigns it to the person who keeps that promise. When your team has dealt with a conversation Overdesk left with it, add a note to the conversation to say so: Overdesk reads what your team wrote since. If Intercom doesn't confirm a reply Overdesk sent, Overdesk waits until someone on your team replies or adds a note in Intercom. A message a Workflow, Fin or another app posted doesn't count.

Inboxes, tags and escalation ​

  • In Allowed inboxes, enter all, or Intercom: and a team's id, such as Intercom:4120397, to limit Overdesk to the conversations that team holds. With a second help desk connected, write Intercom:all for every conversation. On Intercom the inbox is the conversation's team, so a number without Intercom: in front never names one.
  • Triage tags are added to the conversation, and Overdesk creates any tag your workspace does not have yet.
  • Escalation assigns the conversation to the teammate or team you chose for Intercom on the target. Intercom assigns a conversation to whoever replies, so the teammate your access token belongs to holds the conversations Overdesk replied to until Overdesk hands them on, and Overdesk does not count them as an owner who took it. Fin is not offered as a target. See Escalation.

Real-time updates ​

Intercom signs its webhooks with your app's "Client secret", which is on the app's "Basic information" page in the Developer Hub. To let your team ask @Overdesk in a note, subscribe the webhook to one more topic. The steps are in Real-time updates with webhooks.

If the connection is refused ​

The form shows the reason next to the field. A message starting "credentials rejected by Intercom" is followed by Intercom's own words; copy the token again from Configure, then Authentication, in your app. A message saying the Intercom subscription on this account is inactive means Intercom accepted the credentials but refuses every conversation read until the subscription is renewed, so renew it with Intercom and then connect again. A message starting "Overdesk could not read conversations with this token" means the credentials opened the account but Intercom then refused to list conversations; Intercom's own words follow it, so check the credentials' permissions.

Disconnecting Intercom deletes its credentials and everything it put into your knowledge base.