# Store customer matches and orders

View store customer matches and their orders for the visitor you are assisting.

*Release 3.3 · operator, supervisor*

**Visitor details › CRM**

## What it is

The **CRM** tab shows commerce customer information and store orders for the selected visitor. It uses identifiers already held for that visitor and eligible linked-contact details. When several distinct customers match, you can choose which customer's information to inspect.

## Who uses it and why

Operators check customer context and order history while assisting a visitor. Supervisors with access to the visitor can inspect the same information when reviewing or helping with service.

## Where to find it

Select a visitor and open **CRM** in the visitor details panel. The tab is available when customer or order operations are configured for that visitor. Use **Refresh customer information** to request current information again.

## How it works

INSIDE starts with the visitor's primary email address, then eligible alternate email addresses on the linked contact. It removes invalid and duplicate addresses and considers at most five. When no eligible emails exist, it can use the visitor's available phone identifiers if the provider supports them.

Customer lookups run separately for each identifier. Duplicate customer matches are combined. If there is more than one distinct match, choose a **Customer** from the selector. Each customer's orders remain attached to that customer and the store that supplied it.

Depending on the provider, you can see contact details, customer duration, amount spent, order count and store administration links. Under **Orders**, inspect supplied order lines, fulfilment, tracking, refunds and returns. Information the store does not supply remains absent.

When order listing is configured without customer lookup, INSIDE can request orders using the visitor's own available identifiers directly.

## Configure it

An administrator with **Settings** and relevant **AI** access, or **Developer**, configures the relevant customer and order operations in **Settings › Commerce › Commerce Providers**. Store permissions must allow those operations. Your operator account also needs access to the visitor's website and subsite.

Keep the visitor's email or mobile details accurate. Linked-contact email values qualify only when they belong to the contact as a whole or to the selected visitor.

## Limits and good to know

- At most five matching identifiers are considered. The panel does not perform an unrestricted name search.
- The panel requests up to 20 orders for each matched customer. It is not a complete export of the customer's history.
- A failed lookup for one identifier does not discard successful matches for other identifiers.
- An order failure can leave customer details visible. Refresh to retry.
- Matching is for the operator's assistance. It does not authenticate the visitor or grant an AI assistant permission to disclose private records.
- Viewing an order does not send it to the visitor. Order sharing is a separate action with its own checks.

## Depends on and works with

### This feature uses

- **Requires** [Commerce provider setup and selection](COM-001.md): The CRM panel needs an enabled provider with customer lookup or order listing available for the visitor.
- **Configured in** [Website, channel and subsite access](ADM-009.md): Operators must have access to the visitor's website and subsite.
- **Works better with** [Shopify commerce connection](COM-002.md): Shopify can supply store customer records and orders.
- **Works better with** [Salesforce B2C Commerce connection](COM-003.md): Salesforce B2C Commerce can supply records with private reads enabled.
- **Works better with** [BigCommerce store connection](COM-004.md): BigCommerce can supply store customer records and orders.
- **Works better with** [Custom commerce integrations](COM-006.md): A custom provider can implement the panel's required operations.
- **Works better with** [Store order details and history](COM-013.md): Order list and lookup supply store history and detail.
- **Works better with** [Order card configuration and access](COM-015.md): Deliberate order sharing applies recipient checks separately from viewing private panel records.
- **Works better with** [Customer contact details](CRM-001.md): Eligible alternate email addresses on the linked contact add customer matching identifiers.
- **Works better with** [Contact matching](CRM-003.md): The visitor's linked contact supplies eligible identity information for panel matching.
- **Related** [Customer and order access](COM-012.md): Operator customer matching does not grant the visitor verified access to private store records.

### Used by

- **Enhances** [Visitor and conversation information panels](CON-017.md): Configured commerce operations add a CRM panel with matched store customers and orders.
- **Enhances** [Order cards in visitor chat](VX-020.md): Operators use the private commerce customer panel to assist with orders.
- **Enhances** [Shopify commerce connection](COM-002.md): Supplies customer matching and order information in CRM.
- **Enhances** [Salesforce B2C Commerce connection](COM-003.md): Optional private reads supply the CRM customer panel.
- **Enhances** [BigCommerce store connection](COM-004.md): Supplies customer and order information in CRM.
- **Enhances** [Custom commerce integrations](COM-006.md): Implemented customer lookup and order list operations can supply the CRM panel.
- **Enhances** [Store order details and history](COM-013.md): The customer panel displays store customers and their orders to operators.
- **Enhances** [Order card configuration and access](COM-015.md): Operators inspect customer orders before deliberately sharing a card.

## FAQ and troubleshooting

### Why is CRM missing for this visitor?

Check the provider's enabled customer and order operations, its subsite availability and your website/subsite access.

### Why am I asked to add an email or mobile number?

There is no usable identifier for this lookup. Add accurate contact information to the visitor and refresh. Supported identifier types vary by provider.

### Why does the Customer selector show several people?

Different eligible email addresses can match different store customers. Select the intended customer and check the displayed contact details before using their order information.

### Why are the customer details visible but orders fail?

Customer and order operations have separate availability and permissions. Use **Refresh customer information**. If the failure continues, ask your **Settings** or **Developer** administrator to test the provider's order operations.

### Does a match let the visitor access their order history?

No. Visitor access requires the separately configured verification process. The operator panel's matching does not establish ownership for disclosure.
