Support integration guide
Intercom + UbiGrowth workflows
Intercom is a customer messaging platform that owns in-product conversations, and is frequently used for both support and lead qualification. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Intercom part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a support workflow around Intercom with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Contact, Company, Conversation, Ticket, Article, Segment, and Event. Intercom distinguishes Leads from Users, and a Lead converts to a User when identified. Conversations started before identification stay attached to the Lead unless the merge happens, which splits the history.
Intercom is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Support integrations are usually justified with deflection metrics, which is the wrong starting point. The expensive part of a ticket is not the reply; it is the time an agent spends assembling context from Intercom, the CRM, the product, and the issue tracker before they can write anything useful.
The second cost is escalation. A ticket handed to another team without account context, history, and reproduction detail comes back as a question, and the customer waits through a round trip that added nothing.
You're likely here because
- Agents assemble customer context from several systems before replying
- Escalations arrive at other teams missing the detail they need
- Support tooling improvements never clear the engineering backlog
Record model
What a Intercom integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Intercom's.
Identity and matching
Intercom distinguishes Leads from Users, and a Lead converts to a User when identified. Conversations started before identification stay attached to the Lead unless the merge happens, which splits the history.
Start here
Read Conversations tagged as sales intent that never reached a rep, and route them with the product usage context Intercom already holds.
What this will not do
It will not separate support from sales. Intercom deliberately blends them; the routing decision has to be made explicitly in the workflow.
The constraint to plan around
Custom attributes are typed on first write, and a later write of a different type is rejected. An attribute created as a string during testing cannot become a number without recreation.
Build notes
What you actually have to reason about in Intercom.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| role (lead vs user) | conversations before identification attach to the lead and split the history |
| custom attribute type | typed on first write and immutable after; a later mismatched write is rejected |
| conversation state | open, closed, or snoozed, with snooze being a real workflow state |
| company id | the account grouping for B2B, which requires explicit association |
| updated_at | the sync cursor |
Authentication
OAuth or an access token per workspace, with regional hosting meaning US, EU, and AU workspaces use different endpoints. Using the wrong region reads as an authentication failure.
Events and delivery
Webhook topics per event type with signature verification. Conversation events are timely; contact events fire on any attribute change including your own writes.
Workflow
How the Intercom workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Pick up the ticket with context
The account, purchase, and prior-conversation context for a Intercom ticket is assembled before the agent starts writing.
Step 02
Triage against real priority
Tickets are grouped by issue type, account context, and age so the queue reflects what matters rather than arrival order.
Step 03
Draft with the human in the loop
A response is drafted from the assembled context and reviewed by the agent, who remains responsible for what the customer receives.
Step 04
Escalate with the history attached
Escalations carry account context, history, and reproduction detail into the receiving system, removing the clarification round trip.
Design decisions
The support decisions this connection forces.
Each of these has to be settled before the Intercom workflow is allowed to write anything.
Step 01
Define the escalation contract
Decide what an escalation leaving Intercom must include — account context, history, reproduction detail — so the receiving team does not have to ask.
Step 02
Keep the customer-facing boundary explicit
Context assembly, triage, and drafting can be automated well before automated replies are appropriate. Treat those as separate decisions.
Implementation path
How to implement the Intercom workflow.
- 01
Pick one high-volume issue type and map exactly which context an agent needs to resolve it.
- 02
Connect Intercom and the systems holding that context, at scopes limited to support use.
- 03
Build a triage or context surface in Launch and test it against recent real tickets rather than samples.
- 04
After sales-intent routing works, add the product-usage join so the reply references what the person actually did rather than only what they said.
Governance
Controls that matter.
Control 01
Customer-facing replies stay under human review; the workflow assembles and drafts rather than autonomously answering.
Control 02
Access exposes the customer context the workflow needs, not the whole account surface.
Control 03
Billing, refund, and account-change actions require explicit human authorization.
Failure modes
How a Intercom integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
A conversation history is split across two records.
Cause
The person contacted before identification, creating a lead that never merged into the user.
Fix
Merge lead into user on identification, and check for an existing lead before creating a user.
Symptom 02
Attribute writes are rejected.
Cause
The attribute was typed on first write and the new value has a different type.
Fix
Establish attribute types deliberately at design time; they cannot be changed afterwards.
Symptom 03
API calls fail authentication with a valid token.
Cause
The workspace is hosted in a different region than the endpoint used.
Fix
Resolve the regional endpoint from the workspace rather than defaulting.
What changes at scale
Rate limits are per app per workspace. Webhook-driven handling scales; polling conversations does not, particularly on high-volume support workspaces.
Examples
What a working Intercom workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Customer conversations
With Intercom connected, the account, purchase, and prior-conversation context relevant to a ticket is assembled before the agent starts, instead of across five open tabs.
Triage surface
A Launch-built queue view groups Intercom tickets by issue type, account value, and age — the view the team actually needs, without waiting for engineering capacity.
Limitations and considerations
What to validate before you depend on this.
- Custom attributes are typed on first write, and a later write of a different type is rejected. An attribute created as a string during testing cannot become a number without recreation.
- Replying to a conversation messages the customer immediately. Because leads and users are separate roles, a reply on the wrong object reaches nobody and appears sent.
- When support and sales need clean separation. Intercom deliberately blends them, so the routing decision has to be explicit in the workflow rather than inherited from the tool.
- This is not an autonomous customer-facing agent. Replies should stay under human review, particularly where the account or issue carries real consequences.
- Context quality depends on the systems behind Intercom. A stale CRM record produces a confident and wrong summary.
FAQ
Intercom integration questions.
What records does a Intercom integration actually work with?
The primary records are Contact, Company, Conversation, Ticket, Article, Segment, and Event. Intercom distinguishes Leads from Users, and a Lead converts to a User when identified. Conversations started before identification stay attached to the Lead unless the merge happens, which splits the history.
What should the first Intercom workflow be?
Read Conversations tagged as sales intent that never reached a rep, and route them with the product usage context Intercom already holds.
What will a Intercom integration not do?
It will not separate support from sales. Intercom deliberately blends them; the routing decision has to be made explicitly in the workflow.
What is the main constraint to plan around?
Custom attributes are typed on first write, and a later write of a different type is rejected. An attribute created as a string during testing cannot become a number without recreation.
What changes about a Intercom integration at scale?
Rate limits are per app per workspace. Webhook-driven handling scales; polling conversations does not, particularly on high-volume support workspaces.
How does authentication work for Intercom?
OAuth or an access token per workspace, with regional hosting meaning US, EU, and AU workspaces use different endpoints. Using the wrong region reads as an authentication failure.
Does Intercom support webhooks, and can they be trusted?
Webhook topics per event type with signature verification. Conversation events are timely; contact events fire on any attribute change including your own writes.
What is the risk of writing to Intercom?
Replying to a conversation messages the customer immediately. Because leads and users are separate roles, a reply on the wrong object reaches nobody and appears sent.
When is connecting Intercom the wrong call?
When support and sales need clean separation. Intercom deliberately blends them, so the routing decision has to be explicit in the workflow rather than inherited from the tool.
What should a Intercom integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Intercom to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Does this replace Intercom?
No. Intercom stays the system of record for conversations. The workflow layer sits around it for context assembly, triage, and connected escalation.
Will it reply to customers automatically?
Not by default, and not until the workflow has been proven. Context assembly and drafting are separate decisions from automated sending.
How do escalations improve?
The escalation carries its trigger, account context, and history into the receiving system, which removes the clarification round trip that usually costs the customer another day.
How this access is governed
What ARIA is allowed to do in Intercom, and who decides.
Connecting Intercom is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.