Intercom's automation is conversational routing and triggered messaging, not general business-process automation.
Workflows (formerly Custom Bots) let you build if/then chat automations that trigger on a visitor's page, attributes, or behavior -- qualifying a lead before a human sees it, guiding a user through setup steps, or triaging an incoming conversation to the right team or inbox based on keywords or user segment.
Series ties multiple Workflows together into a multi-step, multi-channel journey across chat, email, and push, triggered by events tracked through Intercom's JavaScript or mobile SDK -- what counts as a trigger depends entirely on what your app is actually sending Intercom as a tracked event or user attribute, since untracked events simply can't drive automation.
Ticket automation is separate: routing rules assign incoming tickets to teams or individual agents based on conditions, and SLAs can trigger reminders or escalations, but this ticket layer needs its own deliberate configuration -- it doesn't inherit the Workflow logic built for chat.
What Intercom automation doesn't do is generic cross-system orchestration; moving data into a CRM, notifying a rep in Slack outside Intercom's own Slack app, or triggering non-Intercom actions all run through the REST API and webhooks -- fired on events like conversation created, tagged, or closed -- rather than inside the Workflows builder itself.
How this actually gets built
- Chat-based lead qualification and support triage belongs in Workflows; anything crossing into email or push sequencing belongs in Series
- Ticket routing rules and SLA automation need their own configuration pass, separate from the chat Workflow logic
- Automation reaching outside Intercom -- CRM sync, custom alerting -- runs through the API and webhooks, not the visual builder
The Workflows and ticket-routing layers are genuinely capable for support and lifecycle messaging; the real limitation to plan around is that anything Intercom doesn't track as an event or attribute simply isn't available as a trigger.
Use cases
What you’ll implement with Intercom automation
- Cart abandonment and post-purchase follow-ups triggered by user actions, powered by Intercom rules.
- Tiered onboarding journeys that adapt to user behavior and product familiarity, orchestrated across channels with Intercom.
- Proactive health checks and reminder campaigns for subscription-based services, coordinated through Intercom automation.
- Internal operations alerts and handoffs that route customers to the right teams via Intercom workflows.
- Self-service nudges and knowledge base prompts that reduce live agent volume, using Intercom event data.
- Escalation paths that trigger human review when sentiment or risk thresholds are crossed, managed through Intercom.
- A/B tested message variants that refine timing and content, tracked within Intercom analytics.
- Data-driven segmentation that personalizes automation without compromising privacy via Intercom controls.
- Compliance-driven data routing that enforces consent and data retention policies in Intercom flows.
- Cross-product integrations where Intercom coordinates messaging across marketing, product, and support tools.
Intercom plays a critical role in every case, shaping how automation is designed, executed, and measured to deliver tangible value.