If you're trying to find an agency to build your support system, the fastest way to sort the field is to ask what happens to the work if you stop paying them. Agencies that resell a helpdesk platform will lose the automation, because it lives inside someone else's software. Agencies that build you a system will hand you something that keeps running, because you own it. Everything else in the vetting process follows from that one question. This article gives you the rest of the questions, in the order to ask them, so you can tell the difference on a first call rather than three months into a contract.
Two kinds of agency answer this search, only one builds you anything
Search for a support agency and you'll get two very different businesses mixed into the same results page. The first is a helpdesk reseller: they set up Gorgias or Zendesk, write your macros, configure your triggers, and bill you monthly per agent seat. The second is an agency that builds a custom built customer service system for ecommerce, meaning software wired directly into your store, your carrier, and your order data, that you own outright when the project ends.
Both call themselves a "support automation partner." Both will show you a demo where a customer asks about an order and gets an instant answer. The difference is what's underneath the demo. One is a configuration of a $2,000-a-year software you're renting seats on. The other is a system built for your specific tickets that has no per-seat license baked into it at all. This article is a vetting guide for the second kind.
The pricing model tells you which one you're talking to
Pricing is the cleanest signal you'll get before you ever sign anything. If a proposal charges per agent, per seat, or "per helpdesk user," you're paying for access to software the agency has resold you, and the price rises every time you hire someone to answer tickets. If a proposal quotes a fixed build fee for the workflows themselves, plus your own hosting or infrastructure costs, you're paying to own something.
Read a pricing page the same way. Reseller pricing lists tiers like "Starter, 5 seats" or "Growth, 15 seats." Builder pricing lists project scope: which ticket types get automated, how many integrations, what the handoff to your team looks like. If you can't find a seat count anywhere on the page, that's usually the tell you want. Ask directly: "If we add three more support staff next year, does our monthly cost change?" A reseller's answer is yes. A builder's answer is no, because the system doesn't care how many humans are logged into it.
Why you can't hire your way out of repetitive support tickets
Most founders start this search after a bad hiring cycle. You hire someone for support, they burn out on "where's my order" and "can I change my shipping address" within two months, and you're back to interviewing. The hire isn't the problem. Those tickets don't need judgment, they need a workflow: look up the order, check the carrier status, apply the update, close the ticket.
Answering the same four questions 200 times a day is data entry with a chat window attached, not customer support. Headcount scales linearly with ticket volume: double your order volume, and you need roughly double the staff to hold response times, unless the repetitive fraction of tickets is handled by something other than a person. That's the actual argument for a system over another hire. Ticket volume grows with revenue. Headcount doesn't have to.
This is also why agencies keep getting hired for the same fix: manual work compounds. A founder patches it with a hire, the hire quits or plateaus, the backlog grows, and the founder looks for an agency to build your support system instead of a fourth attempt at hiring.
Six questions to ask on the first call
Ask these in order. The answers will sort resellers from builders faster than any case study.
- "Who owns the workflow logic if we cancel?" A builder answer names you, in writing, and explains the handoff. A reseller answer talks about "your account" on their platform of choice, which isn't the same as ownership.
- "Can you show me a system with no per-seat helpdesk license underneath it?" If every demo they show runs inside Gorgias, Zendesk, or Front, they are a configuration shop, not a build shop.
- "What's the first workflow you'd automate for us, and why that one?" A builder should be able to name a specific ticket type by volume, for example "address changes, because you're probably getting 40 to 60 a week and each one takes a person three minutes."
- "What happens to response time if our order volume doubles next quarter?" You want to hear that the system scales without a proportional cost increase, not "you'd add another seat."
- "Do you write custom code for this, or only configure an existing app's automation rules?" Configuration inside a helpdesk's rule engine is not the same as a system built against your store's API and your carrier's API.
- "Can we talk to a client who took this in-house or moved it to another developer?" Builders don't mind this question because portability was the point. Resellers usually can't answer it, because there's nothing to move, it's a subscription.
If you want a partner and not a vendor, these six questions are the fastest way to hire an ops automation partner for ecommerce rather than sign up for another software bill.
Red flags that mean you're being sold a reseller relationship
A few patterns show up consistently when an agency is reselling a platform rather than building you anything:
- They quote per agent per month rather than a fixed project fee.
- They can't clearly explain what happens to the automation the day you stop paying them.
- They steer every conversation toward a specific helpdesk brand's app marketplace, because that's where their commission or partnership sits.
- Every case study they show operates inside the same one platform's ecosystem, with no example of a workflow that runs independent of it.
- The pitch uses "seamless" and "all-in-one" more than it names an actual handoff they removed.
None of these are dealbreakers on their own; plenty of businesses are genuinely well served by a configured helpdesk. The problem is being sold that as if it eliminates operational drag, when what it actually does is move the drag into a subscription you can't take with you.
What a custom built support system actually replaces
It helps to picture the mechanics instead of the pitch. A custom built customer service system for ecommerce usually replaces a specific stack of manual lookups: a customer asks where their order is, someone opens the store admin, cross-references the carrier tracking page, and pastes a status back into the reply. A system does that lookup automatically, pulling live carrier data and replying without a person touching the ticket.
Address changes work the same way: instead of a person editing the order in the store backend and hoping it's caught before the warehouse packs it, the system checks fulfillment status and either applies the change directly or flags it as too late, automatically. Refund triggers route based on rules you set (order age, product category, return reason) rather than a person deciding case by case. Return labels get generated and emailed without anyone opening a shipping tool. Routing rules send the tickets that do need judgment to a person, and only those tickets.
None of this lives as a macro inside a helpdesk. It's wired directly into your store's data and your carrier's data, which is what makes it a system rather than a faster way to type the same reply.
What ownership needs to say in the contract, not just the pitch
"You own it" is a sentence anyone can say on a sales call. It only means something if it's written down. Before you sign with any agency, get three specific things confirmed in the contract, not the pitch:
- Who holds the code and credentials. You should have access to the repository and the API keys, not just a login the agency controls on your behalf.
- Whether you can take it to another developer. If the answer requires the original agency's continued involvement to function, that's a license with extra steps, not ownership.
- What infrastructure it runs on. A system built on infrastructure you control (your own hosting account, your own store's app framework) is portable. A system built entirely inside an agency's proprietary platform is not, no matter what the sales page calls it.
This is the actual test for owned by you: could you fire the agency tomorrow and still have a working system. If the contract doesn't answer that clearly, assume the answer is no.
A five-minute scoring sheet for comparing agencies
Use this on your next three calls. Score each agency 0 to 2 on each line, 2 meaning a clear builder answer, 0 meaning a clear reseller answer.
- Pricing model: fixed build fee (2) versus per-seat or per-agent (0)
- Ownership answer: named, in writing, code and credentials included (2) versus vague or platform-dependent (0)
- Demo: a real workflow wired to store and carrier data (2) versus a helpdesk skin with macros (0)
- Portability: can name a client who moved the system elsewhere (2) versus no example (0)
- Specificity: named your likely highest-volume ticket type unprompted (2) versus generic "we automate support" (0)
Anything scoring 7 or above out of 10 is worth a second call. Anything under 4 is a reseller, whatever they call themselves on the homepage.
If you'd rather skip the calls and see the numbers first, our support cost calculator works out what your current manual ticket handling is costing per month before you talk to anyone.
Common questions
Is a custom built support system always more expensive than a helpdesk subscription?
Upfront, usually yes. Monthly, no, because you stop paying per seat and stop paying for tickets a workflow could have closed without a person.
Can an agency build a custom system on top of Gorgias or Zendesk instead of replacing it?
Yes, some client setups keep the helpdesk as the inbox and add the automation around it, the ownership question is the same either way, ask who owns the logic.
How long does it take to build a support system like this?
Most builds run a few weeks for the first set of workflows, not months, since it starts with the highest volume ticket types, not a full rebuild.
What if we already pay for a helpdesk and don't want to switch?
You don't have to, an audit call maps what's manual inside your current setup and what a system would take off your team's plate without a platform migration.
If you're weighing this up for your own store, our ecommerce support automation page breaks the queue down by ticket type, with a fixed price against each one.
Find out what the manual work is costing you
One call, we map where the time goes and what a system would replace.
