The real question is who owns the customer touch
Intercom and PostHog Workflows can both send a message to a user who did something in your product. That is where teams get confused. The better question is: which team is sending it, and what should happen when the user replies?
If a support or success person should be able to answer, the message belongs in Intercom. Every reply lands in the Intercom inbox with the conversation history attached.
If the message is an automated reaction to product behavior, and a reply is not the point, PostHog Workflows is often the simpler place. The trigger is already a PostHog event or cohort.
What Intercom is built for
Intercom is a customer service platform first. Its core pieces are:
- Messenger and live chat inside your app and website.
- A shared inbox and tickets for the support team.
- Fin AI Agent, which answers questions and resolves conversations, billed per outcome.
- Help center content that Fin and customers can use.
- Proactive messaging, including in-app chats, banners, and tooltips, plus outbound email, SMS, and WhatsApp on a pay-as-you-go basis.
Everything is organized around the user and their conversation history. That is valuable when support and success teams need context before they reply.
What PostHog Workflows is built for
PostHog Workflows is an automation layer inside PostHog analytics. The trigger is an event, a property change, or a cohort. The action can be an email or SMS, a Slack message, a webhook call, a property update, or an event pushed to a real-time destination. PostHog also offers in-app surveys as a separate product, but Workflows itself does not render in-app messages.
Its strength is precision on behavior. "Users on the Team plan who created a dashboard last week but have not shared one" is a cohort you already have. Turning that into a message takes minutes.
Pricing models compared
These tools bill for completely different things.
| PostHog Workflows | Intercom | |
|---|---|---|
| Base unit | Messages per channel | Support seats |
| Entry point | 10,000 messages per channel free each month | Essential at $29 per seat per month |
| Higher tiers | Per-message usage pricing | Advanced $85, Expert $132 per seat per month |
| AI | Not applicable | Fin at $0.99 per outcome |
| Outbound channels | Included in message pricing | Email campaigns, SMS, WhatsApp pay-as-you-go |
| Add-ons | None listed for Workflows | Proactive Support Plus $99/month with 500 messages, Copilot per agent |
Intercom costs scale with your support team and AI usage. PostHog Workflows costs scale with message volume. If you have ten support agents and only need a few product nudges, routing those nudges through Intercom means paying for a platform sized around support.
Pricing reality for a five-person support team
Take a B2B SaaS with five support agents on Intercom Advanced, Fin resolving 300 conversations a month, and a product team that wants to send about 4,000 onboarding and activation emails a month.
| Line | Intercom | PostHog Workflows |
|---|---|---|
| Seats | 5 x $85 = $425 per month | Not applicable |
| AI resolutions | 300 x $0.99 = $297 per month | Not applicable |
| 4,000 outbound emails | Pay-as-you-go on top | Inside the 10,000 free email messages |
| Proactive add-on if needed | Proactive Support Plus $99 per month, 500 messages included | Not applicable |
Those figures come from Intercom's listed rates in our pricing notes. The support cost is justified by the inbox and Fin. The question is only whether outbound product email should ride on that platform too, or run where the product data already lives.
Users, leads, and identity matching
Intercom separates leads, who are anonymous or unidentified visitors, from users, who are identified with a user ID or email. PostHog separates anonymous persons from identified ones and merges them when you call identify.
Use the same user ID in both tools, set at login. The PostHog Intercom destination can then update the right Intercom user with product properties, and conversations stay attached to one person. If IDs differ, you get duplicate users in Intercom, agents see stale plan data, and in-app messages target the wrong audience. Test with internal accounts first, and send only the properties agents actually use, such as plan, seat count, and last active date.
A working split for SaaS teams
Many teams run both. A split that avoids overlap:
- PostHog captures product behavior, defines cohorts, and runs internal automation: alert customer success in Slack when a key account's usage drops, call a webhook when a trial crosses a threshold.
- Intercom receives the product properties it needs through PostHog's Intercom destination, so agents see plan, activation status, and recent activity in each conversation. It shows in-app banners and tooltips, and runs chat and Fin.
- Customer email goes to one owner. If it stays in Intercom or PostHog Workflows, pick one, so users do not get the same nudge twice.
Migration notes
Moving outbound messages from Intercom to PostHog Workflows makes sense when those messages were really product nudges and Intercom outbound costs are adding up. Rebuild Intercom audience rules as PostHog cohorts, recreate the emails as workflow steps, authenticate your sending domain in PostHog, and carry over unsubscribes. In-app banners and tooltips cannot move, because PostHog Workflows does not render them.
Moving product alerts from PostHog into Intercom rarely makes sense. Intercom is not built to act on detailed analytics cohorts or to call arbitrary webhooks, so keep those in PostHog.
Use-case matchups
| Need | Better fit | Why |
|---|---|---|
| Tooltip guiding users to a new feature | Intercom | In-app tooltips and banners |
| Email when a user stalls in setup | PostHog Workflows | Trigger is an existing cohort |
| Answer "how do I export?" at 2 a.m. | Intercom | Fin and help center |
| Slack alert when a key account's usage falls | PostHog Workflows | Native Slack step on product data |
| Agent sees plan and usage in a chat | Intercom with PostHog destination | Properties on the Intercom user |
| Failed payment and trial ending email | Sequenzy | Stripe-aware lifecycle email |
Three common scenarios
A developer tool with no support team. Founders answer support email themselves. Intercom's seat-based platform and Fin are more than you need. PostHog Workflows can handle onboarding nudges and usage alerts, and a simple shared inbox covers support.
A B2B SaaS with a five-person support team. Chat is part of the product experience, and agents need to see plan and usage in every conversation. Intercom is the right hub for support. Send PostHog properties to Intercom through the destination, keep internal alerts in PostHog Workflows, and decide which tool owns outbound email.
A product-led SaaS scaling self-serve. Support volume is climbing, so Fin and the help center save real time. At the same time, lifecycle email is growing into onboarding tracks, trial conversion, and billing messages. Intercom handles the conversations, PostHog handles the analytics, and a dedicated email tool handles the lifecycle program.
Decision checklist
- Is chat support part of your product experience? Yes means Intercom belongs in the stack.
- Should replies reach a human? Send those messages from Intercom.
- Is the trigger detailed product behavior? Define it in PostHog.
- How many support seats do you pay for? More seats make Intercom a costly place for outbound email alone.
- Do you need in-app banners or tooltips? Intercom renders them. PostHog Workflows does not.
Where Sequenzy fits
Sequenzy does not do live chat, in-app messaging, or support, so it does not replace Intercom. It also does not replace PostHog analytics. It covers the email program that neither tool is built to own: onboarding sequences, activation, trial conversion, product updates, failed payment recovery, and transactional email, with Stripe connected for billing triggers.
Pricing is by emails sent with unlimited contacts, not seats. The comparison plan at 10,000 contacts is $49/month for 60k emails (unlimited subscribers).
Bottom line
Use Intercom for conversations and in-app guidance. Use PostHog Workflows for automated reactions to product behavior and internal alerts. When lifecycle and billing email need a real home, give them one in Sequenzy rather than stretching a support tool or an analytics workflow to fit.
