Apr 2, 2025

Intercom importer

We’re excited to announce the release of our Intercom importer – which allows you to sync or migrate your customer data to Plain in just a few clicks.

When you run an Intercom import, we bring in:

  • Contacts → Customers: All Intercom contacts are imported as customers in Plain.

  • Conversations → Threads: All conversation types – chat, email, and more – are imported as threads.

After the initial migration has taken place, any new contacts, admins, or conversations will automatically be synced to Plain. 

To run an import, head to Settings → Integrations → Intercom and follow the prompts to connect your Intercom account. Check out our docs for full setup instructions.

What's new

  • You can now change the logo of your Plain Slack bot to the logo of your company (previously, it had to be the Plain logo) that appears:

    • In the chat widget (if you don't set one for the chat app).

    • Inside the Plain web app.

    • On unread chat messages emails (if you don't have a chat app logo).

    • On the autoresponder messages in Slack.

Improvements

  • Improved search indexing – you can now find threads by searching company name, domain, and Slack channel name.

  • You can now exit the image preview modal by clicking outside of it, instead of having to find the “X”.

  • Merged display options for 'Jira issues' and 'Linear issues' into 'Linked issues' and added support for Shortcut Stories.

  • Added support for filtering threads by “created at” date.

  • Added a security check when attempting to enable a Slack channel that's in multiple slack workspaces - we now verify that the user is in the channel first.

  • Added a warning to the chat settings page when you have chat notifications enabled but no email settings, as this will result in customer replies to emails being lost.

  • The authentication screen for our chat widget now disables the button when less than three characters are entered in the name field.

  • Fixed UI copy for thread field created/updated/deleted to correctly state that it’s triggered per workspace, not per thread.

Designed, built and written by

David Leyland

Engineering