Owner or Team Lead? Who Decides Escalated Shopify Tickets

Most stores never write this down. So every hard ticket ends up with the owner, or it sits in the inbox because nobody wants to decide for the boss. This guide covers how to split decision power between the owner and the team lead, which cases only the owner should handle, and how to write it all on one page.

Owner vs team lead: two different jobs

Many founders treat "escalation" as one step up a ladder. In practice there are two separate jobs. The team lead handles exceptions to normal rules. The owner handles risk to the business.

Here's who does what, decision by decision:

• Refund or credit above the normal limit, up to a cap you set: the team lead decides, the owner sets the cap.
• Exception to a written policy (late return, final sale): the team lead decides, inside the exception rules. The owner writes the exception rules.
• Final "no" to a customer who keeps pushing: the team lead decides and closes. The owner isn't involved.
• Goodwill gesture for a long-time customer: the team lead decides, inside a goodwill budget. The owner sets the budget.
• Legal threat, filed chargeback, regulator contact: the team lead flags and stops. The owner decides.
• Injury, health reaction, product safety risk: the team lead flags and stops. The owner decides.
• Suspected fraud, account takeover, data request: the team lead flags and stops. The owner decides.
• Press, wholesale or partnership request: the team lead forwards. The owner decides.

Look at what each side decides. The team lead's decisions are about money and policy. The owner's decisions are about exposure. If a decision only costs money and the amount is under the cap, the owner shouldn't see it.

How to write an authority map

An authority map is a short document that says who can decide what, and up to which limit. One page is enough. It has three parts.

1. Money limits. Write down a number for each type of decision. Base it on your own margins, not on a benchmark.

• Refund without return: the team lead can approve up to a set amount per order.
• Store credit or discount code: a separate limit, usually higher, because it keeps the customer.
• Replacement shipment: allowed when the carrier confirms a loss or the item arrived damaged, inside a set order value.

Anything above a limit goes to the owner, with the order and the reason attached. If there's no number, there's no rule. "Use your judgment" sends every case back to the owner.

2. Policy exceptions. The team lead needs written exceptions, not just the policy. For example: "A return up to a few days past the window is accepted if the customer contacted us before the deadline." Or: "Final sale stays final, except for a wrong item shipped by us."

If your sale items cause the most pushback, our guide to a Shopify sale-item return policy, listed at the end of this article, shows how to separate "discounted" from "final sale" so the team lead isn't arguing about grey areas.

3. Who gives the final no. Someone has to be allowed to say "this is our final answer" and close the ticket. That person should be the team lead, not the owner. If a customer learns that pushing harder gets them to the owner, and the owner says yes more often, they will keep pushing. The decision has to depend on the facts of the order, not on how many times the customer asked.

Owner-only cases: legal, safety and security

These are the cases where the team lead's job is to stop and flag, not to decide. A wrong reply here can cost far more than a refund.

Legal. Triggers: the customer mentions a lawyer, says they've filed a chargeback, or mentions a consumer protection body or regulator. Before the owner replies:

• Stop any automated action on that order (refund, cancellation, new code).
• Don't argue about who's at fault in writing.
• Gather the order, the full thread and any evidence (tracking, photos, delivery confirmation).

The owner decides whether to settle, contest the chargeback or ask for outside advice.

Safety. Triggers: an injury, an allergic or skin reaction, a product that overheated, broke dangerously or got into a child's hands. The team lead acknowledges the message, asks the customer to keep the product and its packaging, and sends the case to the owner. The owner decides on the fix and whether other orders from the same batch need checking. One safety ticket can affect every customer who bought that product, so it can't be treated as a one-off refund.

Security. Triggers: someone asks to change the address on an order that isn't linked to their email, a customer says they never placed the order, an account looks taken over, or someone asks for their personal data or for it to be deleted. These tickets look routine. They aren't. An address change for the wrong person is a parcel handed to a stranger. The team lead freezes the action and sends the case to the owner, or to whoever handles fraud and data.

When the owner is also the whole support team

On many small Shopify stores, the owner answers every email. Then "escalate to the owner" means nothing. Every ticket is already with the owner.

The authority map still helps. Write it as if you had a team lead, then hand the team lead's part to someone else: a first hire, a contractor or an AI agent. You keep the owner's part. That's the real job of a first support hire, and our guide on how to hire your first Shopify customer support rep, listed at the end of this article, covers that option.

Relay's take is on its homepage: "Your First Support Hire, Without The Hire."

Where an AI agent fits in the authority map

An AI agent doesn't replace the owner's part. It takes on the routine work in the team lead's part, inside the limits you write.

In Relay's own words, Relay "understands your product, answers customer questions, takes action, and knows when to bring in your team." With Permissions, you choose what Relay can do, from replies to refunds. The site lists issuing refunds based on policies, offering discounts within set limits, processing exchanges for eligible items, and updating orders (shipping address, cancellations, edits).

That maps directly to the authority map. The money limits you wrote for the team lead become the limits you give the agent. The owner-only triggers become the cases the agent hands to your team.

This article is about who decides. For how the handoff itself works and how to word it, two guides are listed at the end of this article:

• How to set up human handoff rules in a Shopify AI agent, for triggers and testing before launch.
• What AI support for Shopify should and should not answer, which sorts tickets into four zones, including the safety, legal and security cases that go straight to a person.

One-page authority map checklist

Before you call it done, check that:

• Every money decision has a number, not "use judgment."
• Each policy has at least one written exception, or a clear "no exceptions."
• One named person can give the final no and close the ticket.
• Legal, safety and security triggers are listed by name.
• For owner-only cases, the team lead's job is written as "stop, gather, flag."
• Any AI agent's permissions match the team lead's limits, never the owner's.
• Once a month, the owner reviews the escalated tickets and asks: should this limit move?

That monthly review keeps the map useful. If the owner approves the same type of exception every week, it belongs with the team lead.

FAQ

What is the difference between escalating to a team lead and to the owner? A team lead handles exceptions: refunds above the normal limit, late returns, goodwill gestures. The owner handles risk: legal threats, safety issues, security problems and business requests. Most escalations should stop at the team lead.

How do I set a refund limit for my support team? Pick an amount per order based on your own margins and the cost of losing the customer. Write it down, and send anything above it to the owner with the order attached. Review it every month based on what was escalated.

Should the owner reply when a customer threatens legal action? The owner should decide what happens next. The team lead or AI agent should stop any automated action on the order, avoid arguing about fault, gather the evidence and pass the case on.

Can an AI agent make decisions that a team lead would make? Yes, within the permissions you give it. In Relay, you choose what it can do, from replies to refunds, and it knows when to bring in your team. Keep the legal, safety and security decisions with a person.