Case study · Technical support

Technical support for ecommerce merchants

Company-reported case study

Actigy BPO provided merchant-facing L1 and defined L2 support for ShopStack. The team handled integration, checkout and theme incidents within the ecommerce platform’s approved access and escalation rules.

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

Ticket volume

Result

2,100 / month

Baseline: 3,600 / month

Window: 5 months

Supporting record: Zendesk analytics

Resolution time

Result

3.4 hours

Baseline: 12 hours

Window: 5 months

Supporting record: Zendesk analytics

Integration-ticket deflection

Result

38%

Baseline: No baseline

Window: 5 months

Supporting record: Zendesk analytics

Client profile

ShopStack, a UK ecommerce platform for mid-market merchants with 110 staff.

Challenge and scope

Merchant tickets average 12 hours to resolve at baseline. Issues span several integrations and can require an engineering escalation.

Merchants may report a broken integration, unexpected platform behavior, or a partner outage under the same ticket category. The first response needs to establish where the fault appears and what it affects. Incomplete evidence creates additional requests from both the merchant and the integration partner.

Delivery workflow

Cover 3,600 monthly merchant tickets across eight integration partners on a 24/5 desk. Gather reproduction steps, check approved diagnostics, and route product defects through Jira.

Use approved read-only records to capture the store, integration, request or event reference, and time of failure. Reproduce the behavior within authorized tools or record why it cannot be repeated. Send evidence to the responsible partner or engineering queue, with severity, steps checked, and a link to the customer issue.

Group repeated cases by integration and symptom, and maintain a shared issue record for common incidents. Update approved merchant guidance as root causes become clearer. Use a sample of closed and deflected requests to check the resolution and identify guidance that still generates contacts.

Delivery team

Poland, about 9 FTE. 1 technical lead, 2 L2 engineers and 6 L1 associates.

Systems and tools

Zendesk, Jira, Shopify, AWS CloudWatch.

Client decision rights

The platform owns code changes, partner contracts, and merchant admission.

Early milestone

In week 4, the resolution time reaches 7.1 hours.

Outcomes

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

Reported results: Technical support for ecommerce merchants
MeasureBaselineResultWindowSupporting record
Ticket volume3,600 / month2,100 / month5 monthsZendesk analytics
Resolution time12 hours3.4 hours5 monthsZendesk analytics
Integration-ticket deflectionNo baseline38%5 monthsZendesk analytics
Merchant CSAT3.9/54.6/55 monthsZendesk analytics

Interpreting the results

The case reports 1,500 fewer monthly tickets and much shorter resolution time. Compare volume per active merchant or integration and use a stable window for follow-up contacts after a self-service step. Read merchant satisfaction and resolution time by integration and responsibility to identify where additional support still helps.

Recommendations for new clients

For ecommerce platforms with integration-heavy queues, tag tickets by partner and issue type. Track contact volume and deflection against the active merchant base and keep resolution time visible.

Provide representative cases for the busiest integrations and at least one issue that needs partner escalation. Agree what the team can inspect in Shopify and log tools, and how partner responders acknowledge a case. Test a known incident and a new product fault before increasing the queue scope.

Scope this workflow for your operation

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