Shopify Inbox is free. So why did we build EasyFunnel?
Shopify Inbox is free, it's built into Shopify, and it does exactly what it says it does. If a visitor opens the chat and types a question, someone (or something) can answer. For a store that wants a basic support channel, it's a perfectly reasonable choice.
So why would anyone build something else? Because Inbox solves a different problem than the one that costs Shopify stores the most money.
This isn't a hit piece on Shopify Inbox. It's a clear-eyed look at the job it does, the job it doesn't, and the gap in between where most of your revenue leaks out.
The job Shopify Inbox does well
Inbox is a support tool. Its job is to handle visitors who have already decided to ask something: "Where's my order?", "Do you ship to Canada?", "Can I get a refund?" These are post-purchase or support questions, and the visitor has already made the effort to open the chat and type.
For that, Inbox is genuinely good:
- It's free, with no per-seat or per-message cost.
- It routes messages to your team (or to Shopify's built-in automations).
- It sits inside the Shopify admin, so order context is right there.
- It handles the predictable, repeatable support load that every store gets.
If your main pain is "I can't keep up with customer service tickets," Inbox is a fair answer. It's the same job Gorgias, Reamaze, and Help Scout do, just cheaper and more integrated. We're not arguing with that.
The job Inbox doesn't do
Here's the part that matters for revenue. Inbox is reactive. It waits for the visitor to open the chat and initiate.
That sounds fine until you think about how people actually shop. The visitor who has a question strong enough to open a support chat is the exception. Most shoppers with a question don't ask. They just leave.
Think about your own behavior. You land on a product page. Something isn't quite clear. Maybe the sizing is ambiguous. Maybe you're not sure the part is compatible with what you already own. Do you open the chat and wait for a reply? Almost never. You either guess, or you close the tab and check a competitor. The question never becomes a support ticket because the visitor never asks. It becomes a bounce.
Inbox is built to catch the question once it's been asked. It has nothing to say about the much larger group of visitors who had a question and left without saying a word. That's not a flaw in Inbox. It's just not the job it was built for.
The number that should change your mind
The gap between "asked a question" and "had a question" is where Shopify stores quietly lose the most money.
- A visitor who opens a support chat is already high-intent. They've decided to engage. Capturing them matters, but it's the small end of the funnel.
- The visitor who had a buying question and bounced is the large end. They were close enough to purchase that a single clear answer might have closed the sale, and they're gone.
Support tools measure the first group because those interactions leave a record. The second group leaves no record at all. There's no ticket, no chat log, no abandoned checkout. Just a session that ended on a product page. Most stores never even know those visitors had a question.
This is the real reason "free" can be expensive. A free support tool that only catches the people who were going to ask anyway doesn't touch the larger pool of near-buyers who left. The cost isn't the subscription fee. The cost is every sale that was one answer away and didn't get it.
Why "just improve your product pages" isn't the full fix
A reasonable store owner will read this and think: fine, then I'll just write better product pages. You should. Clearer sizing, sharper compatibility notes, honest shipping estimates, and a plain-language return policy all raise the floor, and every store should do that work.
But there's a ceiling, and it's lower than people think. A product page is the same for every visitor. A purchase decision is specific to each one.
- The size chart is the same for the shopper who's a perfect medium and the one who's between sizes. Only one of them gets their answer from the page.
- The compatibility list is the same for the common device and the edge-case setup. Only one of them needed the clarification.
- The shipping table is the same for the no-rush order and the anniversary gift due Friday. Only one of them is time-bound.
A page answers the average question. The shopper needs their specific answer. The gap between those two is where the would-be buyer either gets resolved or leaves, and no amount of copywriting closes all of it, because the questions are too specific to the individual. We call that gap the invisible objection layer, and there's a full breakdown of what lives there and why no static page can fully anticipate it.
The territory to own: between product page and purchase
There's a stretch of the buying journey that almost no tool is built for. It's the moment after the visitor has read the product page and before they've added to cart. In that stretch, they're deciding. And deciding, for most products, means having questions the product page didn't fully answer.
- "Will this actually fit me?" (apparel)
- "Will this work with the thing I already own?" (electronics, parts, accessories)
- "How fast can they actually get it here?" (delivery, gifting)
- "Which of these three options is the right one for my situation?" (comparison)
- "Can I return it if it's wrong?" (risk)
These aren't support questions. They're commercial questions. They're the objections that sit between interest and purchase. A support tool waits for them to be typed into a chat. A proactive agent catches them while the visitor is still on the page, answers them in real time, and either closes the sale or captures the lead before the visitor leaves.
Don't compete with Inbox. Do a different job.
A common mistake is to evaluate every chat tool against the same yardstick: "Is it a better customer support tool than Inbox, Gorgias, or Intercom?" That's the wrong question for most stores, and it leads to bad decisions.
- If you want a support tool to handle "where's my order" and returns, Shopify Inbox is hard to beat on price, and Gorgias is hard to beat on power. Use one of them. We're not trying to replace that job.
- If you want to catch the buying questions that happen before the purchase, that's a different job. It needs something that engages the visitor who would never open a support chat, answers their specific question, and turns that into a lead or a sale before they bounce.
These are two different tools doing two different things, and most stores need both. Support handles the people who already bought (or who were determined enough to ask). A proactive agent handles the much larger group who were close to buying and needed one answer to finish.
This is also why the "is it a chatbot?" framing misses the point. A chatbot waits to be talked to. An agent goes to where the decision is happening. If you're comparing an Intercom alternative or a Shopify chat tool, the first question to ask isn't "which has better features?" It's "which job am I hiring this for: support, or pre-purchase?" They're not the same job.
What "proactive" actually means here
It's worth being precise, because "proactive chat" has been abused into meaninglessness by tools that just pop up a generic "How can I help?" bubble after five seconds. That's not what catches buying questions.
A useful proactive agent does three things a support chat doesn't:
- It engages at the moment of decision, not on a timer. The right moment is when the visitor is on a product page and showing the small signals of hesitation (scrolling back up, hovering on the add-to-cart button, dwelling on a spec). Not a generic popup the second they land.
- It asks a specific, relevant question, not "How can I help?" A good opener is tied to the product: "Not sure about the fit? I can check the sizing against your measurements." That gets answered. "How can I help?" gets closed.
- It answers before it asks for anything. It resolves the objection first, then captures the contact detail or nudges toward add-to-cart. A support chat asks the visitor to state their problem and wait. An agent resolves the problem and then asks if they'd like to finish the order.
The difference in outcome is large. We've written about the broader pattern in AI chat vs. contact forms: a conversation that answers first and asks once captures multiples of what a passive form (or a passive chat) does. The same logic applies to the pre-purchase moment on a Shopify store.
The honest summary
Shopify Inbox is a good, free support tool. If your problem is support volume, it's a sensible pick. We didn't build EasyFunnel to be a better support tool than Inbox. We built it because the questions that cost stores the most money aren't support questions at all. They're the buying questions that happen in the seconds before a purchase, the ones a product page can't fully anticipate and a reactive chat never gets asked.
If that gap is where your store is leaking, a proactive agent is the tool for that job. You can see how it works on a real Shopify store at the EasyFunnel for Shopify page, or read the full case for owning the pre-purchase moment in the invisible objection layer.
Ready to track your funnels?
EasyFunnel gives you funnel analytics + an AI agent that captures leads. Try the live demo.
Talk to the agent