Intercom vs Kustomer for a retail support team

Compare Intercom and Kustomer around a retail support case, checking customer and order records, permitted actions, handovers and total upkeep.

For Intercom vs Kustomer, choose Intercom when your team wants a conversation-led helpdesk with multiple team inboxes and workflow routing. Choose Kustomer when a customer’s history and connected retail records must organise the support team’s work.

Both need authorised connections to change store data. A detailed customer timeline helps an agent understand a request, but the order system still decides whether a cancellation or refund succeeds.

Choose around customer context and team work

Intercom Advanced is a practical comparison point for a retailer with several support teams. Kustomer’s quoted customer-service platform is the comparison point when customer records and cross-channel history drive the proposal.

Intercom’s published plans put multiple team inboxes and the Workflows builder in Advanced. Essential covers the shared inbox and ticketing. Expert adds controls such as identity management and service level agreements. Fin AI Agent access is included, while outcomes and some messaging usage are charged separately. Unlimited Copilot assistance is a separate purchase.

Kustomer describes its platform as a customer-service platform and customer relationship management system, or CRM. Its customer-facing automation is Concierge. The current package list also names Envoy for human representatives and Architect for building and improving customer experiences. Treat those named capabilities as parts of the proposed configuration, with their usage and implementation terms recorded in the quote.

Intercom fits a retailer that wants conversation routing to structure service work and can maintain the connected automation. Kustomer fits a team that needs customer context across contacts and transactions, with an administrator responsible for that record model. Both cover multiple communication channels. Existing channel connections and the work to migrate their histories can outweigh a difference in the inbox interface.

The proposed support configurations

DecisionIntercom AdvancedKustomer quoted platform
Team organisationMultiple team inboxes with workflow routingCustomer context with conversation and task routing
Customer automationFin with configured Procedures and Data connectorsConcierge with configured procedures and tools
Staff assistanceCopilot, subject to its separate usage termsEnvoy, listed in current packages
Retail recordsConnected customer and order contextConnected orders in the customer timeline
Purchasing basisPublished plan plus usage and selected additionsTailored quote for the team’s setup

Kustomer’s pricing page lists these AI capabilities in its packages and directs buyers to tailored pricing. It also identifies implementation as an add-on and usage charges for voice, SMS and WhatsApp. Comparing an old seat-only price with Intercom Advanced would miss that purchasing structure.

Compare the same retail customer case

The same product question can become an order lookup and then an exception that needs an authorised action. The system must carry the customer’s identity across those changes in intent.

Consider a fictional retailer selling desk lamps. A customer first asks whether a lamp is dimmable. They then ask where their existing order is and request cancellation if it has not shipped. The sequence below is illustrative, with outcomes determined by the store records and permissions.

A product answer uses product information

For the dimming question, use the specification for the exact lamp variant. Store-authored help content can explain the compatible dimmer or bulb. A customer’s previous purchase does not establish the specification of the product currently being discussed.

Intercom’s Fin Procedures combine instructions with structured controls and connected actions. Kustomer’s Concierge documentation distinguishes knowledge sources from procedures and tools. In both configurations, the product answer must come from the selected source for that product. A connector is needed when the answer depends on live external data.

An order answer needs a verified customer and order

Intercom’s Shopify app links imported customers to their Shopify customer ID. That gives the agent a customer-and-order connection. For protected lookups, Intercom’s Data connector security guidance calls for authenticated access or another secure verification method. Access control in the connected system must prevent someone looking up another customer’s purchase.

Kustomer’s Shopify integration brings orders into the customer timeline. Its documentation explains that ongoing data sync follows order updates and that conflicting custom workflows can interfere with the app’s sync. A visible order card therefore needs a functioning connection behind it.

For the lamp order, match the store’s customer ID and order ID before returning private delivery information. Read fulfilment state from the order record and tracking events from the carrier connection. Keep the customer’s reported delay separate from a confirmed shipment event.

Kustomer’s customer timeline is useful here because staff can read the earlier contact beside the order context. Intercom’s connected record supports the same customer question through the conversation. The deciding issue is how much customer history your team needs to organise and maintain, alongside the required live lookup.

A cancellation needs a saved result

Kustomer documents Shopify cancellation and refund actions for human representatives. They require a synced order and the relevant permissions. Order state and payment conditions can make an action unavailable. These human controls do not establish that every Concierge automation has the same tools enabled.

An Intercom cancellation needs an authorised Data connector used by the configured Procedure. Kustomer Concierge likewise needs the appropriate tool and procedure, with verification before protected actions. The workflow must read the returned result before telling the customer that their order is cancelled.

If the lamp is already with the carrier, route the exception to a person under the store’s policy. Transfer the verified identity, order reference and cancellation request. Include the last observed fulfilment state and any attempted action. The next person needs to know whether the order changed before deciding what to do next.

A conversation marked resolved is a support record. The expected saved business record is the cancellation or refund in the store system, with its resulting status. That distinction prevents a reassuring message from being mistaken for a completed action.

Compare complete costs and maintenance

Use the same staffing and conversation workload for both proposals, then add the work required to keep customer records and automation correct.

For example, assume eight support staff handle 2,000 monthly conversations across email and storefront chat. Two warehouse staff help with delivery exceptions. Keep those fictional inputs constant, including the proportion of automated lookups and human handovers. The underlying ecommerce customer service requirements decide what each proposal must cover.

Intercom’s cost includes the selected Full seats, relevant collaboration access and metered Fin outcomes. Add channel usage and optional assistance or services. Kustomer’s tailored quote must cover the same human access and automation workload, including channel charges and implementation. Compare contract terms, billing currency and tax treatment before calculating a total.

The operational cost includes importing customer history and connecting retail systems. Assign an owner to identity mapping, then budget for policy updates and failed-sync investigation. A retailer with many disconnected customer records will spend more effort reconciling those records than a simple conversation count reveals.

Kustomer’s merge instructions describes permanently combining duplicate profiles. Merge permissions must sit with staff who can establish that the records belong to one person. An email enquiry and a separate phone contact are leads to investigate, not automatic proof of a match.

Keep customer-merge authority separate from permission to refund an order. Kustomer’s permission sets distinguish those capabilities. Intercom also controls teammate access by permission. A support agent’s platform access must not silently become unlimited store authority.

For recovery, retain both conversation activity and the store’s saved result. Kustomer’s conversation audit history identifies changes by business rules and workflows. Intercom’s connector guidance requires explicit failure handling in Procedures. After an uncertain cancellation response, inspect the order before retrying. A failed lookup must pass to a named team with enough context to continue.

Choose Intercom when the conversation-led helpdesk fits the way your service team works. Choose Kustomer when maintaining a customer-centred record justifies the integration and administration effort. The complete proposal must fund the people and connections that turn the customer’s request into a confirmed store action.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup