Intercom on Oliver POS

The Intercom for WooCommerce app maps WooCommerce customers, orders, and order events into Intercom contacts and custom attributes. When an agent opens a conversation, the right rail shows the matched WooCommerce contact — name, email, phone, lifetime order count, average order value, the most recent orders with line items and totals, refund history, and customer notes. Intercom custom attributes are populated from WooCommerce fields, so segmentation rules, automations, and Fin AI's knowledge base can branch on real purchase data.

The Messenger widget on the storefront sees the same data for logged-in shoppers, which means a customer DMing from the product page gets a Fin reply or an agent response that already knows their order history. On the agent side, the conversation panel exposes a click-through into the WooCommerce order admin and (on supported connector versions) the ability to issue a refund back to WooCommerce from inside the Intercom inbox. Oliver POS writes register sales into WooCommerce as standard orders matched to the same customer object, so those sales appear in the Intercom sidebar identically to online orders, and Fin's context window for the conversation includes the in-store activity automatically.

Intercom's value proposition is conversational support that feels personal — the storefront chat opens with the customer's name, Fin answers with knowledge of what they've bought, agents reply with full context. That promise breaks for omnichannel retailers the moment the customer's most-recent or most-relevant purchase happened at the counter. Fin doesn't know about the in-store sale, so it falls back to generic answers or asks the customer for the receipt. The agent picks up a Fin-escalated ticket with no useful sidebar context and has to bounce out to the POS to figure out what the customer bought.

For DTC brands moving into physical retail, this is the single sharpest pain point Intercom users feel. The team chose Intercom because Messenger and Fin let them scale support without growing the agent count linearly; the value of that automation collapses if the AI doesn't see half of what the customer bought.

Oliver POS writes the counter sale into the WooCommerce customer record the Intercom app reads. The contact attributes — lifetime order count, average order value, last order date, last order total — update with in-store activity in real time. Fin's suggestion engine sees those updated attributes the next time the customer opens Messenger; agents see the in-store order in the sidebar from the first message. The Intercom workflow the brand built — Messenger, Fin, automations — actually works on the cross-channel customer the brand has been promising to serve.

At the counter the cashier rings the sale on Oliver POS, captures the customer at tender by email or phone — matched against the existing WooCommerce customer base, or created fresh if it's a new walk-in. Oliver writes the WooCommerce order with line items, taxes, payment method, the created_via=pos meta flag, and a per-outlet tag identifying the store. Refunds at the register write standard WooCommerce refund actions tied to the original order.

When the customer opens Messenger on the storefront, DMs from Instagram or WhatsApp, or emails support, the conversation lands in the Intercom inbox. Intercom matches it to the WooCommerce contact, updates the custom attributes from the recent purchase data, and renders the order-history widget in the conversation panel. The Oliver-written orders sit in the same list as online orders, with the same line items and the same refund-action button. Fin's suggested replies and knowledge-base answers branch on the updated attributes, so a customer messaging about an in-store purchase gets a Fin response that actually knows about the in-store purchase. The agent — when one is needed — sees the same data and (where the connector supports it) issues a refund back to WooCommerce from inside the conversation, which syncs down to Oliver on the next register sync.

Intercom segments, automations, and outbound message campaigns can filter on the created_via=pos meta or the per-outlet tag — so a follow-up message after an in-store purchase, a post-visit NPS, or a regional store-specific announcement can target only customers whose most recent sale came from the relevant outlet.

Intercom on Oliver POS suits DTC and digitally-native brands with one to a few dozen retail outlets, a support strategy that leans on Messenger and Fin to scale beyond linear agent growth, and customer interactions split across web chat, social DM, email, and storefront in-person. Apparel, footwear, beauty, lifestyle, premium grocery, and similar brands fit this profile most often. The biggest gains land for teams where Fin currently can't answer counter-purchase questions because the in-store sale isn't in the customer object. Oliver removes that blind spot — the in-store activity becomes part of the same WooCommerce contact Fin and the agents already read, and the Intercom workflow finally covers every channel the brand sells through.