Skip to main content
Intercom is where most product-led and SaaS companies manage customer conversations - live chat, in-app messaging, proactive outreach, and support tickets. When DialNexa handles a phone call, it can create or update Intercom conversations, look up user context before the call starts, and write call outcomes back to the customer record - so your support and success teams have one unified view.
This integration is particularly valuable for SaaS and product companies where customers move between Intercom chat and phone support. DialNexa makes sure the context moves with them.

​
What this integration does

DialNexa connects to Intercom through its REST API. Before, during, or after a call, DialNexa can:
  • Look up the caller’s Intercom user profile - pulling in account details, subscription plan, recent conversations, and tags before the agent speaks
  • Create a new conversation in Intercom with the call summary and outcome
  • Add notes to an existing conversation when the call is a follow-up to an open Intercom thread
  • Update user attributes - custom data fields, tags, segments based on what was said on the call
  • Send Intercom messages to the user after the call (in-app or email) as a follow-up
  • Tag users based on call outcome - churned, expanded, escalated, NPS risk, and so on

​
When to use DialNexa with Intercom

SaaS support escalations - a customer raises an issue in Intercom chat that gets complex enough to warrant a call. DialNexa calls them, resolves or escalates, and writes the outcome back to the Intercom conversation - closing the loop without losing the thread. Proactive customer success outreach - your CS team uses Intercom to track health scores and engagement. DialNexa calls users who show low engagement, at-risk behavior, or are approaching renewal - and writes conversation notes back to their Intercom profile. Product onboarding calls - new users who haven’t completed onboarding get a call from DialNexa. The agent walks them through setup, captures blockers, and tags the user in Intercom accordingly. Follow-up messages can be triggered automatically. Inbound inquiry routing - when a prospect fills out a form or starts a chat, DialNexa calls them back immediately. The Intercom conversation notes what the caller asked and what the next step is - giving the sales or support team full context when they follow up. In-app support callbacks - users who request a callback through your Intercom widget trigger a DialNexa call. The agent has their profile loaded before the call starts, and the Intercom conversation gets updated with the resolution.

​
What DialNexa does with Intercom

User lookup

Pull the caller’s Intercom profile - plan, recent activity, open conversations, and tags - before the agent starts talking, so the call feels personal and informed.

Conversation creation

Creates a new Intercom conversation with the call summary, giving support and success teams a written record of what happened on the phone.

User attribute updates

Update custom data fields - call date, call outcome, retention risk score, upsell interest - so your Intercom segments and automations stay accurate.

Tags and segments

Tag users based on call outcome so Intercom can trigger the right follow-up messages, sequences, or alerts automatically.

​
Setting up the integration

In your DialNexa agent workflow, add Intercom actions at the right points:
  1. Pre-call lookup - before the call starts, look up the caller’s Intercom profile using their phone number. The agent gets account context before saying hello.
  2. Post-call update - after the call ends, create a conversation note or update user attributes with call outcome data
  3. Intercom API connection - your Intercom access token (set up once in DialNexa integrations)
  4. Field mappings - which DialNexa variables write to which Intercom user attributes
  5. Tag logic - which call outcomes trigger which Intercom tags

​
Workflow ideas

A customer is in an Intercom chat with a support rep. The issue gets complex - the rep decides to call. DialNexa calls the customer and the agent already knows everything from the chat thread. After the call, a note is added to the Intercom conversation with the resolution. The customer never has to repeat their story.
Intercom data shows a customer’s engagement has dropped - fewer logins, fewer actions, silence. Your workflow triggers a DialNexa call. The agent checks in, captures why engagement has dropped, and writes the outcome to the customer’s Intercom profile. The CS team gets tagged in if escalation is needed.
New users who haven’t completed key onboarding steps after 7 days get a DialNexa call. The agent walks them through the stuck point, captures what’s blocking them, and tags their Intercom profile with the blocker category. Your product team gets aggregated data on where users are getting stuck.
When a renewal call is scheduled, DialNexa pulls the customer’s Intercom profile - support history, feature usage, recent conversations - and surfaces it to the CS rep. After the call, the Intercom profile is updated with renewal intent, expansion interest, or at-risk flags.

​
Pairing Intercom with other integrations

  • Intercom + Slack - when a call reveals a churn risk or escalation, fire a Slack alert to the CS channel with the Intercom conversation link
  • Intercom + HubSpot - sync call outcomes between Intercom user attributes and HubSpot contact properties so both sales and support have the same picture
  • Intercom + Salesforce - write Intercom conversation notes into Salesforce Account activity for enterprise accounts where sales and support need to be in sync
  • Intercom + Zendesk - when a phone call generates a support ticket in Zendesk, link it back to the Intercom conversation for full channel history
  • Intercom + Gmail - after a call where a follow-up was promised, DialNexa sends the email and logs it as an Intercom conversation event

​
Common questions

DialNexa searches Intercom by the caller’s phone number. If the number is stored on the Intercom user record, the profile is returned before the call starts. If no match is found, the agent can capture the caller’s email to do a secondary lookup, or create a new user record at the end of the call.
You can configure DialNexa to send data to Intercom mid-call - for example, adding a note when an escalation is detected - but most teams configure post-call updates after the full conversation is captured.
Yes, indirectly. By tagging the user or updating custom attributes in Intercom after the call, you can trigger Intercom outbound messages or series sequences based on those tags. For example, tag the user as “onboarding-blocked” and trigger an Intercom message series with helpful resources.
A structured summary of the call - caller name, date, duration, outcome, key points discussed, and what the next step is. The full DialNexa transcript and recording link are also included so anyone reading the conversation has complete context.
Yes. The same integration can serve both use cases - support teams use it to close the loop on escalated calls, while sales teams use it to log prospect conversations and trigger follow-up sequences. You configure separate actions in separate DialNexa workflows.