Case study · Customer support

Order status support for multichannel retailers

Company-reported case study

Actigy BPO handled “where is my order?” (WISMO) contacts for Cartwright Retail. The reported comparison moved from 9,400 to 3,000 monthly WISMO tickets over five months, alongside the retailer’s order and carrier records.

Actigy BPO confirms the engagement and supporting records. Results apply to the stated scope and measurement windows.

WISMO tickets

Result

3,000 / month

Baseline: 9,400 / month

Window: 5 months

Supporting record: Zendesk analytics

Handling time

Result

2.1 min

Baseline: 6 min

Window: 5 months

Supporting record: Zendesk analytics

Customer satisfaction (CSAT)

Result

4.5/5

Baseline: 3.7/5

Window: 5 months

Supporting record: Zendesk analytics

Client profile

Cartwright Retail, a UK multichannel retailer with 420 staff.

Challenge and scope

The support team cannot see carrier tracking in its usual queue, so order updates take six minutes to handle at baseline.

Storefront, carrier, and payment records can show different statuses for the same order. A label-created scan may be the latest event even though the buyer expects a delivery date. Without a common view, the desk spends time opening several portals and may give a date that the carrier has yet to confirm.

Delivery workflow

Use Shopify, Zendesk, and approved tracking data from four carriers to answer order questions across two sales channels. Queue missing or conflicting delivery records for follow-up.

Attach the order and carrier references to the ticket and retrieve the latest authorized tracking events. Match the status to a customer response that reflects the last confirmed event. Route lost shipments, address mismatches, and refund requests with the event record and the customer’s prior contacts.

Set follow-up deadlines for shipments where the carrier has yet to provide an updated scan. Review a sample of messages tagged delivered, delayed, or missing and compare the explanation with carrier data. Share recurrent failure patterns by carrier and channel with the retailer’s operations team.

Delivery team

Romania, about 12 FTE. 1 support lead, 2 QA reviewers and 9 order support associates.

Systems and tools

Zendesk, Shopify, carrier tracking APIs.

Client decision rights

The retailer owns refund approval, carrier contracts, and inventory decisions.

Early milestone

At week 4, the WISMO rate is 6,100 contacts a month.

Outcomes

Company-reported results, with the baseline, measurement window and supporting record described for each measure.

Reported results: Order status support for multichannel retailers
MeasureBaselineResultWindowSupporting record
WISMO tickets9,400 / month3,000 / month5 monthsZendesk analytics
Handling time6 min2.1 min5 monthsZendesk analytics
Customer satisfaction (CSAT)3.7/54.5/55 monthsZendesk analytics
Refund-query accuracy92%99.1%5 monthsQA review sample

Interpreting the results

A reduction from 9,400 to 3,000 monthly order-status tickets can reflect several changes in order volume and carrier performance. Use contacts per shipped order and compare the same shipment stages. Read shorter handling time with the gain in refund-query accuracy, where the customer needs a precise next step.

Recommendations for new clients

For retailers with a high share of shipment queries, measure contacts per shipped order as well as total ticket volume. Review changes in carrier mix and shipment volume before interpreting the results.

Start with orders from two carriers and include mixed records such as partial shipments, missing scans, and deliveries reported as missing. Provide carrier status definitions and the escalation route for claims and refunds. Review status accuracy and repeat contact on the same shipments before rolling out across channels.

Scope this workflow for your operation

Use the documented workflow, client-held decisions and operational checks to outline a pilot for your own workload.