Free Starter Pack Before you start using Claude for Excel, apply these best practices
← All Integrations
Intercom Logo

Intercom + Go Fig

Customer Success

Connect Intercom to Go Fig for customer communication analytics and engagement insights.

Intercom sits between your customers and your product, chat conversations, in-app messages, help center articles, tours, and support tickets. That conversation volume is a leading indicator of churn, expansion, and cost-to-serve long before it shows up in billing. Go Fig pulls conversations, contacts, companies, admin activity, tags, segments, and custom attributes from Intercom into the Financial Intelligence Graph and joins them to MRR, contract tier, and revenue from your billing and accounting systems. Celeste can then answer the questions that matter to finance, cost-to-serve by plan, conversation volume trends for accounts that later downgraded or churned, first-response-time impact on retention, and which customer segments are quietly eating support capacity. The integration is read-only and respects Intercom's workspace boundaries so multi-workspace setups stay cleanly separated inside the FIG.

Key facts

API
Intercom REST API v2.10 or later
Workspaces
Multi-workspace supported, kept separate
Custom attributes
Contacts and companies, fully synced
Conversation history
Full backfill of closed conversations
Sync cadence
Hourly incremental, webhook-driven for new conversations

SOC 2 Type II ยท All integrations

What you can do with Intercom data in Go Fig

Cost-to-serve by plan and segment

Join Intercom conversation volume, handle time, and admin hours to MRR and plan tier from billing, so finance can see which segments are profitable at current support load and which plans are underpriced relative to support cost.

Churn leading indicators

Model conversation frequency, sentiment signals, and tag patterns (bug, cancellation, integration_issue) against downgrade and churn events to surface at-risk accounts 30 to 90 days before they leave.

Support staffing forecast

Forecast conversation volume from user growth and feature-release cadence, then layer in admin capacity to flag where coverage gaps will appear before they become SLA misses.

Data available from Intercom

Go Fig extracts and normalizes the following data from your Intercom account:

Conversations and conversation parts
Contacts (leads and users)
Companies
Admins (teammates)
Teams
Tags and tag taxonomy
Segments
Events (custom product events)
Help center articles and collections
Outbound messages and tours
Conversation ratings (CSAT)
Custom attributes on contacts and companies

How to connect Intercom

1

Authorize Go Fig in Intercom

From the Intercom developer hub, install the Go Fig app and approve read scopes on contacts, companies, conversations, admins, tags, and events. Multi-workspace organizations install per workspace, each workspace lands as an isolated tenant inside Go Fig.

2

Review tag taxonomy and custom attributes

Conversation tags are the primary axis for support analytics. Go Fig inventories your current tags (bug, billing, feature_request, cancellation, etc.) and flags low-volume or near-duplicate tags that hurt segmentation fidelity. Custom attributes on contacts and companies (plan, MRR, account_owner) sync as native columns.

3

Map admin groups to cost centers

Support admins map to teams, and teams map to cost centers in your accounting system (support, onboarding, customer success). This is the join that produces true cost-to-serve once handle time and admin hours are in the Financial Intelligence Graph.

4

Connect billing for revenue-weighted analysis

If Stripe, Chargebee, or your accounting system is connected, Go Fig joins Intercom companies to billing accounts on external_id or email domain. Once joined, every support metric can be weighted by MRR, ARR, or contract tier automatically.

Authentication: OAuth 2.0 with Intercom's app ecosystem or a workspace-scoped Access Token for single-workspace setups. We request read scopes on contacts, companies, conversations, admins, tags, segments, and events. Multi-workspace customers authorize Go Fig per workspace so data stays partitioned by workspace ID.

Common Questions About Intercom Integration

Does Go Fig sync conversation content or just metadata?

Both, with controls. Metadata (participants, tags, duration, response times, ratings) always syncs because it is required for support analytics. Full conversation body text syncs by default and can be disabled during setup if your data policy restricts storing conversation content outside Intercom. Even without body text, Celeste can still produce cost-to-serve, handle-time, and tag-volume analysis.

How does Go Fig handle Intercom's tag taxonomy?

Tags sync as both raw categorical values and as normalized groups. Go Fig's starter schema flags common tag sprawl (bug vs Bug vs BUG, or feature_request vs feature-request) and offers a mapping layer so analysis is resilient to tag naming drift. Celeste uses the normalized view for cross-period trend analysis and the raw view when you need fidelity to a specific admin's tagging.

Can Go Fig measure CSAT and satisfaction data against revenue?

Yes. Conversation ratings sync with the five-point Intercom scale plus any open-text feedback. Once joined to contract value and plan tier from billing, Celeste can surface CSAT trends for high-ARR accounts, rating distribution by plan, and correlation between CSAT and retention. This is one of the more common analyses VP CS and CFOs ask for jointly.

What about outbound messages, tours, and help center data?

Outbound message send, open, and click metrics sync per campaign. Product tour engagement syncs per tour step. Help center article views and helpfulness votes sync per article. All of this lives in the same schema as conversations, so you can analyze whether deflection content is actually reducing support load, and measure the ROI of the CS content team's work.

How does sync handle Intercom API rate limits?

Intercom enforces 10,000 requests per minute per workspace, which is generous. Go Fig uses webhooks for new and updated conversations (near real-time) and hourly incremental sync for everything else, anchored on updated_at. Backfills for historical conversations use the conversations search endpoint with pagination. Steady-state sync stays well under the rate ceiling even for workspaces handling thousands of conversations per day.

Ready to connect Intercom?

See how your Intercom data looks in Go Fig with a personalized demo.

Book a Demo