---
title: Markin + Intercom
url: https://markin.ai/integrations/intercom
category: Support and contact centre
description: Connect Markin to Intercom: trigger in-app conversations only when the expected value clears the bar, and read the outcome back.
---

# Markin + Intercom

> In-app conversations as a decision surface.

**Job:** Message in-product only when the decision earns the interruption.

A Markin and Intercom setup reads conversations and product-qualified signals, then writes the decided action onto the user so Intercom messages and bots run on a decision rather than a static rule.

In-app messaging is cheap to send and expensive in attention. Arbitration keeps the surface useful instead of exhausting it.

## What can you ask Markin to do in Intercom?

- How do I decide which users get an in-app message?
- Can Intercom conversations feed a churn model?
- How do I reduce in-app message fatigue?
- How do I connect product usage to in-app messaging decisions?

## What Markin does in Intercom

- Read conversations, tags and response history.
- Read user and company attributes.
- Detect friction expressed in conversations.
- Write the decided action and reason as a user attribute.
- Trigger the matching in-app series.
- Suppress users whose expected value does not justify an interruption.
- Maintain a randomised holdout.
- Report incremental conversion and revenue per message.

## The growth work behind Intercom

### Read the estate

- Track catalogue, pricing and plan changes as they happen.
- Flag data quality breaks that would make a decision unsafe.

### Find where revenue is leaking

- Spot product friction that correlates with downgrade and cancellation.
- Spot channels and campaigns spending into audiences that would have converted anyway.

### Explain why

- Show the counter-evidence, not only the supporting cut.
- Keep the query trail so an analyst can reproduce every number.

### Write hypotheses worth funding

- Keep the full portfolio visible, including what was deliberately not funded.
- Write hypotheses continuously across marketing, product, pricing and technical health.

### Decide per customer

- Apply frequency caps, fatigue and quiet hours before anything is committed.
- Respect eligibility, consent, locale and channel preference.

### Execute in the tools you already run

- Trigger journeys and campaigns that your lifecycle team owns and can edit.
- Update audiences, lists and segments without hand-built rules.

### Prove it caused the revenue

- Hold back a randomised control group on every decision, not one global holdout.
- Read uplift in revenue per customer against that control.

### Retire, govern and hand over

- Keep personal data in your systems and act on it in place.
- Show the whole decision trail when legal, finance or an auditor asks.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **Triggered event.** Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.
- **Attribute write-back.** Markin writes the decision onto the customer profile; your existing journeys read it as an entry condition. Latency is the platform's sync interval.

## What Markin reads from Intercom

- Conversation history and resolution outcomes
- User attributes

## What Markin writes back

- Attributes and events that trigger targeted conversations

## Used together with

- [amplitude](https://markin.ai/integrations/amplitude)
- [segment](https://markin.ai/integrations/segment)
- [stripe](https://markin.ai/integrations/stripe)
- [hubspot](https://markin.ai/integrations/hubspot)
- [zendesk](https://markin.ai/integrations/zendesk)
- [web-and-mobile-sdk](https://markin.ai/integrations/web-and-mobile-sdk)

## Related

- [Solution: lifecycle-automation](https://markin.ai/solutions/lifecycle-automation)

## FAQ

**How does Markin connect to Intercom?**

Triggered event, Attribute write-back. Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.

**What does Markin read from Intercom?**

Conversation history and resolution outcomes; User attributes.

**What does Markin write back into Intercom?**

Attributes and events that trigger targeted conversations

**Do we have to move our data to Markin?**

No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.

**Does Markin replace our engagement platform or CDP?**

No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.

**What if the system we use is not listed?**

The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.

Source: https://markin.ai/integrations/intercom