Passing order details to support agents

Pass order details to an agent only after the integration has found the right order. Show enough context for the agent to judge what the data means. A convenient sidebar is useful, but it should not turn a probable customer match into an unverified statement about payment, delivery or a refund.

Choose fields from the question agents answer

Begin with the enquiries the team handles: “Where is my order?”, “Has the return been received?” and “Which item was charged?” For each, list the fields needed to answer it and the source system that owns those fields. An order number, order date, item summary and current status may be enough for a basic status enquiry. A more complex case may need a direct route to the source record.

Keep status fields distinct. Payment, fulfilment and return progress answer different questions. “Paid” describes payment; it does not mean every item has been fulfilled.

“Fulfilled” describes fulfilment; it does not by itself answer whether a return is in progress. Labels displayed in the support tool should retain those distinctions.

Order Status Fields: What They Mean and When to Use Them

Check the match and the age of the data

A customer can contact support through a different email address or a social account that has no email address. Gorgias documents a Customer Timeline for reviewing customer interactions, including ticket history and Shopify order data. This is a product example, not a reason to assume that similar-looking profiles refer to the same person.

Ask the vendor how the connection selects a customer and an order when several records could match. An agent should be able to search by a verified order reference and see which store the result came from. A useful design also shows when the connected data was updated. It gives the agent a way to open the authoritative order record if the displayed details look wrong.

Display limits matter. Gorgias says its Shopify sidebar shows the ten most recent orders. An older purchase may therefore exist even when it is absent from that view.

Gorgias also documents a case in which a shipping-address change does not immediately appear in its helpdesk. Treat a missing or stale sidebar result as a reason to verify, rather than proof that no order or change exists.

Integration Data Freshness and Visibility Limits

Separate viewing from acting

Decide which agents need to see each field and which, if any, may change an order. Zendesk’s Shopify integration documents both an order-information sidebar and optional refund and cancellation functions. Those are separate capabilities to evaluate. Check the permissions requested by any integration against the support task.

For a sample case, ask an agent to identify the order, interpret its payment and fulfilment states, then explain the next step without changing the source record. Follow with an ambiguous match and an older order.

Record where the agent had to leave the ticket, what information was unavailable and which action needed additional approval. Use those findings to set the fields and permissions the integration actually needs.

Viewing vs Acting in Order Integration