WhatsApp Intercom Integration: Complete Setup Guide (2026)

Intercom is the gold standard for SaaS customer support and in-product messaging. WhatsApp is where your customers actually are. Connecting the two creates a unified support experience: your team works in one inbox, your customers reach you through their preferred channel, and every conversation is automatically logged, tagged, and linked to the right contact record.

In 2026, the WhatsApp + Intercom combination powers support operations at hundreds of SaaS companies, e-commerce brands, and service businesses worldwide. This guide covers every integration approach — from native Intercom WhatsApp to Zapier/Make automation to ChatDaddy's native webhook — and helps you choose the right setup for your team's needs.

ChatDaddy helps over 23,500 businesses process more than 10 million WhatsApp messages daily. Here is how to connect it with Intercom.

1. Why Integrate WhatsApp with Intercom?

Without integration, WhatsApp and Intercom operate as siloed channels. Your support agents switch between two platforms, manually copy customer information between systems, and inevitably miss context. A customer who complained on WhatsApp yesterday contacts your Intercom chat today — and your agent has no idea about the prior conversation.

Integration solves this by establishing a bidirectional data flow:

• WhatsApp messages appear in your Intercom inbox alongside web chat conversations
• New WhatsApp contacts are automatically created as Intercom contacts with their phone number and conversation history
• Intercom's automation rules, SLA timers, and tagging workflows apply to WhatsApp conversations
• Agents can see a customer's complete history (both channels) in one unified contact record
• Intercom reports include WhatsApp conversation volume, resolution time, and CSAT scores

For support teams, this integration also enables an important operational model: WhatsApp as the high-touch, personal channel for complex or escalated issues, and Intercom web chat as the self-serve first-response layer. Together, they cover every customer preference.

2. Three Integration Approaches Compared

The right approach depends on your existing tools, technical capacity, and message volume. Each is covered in detail below.

3. Option 1: Native Intercom WhatsApp Integration

Intercom offers a native WhatsApp channel integration for customers on certain plan tiers. This is the simplest path if you are already paying for Intercom at the right tier.

How Native Intercom WhatsApp Works

Intercom connects directly to the WhatsApp Business API through Meta's approved infrastructure. Once connected:

• Inbound WhatsApp messages appear in your Intercom inbox as conversations, indistinguishable from web chat messages in terms of workflow
• Agents can reply to WhatsApp messages from within Intercom
• Intercom's automation rules (assignment rules, bots, SLA timers) apply to WhatsApp conversations
• Contact records in Intercom include the customer's WhatsApp conversation history

Limitations of Native Integration

The native approach has notable constraints:

• Requires Intercom's higher-tier plans — not available on Starter
• Limited broadcast/outbound messaging capabilities compared to dedicated WhatsApp platforms
• No multi-number support — one WhatsApp number per workspace
• WhatsApp-specific features like bulk broadcasts, chatbot flows, and coexistence mode are not available
• Message template creation and management must be handled through Meta Business Manager separately

For teams that primarily need inbound support through WhatsApp and are already on Intercom, native integration is a reasonable starting point. For teams that want full WhatsApp capabilities — outbound campaigns, automation flows, shared inbox, broadcasts — the ChatDaddy + Intercom approach is more powerful.

4. Option 2: Zapier or Make (Integromat) Bridge

For teams that want a code-free integration between WhatsApp (via ChatDaddy) and Intercom, Zapier and Make provide pre-built automation platforms that connect the two systems through triggers and actions.

Common Zapier Workflows for WhatsApp + Intercom

• New WhatsApp contact → Create Intercom contact: When a new contact messages your WhatsApp number, automatically create or update their record in Intercom
• WhatsApp message received → Create Intercom conversation: Log incoming WhatsApp messages as new conversations in Intercom with the full message text
• Intercom conversation closed → Send WhatsApp follow-up: Trigger a WhatsApp CSAT or follow-up message when an Intercom conversation is resolved
• WhatsApp keyword triggered → Add Intercom tag: When a customer sends a specific keyword on WhatsApp (e.g., "urgent"), automatically tag their Intercom record for priority handling

Setting Up the Zapier Integration

The basic setup requires: a ChatDaddy account with API access, an Intercom account with API access, and a Zapier account. In Zapier, select ChatDaddy as the trigger app (new message, new contact) and Intercom as the action app (create contact, create conversation, add tag). Most workflows can be built without code in under 30 minutes.

Make (Integromat) for Complex Workflows

Make offers more sophisticated workflow logic than Zapier — useful for conditional routing (e.g., if WhatsApp message contains "invoice", create an Intercom ticket with billing tag and assign to billing team). Make also handles higher webhook volumes more cost-effectively for teams with large message throughput.

5. Option 3: ChatDaddy + Intercom via Webhooks

For teams with developer resources, direct webhook integration offers the most powerful and reliable WhatsApp + Intercom connection. Here is how to set it up:

Step 1: Configure ChatDaddy Webhooks

In your ChatDaddy dashboard, navigate to Settings → Webhooks. Create a new webhook and select the events you want to sync: new inbound message, new contact created, message delivered, message read, conversation assigned. Enter your middleware endpoint URL (a simple server or serverless function that receives ChatDaddy events and calls the Intercom API).

