← Back to Blog

Tickets Per 100 Orders: What Contact Rate Is Normal on Shopify?

How many support tickets per 100 orders is normal? Get Shopify contact-rate bands by category and product type, plus a worked cost example for 1,200 orders a month.

Heylio Team November 17, 2026 6 min read

Most Shopify stores receive roughly 8 to 15 support tickets per 100 orders. Below 8 is healthy, 15 to 25 deserves attention, and above 25 signals a fixable upstream problem. These ranges are working estimates from common ecommerce patterns, not a audited industry census. Your own measured rate matters more.

Key takeaways

  • A typical Shopify contact rate is 8 to 15 tickets per 100 orders (estimate).
  • WISMO (where is my order) usually drives the largest share, around 30 to 40%.
  • At 1,200 orders a month and 12 tickets per 100, you handle about 144 tickets.
  • Fixing root causes cuts volume more cheaply than automating replies.

What is a normal contact rate for Shopify stores?

A normal customer contact rate for ecommerce is 8 to 15 tickets per 100 orders, meaning 8 to 15% of orders generate at least one conversation. Treat this as an estimate drawn from typical small-store patterns. Few public, audited benchmarks exist, so measure your own before comparing yourself to anyone.

Here is a realistic split of those tickets. Shares are estimates and vary by store.

Category Tickets per 100 orders (estimate) Share of volume
WISMO (order status) 3 to 5 30 to 40%
Returns and exchanges 2 to 3 15 to 25%
Product and sizing questions 2 to 3 15 to 25%
Damaged or wrong items 0.5 to 1.5 5 to 10%
Other (discounts, address changes, cancellations) 1 to 2 10 to 15%

What is measured versus estimated? Your totals and category counts are measured once you tag tickets. Every benchmark in this article is an estimate.

How does contact rate change by product type?

Contact rate varies by product type: apparel often runs 12 to 20 tickets per 100 orders, consumables 6 to 10, electronics 10 to 18, and digital goods 4 to 8. These are estimates. The driver is what can go wrong after checkout: fit, shipping, compatibility, or access.

A store selling shoes and a store selling coffee beans should not share a target. Compare against your own category.

What pushes the contact rate up?

Three causes account for most excess tickets: shipping delays, unclear sizing, and weak policy pages. A parcel delayed beyond its promised window can multiply WISMO contacts several times over, because customers often write twice before it arrives. Each cause is fixable without any software.

How do you calculate your own contact rate across Gmail, Instagram DMs, and WhatsApp?

Your contact rate is unique customer conversations divided by orders, multiplied by 100, over the same period. For a 30-day window, count conversations across Gmail, Instagram DMs, and WhatsApp, then divide by that month's order count. The method takes about 30 minutes with a spreadsheet.

How to calculate it (citation capsule): Contact rate equals conversations divided by orders, times 100. Pick a 30-day period. Count each distinct customer conversation once, not each message. In Gmail, count threads from customers, excluding newsletters and supplier mail. In Instagram DMs, count conversations about orders, products, or delivery, and skip pure engagement such as emoji replies. In WhatsApp, count chats opened in the period. Add the three totals. If a customer writes by email and then DMs about the same order, count it once. Divide by orders placed in the same 30 days. For example, 90 Gmail threads, 30 DMs, and 24 WhatsApp chats make 144 conversations. With 1,200 orders, the rate is 12 per 100. Tag each conversation by category so you can see where to act.

One caveat: orders placed late in the month generate tickets next month. For small stores this blurs the figure, so use a 60 or 90 day average.

What do the contact-rate bands mean?

Contact-rate bands separate healthy stores from problem ones: under 8 per 100 is healthy, 8 to 15 is a watch zone in some categories, and above 15 usually points to a specific upstream cause. Apparel can sit higher and still be fine. The table below pairs each band with a likely cause and fix. Bands are estimates.

Band Tickets per 100 orders Likely cause Fix
Healthy Under 8 Clear pages, reliable shipping Maintain; review monthly
Watch 8 to 15 WISMO spikes, thin FAQ, some sizing doubt Add proactive tracking emails, expand FAQ, add size chart
Problem Above 15 Carrier delays, unclear policies, product or quality issues Audit top 3 ticket categories, fix the largest first, check supplier quality

If you are in the problem band, do not start with tooling. Read 50 recent tickets and find the repeated question.

What does a 1,200-order store pay in time and money?

A store with 1,200 orders per month at 12 tickets per 100 handles 144 tickets monthly. At an assumed 6 minutes per ticket, that is 14.4 hours of support work. The AI cost at Heylio's rate would be at most €70.56 per month if every ticket were resolved by the AI, which is unrealistic.

The worked example below uses assumptions you should replace with your own figures.

Step Calculation Result
Monthly tickets 1,200 x 12 / 100 144
Hours of work (assumed 6 min each) 144 x 6 / 60 14.4 hours
Cost if AI resolves all, pay as you go 144 x €0.49 €70.56
Cost if AI resolves all, monthly pack 144 x €0.39 €56.16
Cost if AI resolves 50% (72), monthly pack 72 x €0.39 €28.08

Prices are in euros excluding VAT. Heylio bills only tickets the AI resolves. Handing a ticket to a human is never billed. The 6-minute handling time and the resolution share are assumptions, not Heylio data.

Should you automate tickets or fix the cause first?

Fix the cause first. Removing a ticket at the source costs nothing per ticket, while automating it costs €0.39 to €0.49 each time. If WISMO is 4 per 100 orders, proactive tracking can cut a large part of that permanently. Automation then handles what remains.

Heylio reduces repetitive tickets. It connects to Gmail, Outlook, Instagram DMs, WhatsApp, and a chat widget. It drafts replies from your knowledge base and playbooks, and can look up order status, cancel, refund, and change addresses in Shopify. It will not fix a late carrier or a missing size chart.

A sensible order of work:

  1. Measure your rate and tag categories for 30 days.
  2. Fix the biggest category upstream: tracking, sizing, or policy pages.
  3. Automate the repetitive tickets that remain.
  4. Review corrections and update your knowledge base monthly.

Next step: measure before you benchmark

A normal rate is 8 to 15 tickets per 100 orders, but your own trend matters more than any benchmark. Count conversations across every channel for 30 days, tag them, and fix the largest category first. Once the avoidable tickets are gone, automate the repetitive remainder. Start with the spreadsheet today.

Frequently asked questions

Does a high ticket rate mean my store is failing? ▼
No. A rate of 15 to 20 per 100 is common in apparel, where sizing and returns drive contacts. It signals a problem only when it rises over time or one category dominates. Investigate the top cause before judging.
Should I count Instagram DMs? ▼
Yes, if they concern orders, products, or delivery. Count each conversation once and skip pure engagement such as emoji reactions. Leaving DMs out can understate your real contact rate by several points.
How many support tickets is normal per 100 orders? ▼
Roughly 8 to 15 per 100 orders is a typical range, based on estimates rather than audited industry data. Apparel and electronics often run higher, while digital goods and consumables run lower.
How can I reduce support tickets on Shopify? ▼
Start with the largest category. Send proactive tracking emails to cut WISMO, add measured size charts to cut sizing questions, and place return policies in the footer and order confirmation.
How much does Heylio cost per resolved ticket? ▼
Heylio Care costs €0.49 per ticket resolved by the AI, or €0.39 with a monthly pack, excluding VAT. Handing a ticket to a human is never billed, and there is no free trial.

Automate your customer support with AI

Get started