Intercom Customer Messaging

VerifiedCaution

Integrate Intercom for customer messaging, support, and onboarding.

Sby Skills Guide Bot
DevelopmentIntermediate
7/24/2026
Claude CodeCursorWindsurfCopilotCodex
#intercom#customer-support#in-app-messaging#onboarding#chat-widget

Recommended for

Automated summary

Walks through integrating the Intercom Messenger and REST API into a web app, covering user boot and update, event tracking, a React provider, and server-side contact and message creation.

Strengths

  • Offers copy-ready snippets for Messenger boot, SPA updates, and event tracking.
  • Provides a React provider that loads the widget and boots it with the authenticated user.
  • Demonstrates server-side calls to the Contacts and Messages endpoints with custom attributes for segmentation.

Limitations

  • Help center, product tours, chatbots, and ticketing are only mentioned, with no implementation code.
  • Compatibility lists iOS and Android, but every example targets web/React and TypeScript.
When to use it

Use when adding an Intercom chat widget, identifying users, or creating contacts and sending messages from your backend.

When not to use it

Avoid if you need a free or open-source support stack, or detailed guidance on help center, tours, or ticketing setup.

Security analysis

Caution
Quality score78/100

The skill performs legitimate Intercom integration using standard network APIs and a third-party widget. There is no destructive, exfiltrating, or obfuscated behavior, but it handles a server-side secret token and injects a remote script, so a caution rating is appropriate.

Findings
  • •Injects a third-party Intercom widget script from widget.intercom.io into the page, which expands the client-side attack surface.
  • •Server-side examples require INTERCOM_ACCESS_TOKEN; the skill should emphasize that this secret must never be exposed client-side.
  • •React example uses script.innerHTML to inject a script block, which is fragile and may conflict with CSP or be mistaken for an XSS pattern.
  • •Example code contains placeholder values (admin_id, user_id, user@example.com) that must be replaced and validated.
How this analysis is made

Examples

Add messenger to Next.js
Add the Intercom messenger to my Next.js app and identify logged-in users with their plan and MRR as custom attributes.
Server-side contact and message
Write a server-side function that creates or updates an Intercom contact and then sends that user an in-app message.
Track onboarding event
Track a completed-onboarding event in Intercom when a user finishes my onboarding flow, including plan and team size.

name: intercom description: >- Add customer messaging and support with Intercom. Use when a user asks to add in-app messaging, build a help center, set up customer onboarding flows, create product tours, or implement a support ticketing system. license: Apache-2.0 compatibility: 'Any web app, iOS, Android' metadata: author: terminal-skills version: 1.0.0 category: business tags: - intercom - chat - support - onboarding - messaging

Intercom

Overview

Intercom is a customer messaging platform for support, onboarding, and engagement. Includes live chat, help center, product tours, chatbots, and a shared inbox. Industry standard for SaaS customer communication.

Instructions

Step 1: Install Messenger

// lib/intercom.ts — Initialize Intercom in a web app
export function initIntercom(user?: { id: string; email: string; name: string }) {
  window.Intercom('boot', {
    app_id: process.env.NEXT_PUBLIC_INTERCOM_APP_ID,
    ...(user && {
      user_id: user.id,
      email: user.email,
      name: user.name,
      created_at: Math.floor(Date.now() / 1000),
    }),
  })
}

// Update when user navigates (SPA)
window.Intercom('update', { last_request_at: Math.floor(Date.now() / 1000) })

// Track events for targeting
window.Intercom('trackEvent', 'completed-onboarding', {
  plan: 'pro',
  team_size: 5,
})

Step 2: React Component

// components/IntercomProvider.tsx — React wrapper
'use client'
import { useEffect } from 'react'
import { useUser } from '@/hooks/useUser'

export function IntercomProvider({ children }) {
  const { user } = useUser()

  useEffect(() => {
    // Load Intercom script
    const script = document.createElement('script')
    script.innerHTML = `(function(){var w=window;var ic=w.Intercom;if(typeof ic==="function"){ic('reattach_activator');ic('update',w.intercomSettings);}else{var d=document;var i=function(){i.c(arguments);};i.q=[];i.c=function(args){i.q.push(args);};w.Intercom=i;var l=function(){var s=d.createElement('script');s.type='text/javascript';s.async=true;s.src='https://widget.intercom.io/widget/${process.env.NEXT_PUBLIC_INTERCOM_APP_ID}';var x=d.getElementsByTagName('script')[0];x.parentNode.insertBefore(s,x);};l();}})();`
    document.body.appendChild(script)

    if (user) {
      window.Intercom('boot', {
        app_id: process.env.NEXT_PUBLIC_INTERCOM_APP_ID,
        user_id: user.id,
        email: user.email,
        name: user.name,
      })
    }
  }, [user])

  return children
}

Step 3: Server-Side API

// lib/intercom-api.ts — Server-side Intercom operations
const INTERCOM_TOKEN = process.env.INTERCOM_ACCESS_TOKEN!

// Create or update a user
await fetch('https://api.intercom.io/contacts', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${INTERCOM_TOKEN}`,
  },
  body: JSON.stringify({
    role: 'user',
    external_id: userId,
    email: 'user@example.com',
    name: 'John Doe',
    custom_attributes: { plan: 'pro', mrr: 49, company_size: 10 },
  }),
})

// Send a message
await fetch('https://api.intercom.io/messages', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Bearer ${INTERCOM_TOKEN}`,
  },
  body: JSON.stringify({
    from: { type: 'admin', id: 'admin_id' },
    to: { type: 'user', id: 'user_id' },
    message_type: 'inapp',
    body: 'Hey! How are you finding the new dashboard?',
  }),
})

Guidelines

  • Intercom starts at $39/seat/month — expensive but full-featured.
  • Use custom attributes to segment users (plan, MRR, feature usage).
  • Product tours and onboarding flows reduce support tickets significantly.
  • For budget alternative, consider Crisp (free tier) or Chatwoot (open-source).

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/intercom-customer-messaging-mryiqi3a' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/intercom-customer-messaging-mryiqi3a/download' --output '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md.part' && mv '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md.part' '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: Any web app, iOS, Android

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && test -s '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/intercom' && cp -R '.skill-downloads/intercom-customer-messaging-mryiqi3a' '.claude/skills/intercom'

Cursor
test -f '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && test -s '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/intercom' && cp -R '.skill-downloads/intercom-customer-messaging-mryiqi3a' '.cursor/skills/intercom'

Codex
test -f '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && test -s '.skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/intercom' && cp -R '.skill-downloads/intercom-customer-messaging-mryiqi3a' '.agents/skills/intercom'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/intercom-customer-messaging-mryiqi3a'

openskills read 'intercom-customer-messaging-mryiqi3a'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/intercom-customer-messaging-mryiqi3a/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills