Shopify Support Apps: A 154K Store Study

TL;DR: StoreInspect's February 20, 2026 output found a tracked public support signature in 8,594 latest-snapshot records. A missing signature does not mean a store has no customer service. Use the study to understand detectable ecosystems, then choose tools against your actual channels, order workflows and staffing needs.

Some links in this article are affiliate links. We may earn a commission if you purchase through them, at no extra cost to you.

What the study measured

The retained support-app-stats.ts query selects the latest available snapshot for each store, without an observation-age ceiling or a successful-scrape restriction. Its support predicate matches the support category or specified provider names and slugs. It includes Gorgias, Tidio, Zendesk, Re:amaze, Intercom and Gladly, plus patterns for other tools such as Shopify Inbox, Help Scout, Freshdesk and Richpanel.

Having a matching pattern in the query is different from reliably detecting that tool on every storefront. Email-only helpdesks, backend systems, custom tools and widgets that do not load during the observation can be missed.

The February 20, 2026 output records slightly different totals from separately executed queries:

The status rows sum to 153,866, not 153,867. The retained output does not explain the one-record difference or the overview's two-record difference. We do not silently assign the unmatched records to a support category. Within the status query, the rounded rates are 5.6% detected and 94.4% not detected.

These are historical database observations, not an active-store census or a measure of unmet support demand.

Provider identities and visible coverage

The raw adoption table separates names, slugs and categories. For example, it records Gorgias Chat under gorgias-chat on 2,953 stores and under a null slug on 1,155 stores. Zendesk and Re:amaze also have multiple identities. Summing identity rows can double-count a store.

The separate broad provider-cohort queries deduplicate store IDs by provider name or slug. They report:

These providers can overlap. Their ratios to the 8,594-record support-status cohort are not mutually exclusive market shares, and differences in query predicates matter. We retain the cohort counts without presenting a complete canonical market ranking.

Detection by estimated traffic tier

The support-status query's major stored traffic bands were:

The source also contains small legacy or differently cased tier labels; this table shows the five major bands rather than claiming they cover every record.

Combining the two displayed 1M+ bands gives 327 ÷ 1,931 = 16.93%. Compared with 2,484 ÷ 68,109 = 3.647% below 50K, the ratio is 4.64, not 5.4. The larger 5.4 comparison applies approximately to 1M–5M alone.

Estimated tiers are not actual visitor measurements. The estimator uses technology signals, so an association between support detection and estimated traffic is not independent evidence of ticket volume, revenue or growth. The lower detection rate at 200K–1M also shows that adoption is not a smooth progression.

Choose a support system from ticket history and operational requirements rather than a presumed traffic threshold.

Stored Plus flags and category differences

The source reports 8,140 support matches among 103,230 Plus-flagged records, or 7.9%, and 454 among 50,636 unflagged records, or 0.9%. The ratio using unrounded rates is about 8.8.

These are stored detection flags, not verified subscriptions. Individual provider rows in that table omit aliases; we do not compare a single Gorgias slug with an all-alias overall count. See how to identify Shopify Plus stores for validation.

The niche query uses latest snapshots joined to stored categories:

The rates can guide a comparison with relevant peers. They do not explain why a merchant adopted a tool or prove that live chat converts better in one category. Ask which customer questions and post-purchase problems actually consume staff time.

Support and marketing co-detection

The broad Gorgias query matches distinct stores whose app name or slug contains Gorgias. It then counts distinct stores for each other app name and category. That query reports 3,532 Klaviyo co-detections among 4,113 Gorgias records, or 85.9%.

The original article also showed 3,097 in a separate pairing table. That query selected the first item from unordered arrays of support and email names; it did not count every provider intersection. We have removed that table rather than treating it as the same population.

The category-cohort query reports:

These are historical co-detections, not “winning combinations.” The study measures no customer satisfaction, response-time improvement or return on investment.

For an implementation, the useful question is how support and marketing exchange data: can agents see relevant customer context, do suppressions and consent states carry across systems, and could automated messages overlap? CRM research and technology-stack research can frame those checks.

Choosing among support tools

The following is vendor-documentation research checked October 10, 2026, not a claim that we personally tested each product. Features and exact plan access require verification for your configuration.

No tool is a universal winner. A team already operating a suitable helpdesk may benefit more from repairing workflows than migrating.

Include Shopify Inbox in the comparison

Shopify Inbox requires installation from the Shopify App Store. Online-store chat is configured through the theme's Online store chat app embed, according to Shopify's settings guide.

Current documentation also describes an opt-in Inbox agent, with knowledge drawn from catalog and policy content and handoff to staff. Check its availability and controls in your own store. Public signature coverage in this historical study does not establish how many stores used Inbox.

Evaluate the native option against your required channels, permissions, reporting and order actions. There is no evidence here that it becomes inadequate at exactly 100 conversations.

Model the full cost

Gorgias's current pricing page describes plans from 50 to 5,000 monthly tickets, AI resolution charges and separate Voice/SMS usage. Its rendered page did not expose a complete current dollar quote during our check, so we removed the old $60/300-ticket starting-price assertion.

Tidio's pricing configurator separates plan terms, billable conversations, Lyro allowances and other usage. A one-off AI allowance is different from a recurring monthly allowance. Select the billing term and quantities before comparing costs.

For every shortlist, obtain the base subscription, seats if applicable, channel fees, usage limits, overages, AI billing definitions, onboarding and migration work. Test normal and peak-month costs. The study contains no demonstrated ticket-volume point at which a paid tool automatically pays for itself.

A practical evaluation

Use a representative set of actual support cases: order status, delayed delivery, returns, product questions and a policy exception. Remove personal data from evaluation copies where it is unnecessary.

Check routing, identity, permitted order actions, response accuracy, knowledge freshness and human escalation. Measure your current backlog, response time, resolution time, repeat contacts and customer satisfaction before a trial. Agree on success criteria with the people handling the work.

For an agency prospect, inspect the published contact and chat journeys before describing a gap. Ask whether the existing support system meets the merchant's needs. A missing public signature, a Plus flag or a marketing app does not prove an approved budget.

A concise outreach observation might be: “I could not find a chat route during this dated storefront check. Do you handle those questions through another channel?” It should not claim that the store has no customer support or promise a numerical sales uplift.