Step 2: Map ChatDaddy Events to Intercom API Calls

When ChatDaddy fires a "new_message" event, your middleware should:

1. Check if the sender's phone number exists in Intercom (search contacts by phone)
2. If not found: create a new Intercom contact with the phone number, WhatsApp name, and any available profile data
3. Create a new Intercom conversation (or find the existing open conversation for this contact) and add the message as a note or reply
4. Apply appropriate tags and routing rules based on message content or source

Step 3: Bidirectional Sync for Replies

To enable replies from Intercom to reach WhatsApp, configure an Intercom webhook that fires when an agent sends a reply. Your middleware receives this event and calls the ChatDaddy API to send the reply as a WhatsApp message to the customer. This creates a seamless bidirectional flow where agents never need to leave Intercom.

6. Auto-Creating Intercom Contacts from WhatsApp Leads

One of the highest-value automation flows is automatically creating Intercom contacts whenever a new customer messages your WhatsApp number. This ensures every WhatsApp lead is captured in your customer database with no manual data entry.

What Data to Sync

• Phone number: The WhatsApp sender's phone number becomes the Intercom contact's primary identifier
• Display name: The WhatsApp profile name is mapped to the Intercom contact name
• First message: The content of the first WhatsApp message is logged as the first event in the Intercom contact timeline
• Source tag: Tag the Intercom contact with "whatsapp_lead" for segmentation and reporting
• Lead source: If using Click-to-WhatsApp ads, pass the ad campaign source as a custom attribute in Intercom

With ChatDaddy's contact management, you can also enrich WhatsApp contacts with custom fields (company name, deal value, product interest) that sync to Intercom, giving your support agents full context before they even read the first message.

7. Syncing WhatsApp Conversation History to Intercom

Conversation history sync is critical for support continuity. When a customer contacts your Intercom chat after previously messaging on WhatsApp, your agent needs to see both conversations in context.

Approaches to Conversation History Sync

Real-time sync: Every WhatsApp message is forwarded to Intercom as it arrives, creating a running log in the Intercom conversation timeline. This is the most complete approach but requires webhook infrastructure or a Zapier/Make workflow.

Session sync: At the end of each WhatsApp conversation session, a summary or full transcript is posted to the Intercom contact's notes. Less granular but simpler to implement.

On-demand lookup: Agents in Intercom see a link to the corresponding ChatDaddy conversation for full WhatsApp history, rather than duplicating the content. This works well when storage efficiency matters.

Customer Identity Resolution

The technical challenge in conversation sync is matching a WhatsApp contact (identified by phone number) to an Intercom contact (identified by email or user ID). The recommended approach is to use phone number as the matching key in Intercom: always store the WhatsApp phone number in the Intercom contact record, then use phone number lookup when syncing new WhatsApp events.

8. Triggering Intercom Workflows from WhatsApp Events

Beyond conversation sync, the WhatsApp + Intercom integration enables powerful event-triggered workflows. WhatsApp events can trigger Intercom automations, and Intercom events can trigger WhatsApp messages.

WhatsApp Events That Can Trigger Intercom Workflows

• Customer opts in via WhatsApp: Trigger Intercom onboarding series
• Customer sends "urgent" keyword: Escalate to priority queue in Intercom
• WhatsApp conversation unresolved for 4 hours: Create Intercom ticket for manager review
• Customer completes WhatsApp chatbot flow: Update Intercom contact lifecycle stage
• Customer churns (WhatsApp opt-out): Trigger Intercom win-back sequence via email

Intercom Events That Can Trigger WhatsApp Messages

• Intercom conversation resolved: Send WhatsApp CSAT survey
• Customer goes inactive in Intercom: Send WhatsApp re-engagement message
• New feature announcement: Trigger WhatsApp broadcast to opted-in users
• Trial expiration approaching: Send WhatsApp reminder with upgrade link

9. Real-World Use Case: Dual-Channel Support Team

A B2B SaaS company with 50+ support agents uses Intercom as its primary support platform and WhatsApp as a dedicated high-touch channel for enterprise customers. Here is how the integration works in practice.

The company's enterprise customers (5%+ of their customer base, 40%+ of revenue) prefer WhatsApp for urgent issues because it feels more immediate and personal than filing a support ticket. The support team needed WhatsApp to be a first-class citizen in their Intercom workflow without creating a separate support operation.

Their Setup

ChatDaddy handles all WhatsApp operations: inbound message routing, automated first responses with expected wait times, and escalation to human agents. Webhooks sync all WhatsApp conversations to Intercom in real time. Support agents assigned to enterprise accounts work exclusively in Intercom but see WhatsApp conversations alongside their other tickets.

Results

• First response time on WhatsApp dropped from 47 minutes to under 8 minutes after integration
• Enterprise CSAT increased from 87% to 94% within 3 months of launching the integrated channel
• Agent context-switching between platforms was eliminated — saving an estimated 2.5 hours per agent per week
• WhatsApp conversation volume grew 340% in 6 months as enterprise customers discovered the channel and adopted it as their preferred support method

10. Frequently Asked Questions