Shopify app support models, compared

Shopify app support comes in three basic shapes: an automated assistant that answers first and hands over to people when it cannot, a ticket system that sorts requests by priority, and direct access to the developer who wrote the code. Each one is a reasonable answer to a real constraint, and each one breaks in a predictable place. This guide describes the three models using the public help centers of well-known apps, shows where each tends to fail a merchant with a live problem, and ends with the questions that tell you which model you are buying.

Who owns the problem in the first place

Before comparing vendors, it helps to know where Shopify draws the line. Its Help Center states that "Shopify only provides support for apps made by Shopify." For a third-party app, the developer handles app errors, feature questions, theme code additions, and charge disputes or refund requests. A merchant can send a request from the admin (Settings, then Apps, then the app's support option), and Shopify forwards it to the developer. Shopify then contacts the merchant after 3 days to ask whether the developer helped, and contacts the developer again if not.

Two more details from the same page are useful when you shop for apps. The Support section of an App Store listing shows which developer provides support, and the Website link in the listing's Developer section leads to that developer's own support channels. Shopify's App Store requirements also ask developers to add an emergency developer contact to their Partner Dashboard (requirement 4.5.6), and to let merchants upgrade and downgrade plans without having to contact support (requirement 1.2.3).

So every app has a support model, and the one that matters to you is the developer's.

Model one: the assistant answers first

Many large apps put an automated assistant at the front door. Klaviyo's Help Center describes Composer's virtual assistant, which "will suggest relevant resources." On paid plans, Klaviyo offers email and chat support; email runs 24/7 and chat with a person runs 24/5, with weekend hours that vary by plan. If the assistant cannot resolve the issue and the plan includes chat, the customer "may be added to the live chat queue." Free plans do not include live chat with a human support specialist, and email support on a free account is available for the first 60 days after the account is created.

Judge.me uses the same front door with different hours. Its help article says the support team is available 24/7, including weekends and holidays. Live chat opens with an instant response from an AI assistant, "which can resolve most questions right away," and a human support team is available around the clock behind it. Email replies come within 24 hours. The company says it does not offer phone support or scheduled demo, onboarding or consultation calls.

Where it works. Questions with a documented answer: where a setting lives, what a plan includes, how to export something. An assistant can answer those at three in the morning.

Where it fails merchants. Problems specific to one store. A gift that does not appear in one theme's cart drawer, or a discount that stops combining after another app was installed, has no article to retrieve. The merchant spends the first minutes of the conversation getting past the assistant, then explains the problem again to the person who picks it up.

Model two: the ticket queue with triage

Larger support teams sort work by urgency. Recharge's Help Center says in-app support is available 24/7 through a virtual assistant that serves FAQs, troubleshooting guides and product information. Live agents are available from 6 AM to 6 PM Pacific time, Monday through Friday, excluding observed US holidays. Recharge notes that live agent support "is primarily for context gathering, with resolutions provided in follow-up emails." Video callbacks are offered to merchants on its Custom Pricing plan, in the same weekday window.

Its ticket handling article explains the triage: requests are answered in order of priority and then in the order submitted, so a service outage goes ahead of a widget configuration request. Merchants pick a priority when they submit, and Recharge may change it as the issue develops. Requests sent outside in-app support, such as through social media, are not covered by its service level agreement.

Where it works. At scale. Triage keeps an outage from waiting behind a styling question, and a ticket keeps one written record that several engineers can read.

Where it fails merchants. Time zones and handoffs. A store on the East Coast whose problem starts at 7 PM Eastern on a Friday is outside a 6 AM to 6 PM Pacific weekday window until Monday. And a model where the first conversation gathers context and the fix arrives later by email works well for complex investigations, but for a merchant mid-launch it means at least one more round trip before anything changes on the store.

Model three: the person who wrote the code

Small vendors often skip the layers. The developer reads the message, opens the code or the store's page source, and answers. There is no assistant to get past and no handoff, because the person who diagnoses the problem is the person who can change the code.

Where it works. Store-specific problems and pre-install questions. A developer can say "yes, that theme's cart drawer is supported" or "no, that combination is not possible today, here is the closest thing" from direct knowledge, and can ship a fix without a ticket crossing teams.

Where it fails merchants. Availability and scale. One person cannot be awake around the clock, and a vendor whose support depends on one inbox has to say honestly what happens when that person is away. The model only holds if the vendor collects a way to follow up, such as an email, before the conversation starts, and actually replies.

Why small vendors can offer direct access

Two things make it possible. The first is volume: a young app with a focused set of features gets fewer and more similar questions, and a developer can answer them alongside building. The second is how Shopify assigns responsibility. Because the developer already owns errors, theme code additions and charge disputes for its app, putting that developer in the chat removes steps rather than adding a new role.

That is the model we chose. On this site the chat is answered by the developer who builds the apps; we describe the promise and what the chat stores in why a real developer answers our chat.

What to ask any vendor about support

• When I write at 7 PM Eastern on a Friday, who reads it, and when?
• Is the first reply from a person or an assistant, and how do I reach a person?
• Will the person I talk to be able to fix the problem, or will they pass it on?
• Which channels does my plan include, and which are reserved for higher plans?
• Where do I see the developer's support channels before I install?

Ask the same five of every app on your shortlist. The answers are usually on the vendor's help center. Seven questions to ask before installing adds the technical side: theme fit, speed, uninstall cleanup, data and billing.

FAQ

Does Shopify support third-party apps? No. Shopify's Help Center says it only supports apps made by Shopify. It forwards admin support requests to the developer and checks back with the merchant after 3 days.

Is an AI assistant a bad sign? Not by itself. It answers documented questions at any hour. What matters is how quickly you reach a person when the problem is specific to your store.

How do I find an app's support channels before installing? Shopify says the Support section of the App Store listing shows which developer provides support, and the Website link in the Developer section leads to its support channels.

Talk to us before you decide

If you are comparing apps right now, ask us the five questions above in the chat and judge the answer. Plans are on the pricing page, the mini apps hub shows what each app does, and the Help Center has the setup guides.