Markin + Intercom integration
In-app conversations as a decision surface.
What is a Intercom AI agent?
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 Markin reads
- Conversation history and resolution outcomes
- User attributes
What Markin writes back
- Attributes and events that trigger targeted conversations
How the connection works
| Pattern | What it means here |
|---|---|
| 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 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
- 01Read conversations, tags and response history.
- 02Read user and company attributes.
- 03Detect friction expressed in conversations.
- 04Write the decided action and reason as a user attribute.
- 05Trigger the matching in-app series.
- 06Suppress users whose expected value does not justify an interruption.
- 07Maintain a randomised holdout.
- 08Report incremental conversion and revenue per message.
Scope of work
The growth work behind Intercom
The list above is what Markin touches in Intercom. A connector is only the surface. Below is the work itself: what an analyst, a lifecycle manager, a data scientist and an experimentation lead would do between them, running continuously against your own data.
Read the estate
Normally a data engineer, once, then never refreshed.
- Track catalogue, pricing and plan changes as they happen.
- Flag data quality breaks that would make a decision unsafe.
Find where revenue is leaking
Normally a quarterly analyst deep dive.
- Spot product friction that correlates with downgrade and cancellation.
- Spot channels and campaigns spending into audiences that would have converted anyway.
Explain why
Normally a two-week investigation pulled off the roadmap.
- Show the counter-evidence, not only the supporting cut.
- Keep the query trail so an analyst can reproduce every number.
Write hypotheses worth funding
Normally a workshop, limited to the ideas in the room.
- Keep the full portfolio visible, including what was deliberately not funded.
- Write hypotheses continuously across marketing, product, pricing and technical health.
Decide per customer
Normally segment rules refreshed when someone has time.
- 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
Normally a ticket, then a slot in next month's calendar.
- 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
Normally argued about, rarely measured.
- 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
Normally nobody's job, so nothing is ever switched off.
- Keep personal data in your systems and act on it in place.
- Show the whole decision trail when legal, finance or an auditor asks.
Intercom questions
- 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.