Blog · Support operations

How to set up a VIP policy for customer support

Most brands already treat their best customers a little better. It usually happens from memory, and it depends on who picks up the ticket. Below is how I'd write it down, with a builder at the bottom that turns your choices into an SOP.

By Nathan Tone · September 18, 2026

Skip to the SOP builder ↓

Say a customer is on their ninth order with you. The last box showed up missing an item, so they write in. They get the same reply a first-time buyer would: sorry about that, could you send a photo of what arrived and the packing slip, and we'll take a look. Nobody decided that someone on their ninth order should have to prove it. Nobody decided otherwise, either.

At a lot of brands, VIP handling exists but lives in people's heads. The founder recognizes a name in the inbox and jumps in. A senior agent notices a big order total and bumps the ticket up. Whether a good customer gets treated like one comes down to who happened to be looking that day.

In my experience, a VIP policy for support comes down to two decisions: who counts, and what an agent can do for them without asking anyone. Decide both before the ticket comes in, and put them where the agent will see them as soon as it opens. Once those two are settled, the perks mostly write themselves.

Decide who counts

Start with signals your store already has. Lifetime spend is the obvious one. Order count catches the customer who buys small and often, and for a subscription business, tenure does the same job. Pick one or two, set a line for each tier, and keep it to two tiers to start. You can always add a third once the first two are working.

Then there's the situational VIP, whose status comes from this one order. A large first order that arrives broken is the usual case. There's no history with you yet, and the next few emails decide whether there will be. It's worth a rule that treats any order over a set value like a VIP ticket, whoever placed it.

Some people matter for reasons that never show up in spend: creators who post about you, wholesale buyers, press. Those need a manual tag and one person who owns the list, or the list quietly goes stale.

Whatever you pick has to be visible when it matters. If an agent has to open the store admin and add up someone's order history to find out who they're talking to, it won't happen on a busy Monday. In our work, that's a tag on the customer in Shopify, a matching tag in the helpdesk, and custom routing that sends those tickets to the right people.

Last, decide how status ends. A customer who spent a lot three years ago and hasn't ordered since probably shouldn't hold your top tier forever. Measuring spend over a rolling window, the last twelve months for example, keeps the tiers current without anyone having to maintain them.

Write down what an agent can do without asking

Most VIP treatments fall into five groups:

• Speed: front of the queue and a shorter response target.
• Who handles it: straight to a senior agent or a small named team, and past the bot.
• Spending authority: refunds, credits and replacements up to a set amount with no manager sign-off, and shipping or return fees waived.
• Less work for the customer: no photos, receipts or return shipments on low-value claims, and more room on late returns and final-sale exchanges.
• Owning it: the agent sees the problem through to the end, including calling the carrier themselves.

Look at the middle three. Most of what makes VIP support feel different is a check that got removed: an approval, a request for evidence, a return label. Removing a check is a policy decision, so it needs a number attached. "Use your judgment with VIPs" leaves every agent guessing how far they can go, and each one guesses a little differently. "Refund or replace up to $X without approval, and no photo needed under $Y" leaves nothing to guess.

There isn't a correct figure. It depends on your margins and what a customer at that tier is worth to you. A reasonable place to start is the amount you'd approve anyway if an agent brought it to you. At that level the rule only removes the wait.

Speed and routing cost you very little per ticket, since it's the same work done sooner or by someone more experienced. The spending groups are where the money goes, so that's where the numbers deserve the most thought.

Reach out first

Everything above happens once a VIP writes in. The other half of it is contact they didn't have to ask for.

A support queue is organized around the case: a ticket comes in, gets solved and gets closed. For your best customers it's worth organizing around the relationship, which mostly means reaching out at the moments a ticket would otherwise end or never start:

• When something goes wrong on your side. If a VIP's shipment stalls or an item they ordered is delayed, tell them and say what you're doing about it before they have to ask.
• When something new is coming. Give them first access to a launch or a restock before it goes public.
• After it's resolved. Check back once the replacement lands or the refund clears, and make sure everything is good now. It's one short email.

This part needs its own owner and a trigger for each moment, like a stalled tracking scan, a launch date on the calendar or a replacement marked delivered. Without a trigger, it's the first thing to go on a busy week.

Put it all in one table

Tiers across the top, treatments down the side, and a limit or a yes/no in every cell. Something like this, with your own numbers in place of the letters:

Keep it small enough to read at a glance, because agents check it in the middle of a ticket. And fill in the first column honestly. Writing down what everyone gets is what makes the VIP columns mean anything, and sometimes it shows that the base policy is stricter than you meant it to be.

In our work, rules like these go into the SOP, and AI reasons over the SOP, the customer's history and their message to put together the action and the reply. Without any AI, the table alone gets you most of the way. Everyone who answers tickets is working from the same numbers, and the builder at the bottom of this post turns your version into a first SOP you can hand to your team.

Won't VIP rules get abused?

Some. And a customer with a high lifetime spend can also be a customer who returns a lot, so a rule keyed only to gross spend can hand your loosest terms to your most expensive customers. A few guardrails cover most of it:

• Tag everything that goes out free. Replacements, refunds, waived fees. The next agent sees what this customer has already had.
• Cap the no-questions allowance. A set number of claims per customer per year, after which the next one gets a normal look.
• Count net spend. Subtract returns and refunds before deciding the tier.
• Let status expire. The rolling window from earlier handles this.

When one of those trips, stay kind. You can empathize with what they're dealing with and explain how the next one will be handled. Accusing a long-time customer of gaming you in a support email helps nobody.

Questioning your best customers has a cost of its own, too. Asking someone on their ninth order for a packing slip to catch the rare bad actor costs you something with every honest customer who gets the same request.

Where to start

Pull your customer list sorted by spend over the last year and look for the natural break. Pick one or two criteria and set up the tag. Fill in the table with the numbers you'd approve anyway, then hand it to whoever answers tickets, person or AI.

Most of what VIP treatment means, like reading everything a customer has said before, noticing the thing they didn't ask about, or reaching out before there's a problem, has always been possible; it's been expensive, so brands saved it for the customers who spend the most. That cost is coming down, and some of what's in your top column today could end up in the first one.

For now, start with the table. Your ninth-order customer can keep their packing slip.