Sending WooCommerce orders to Intercom puts order lifecycle events on the contact timeline and attributes. Support and automations see what was purchased without pasting order numbers into chats by hand.
Sync Engine for Intercom pushes those events from your WordPress site. Connect with OAuth or an Access Token, sync users, then enable Woo order events. Each order is sent once, in the background, within Intercom’s normal API limits.
Why orders belong in Intercom
Your team already works in Intercom. Every hop to WooCommerce admin costs time:
- Slower first response while someone searches order history
- “Let me check your order” delays that train customers to repeat themselves
- Automations that never fire because the trigger event never arrived
- Refund conversations where the agent learns the bad news from the customer
WooCommerce stays the store. Sync Engine puts the order details on the Intercom contact, where the conversation already is.
What to send (event thinking)
Think in events, not nightly CSV dumps:
- Order created, order completed, and order refunded
- Each order event carries order id, status, total, currency, item count, shipping total, payment method, billing city, and billing country
- Product names and SKUs travel with cart, product-view, review, booking, and subscription events
- Tie every event to contact identity (email for guests; registered WordPress users stay linked)
- Derive metrics: LTV after refunds, total revenue, refunds, AOV, order count, items, first/last order, days since last order, average days between orders, category, payment method
- Segments: New · VIP (LTV ≥ 1000 or ≥ 10 orders) · At-Risk (>90 days) · Regular
Cart abandonment is next door. See abandoned cart events.
What support sees after orders sync
What changes for support:
- Last order amount and date visible when the conversation opens
- Refund already on the contact before the customer explains
- VIP segment changes which macros and which human answers
Automation ideas (Intercom-side)
Once the events exist, you can build in Intercom:
- Post-purchase onboarding Series keyed off order events
- High-AOV routing to senior agents
- Win-back when days-since-last-order crosses your threshold
You write the Series in Intercom. Sync Engine puts the order events on the contact those Series use.
Bad patterns
- Screenshotting orders into tickets
- CSV of yesterday’s orders uploaded “when we remember”
- A single Zap that misses refunds or status edge cases
- Dual-writing the same order attributes from Zapier and a plugin
Implementation with Sync Engine
Install from WordPress.org; connect with OAuth or an Access Token (connect guide).
Confirm User Sync works with a test customer before you turn on store events.
Enable Woo order and event sync under Events.
Confirm the Intercom contact shows the order details, then attach Series or Inbox rules in Intercom. Optionally enable Metrics and custom attribute mapping.
Store sync is HPOS compatible.
Plan details live on the WooCommerce Intercom plans page.
Related spokes
FAQ
Can Sync Engine send WooCommerce orders to Intercom?
Do I need Zapier?
Refunds too?
Subscriptions?
Is Messenger required?
Is this HPOS compatible?
Where can I see pricing?
Stop alt-tabbing to Woo mid-ticket
Install free, connect, then enable order events so every ticket shows purchase history.
Install free on WordPress.org