Why we built SupportPilot the way we did

Customer support is the most repetitive emotional work on the internet.

Where is my order. Can I cancel. The size doesn't fit. I haven't received the refund. The shipping label is wrong. The address was a mistake. These are the same eight emails, written by hundreds of different humans, dropped into your inbox every week. None of them is hard. All of them, together, are exhausting.

For a small team — one founder, two part-time agents, a freelance VA — answering them is the work that fills the day and starves everything else. Product roadmap. Marketing. Sleep.

That's the work SupportPilot is built for. Not the dramatic ticket. Not the legal escalation. The boring, repetitive, eighty-times-a-week work.

The bet: human + AI on most cases. Not AI alone.

Most AI support tools sell a fantasy: fully autonomous, resolves 100% of tickets, set it and forget it. We've all received the responses those tools send. The tone is off. The order number is wrong. The apology is hollow. The customer churns. The brand pays.

We don't believe in that. We believe in human + AI on most cases, AI alone on none. The AI does the mechanical work — read the ticket, find the order, look up the policy, draft the reply in your voice. Then you read it. Five seconds. You send it, refine it, or skip it. Always your call. Your name on every reply.

We will never auto-send a reply on your behalf. Not as an upgrade. Not as a setting. Not for anyone. It's the line we drew on day one and we won't move it.

Speed is the feature.

Delegating must be faster than doing it yourself. Otherwise the AI is just another tool in your stack you're paying to ignore.

Every design decision in the product comes back to that. The ticket loads in under a second. The draft is already there when you open it. One keyboard shortcut sends. The next ticket is queued. If we ever ship something that makes a single ticket take longer than typing the reply by hand, we've failed.

We don't replace your tools. We sit between them.

You already have a website, a payment processor, an inventory system, a mail server. You don't need a tenth platform that wants to own them. You need an inbox that connects to them.

SupportPilot reads your Shopify orders. It looks up the right tracking number from your carrier. It checks the customer's history. It knows your refund policy because you wrote it once in plain English. It drafts the reply that pulls all of that together. The data lives where it lived before. We just stop you from having to copy-paste between five tabs.

What we won't do.

• We will never train AI models on your customer data. Your tickets, your knowledge base, your tone — none of it leaves your tenant. Your data is not our product.
• We will never send a reply without your explicit click. Not in batch. Not for "low-risk" categories. Not after a trial. Never.
• We will never gate features behind upsells you didn't ask for. If a feature works in the free tier today, it works in the free tier tomorrow.
• We will never claim "100% automated" or "AI agents replace your team." That's a lie that costs your customers and your reputation. We sell time saved, not people replaced.
• We will never store more data than we need. Tickets older than your retention window are purged. Period.

Why now.

Two things changed in the last 24 months. Language models became good enough to read a customer email and understand what's actually being asked — not just match keywords. And the platforms behind your business — Shopify, Gmail, Outlook, Stripe, IMAP — opened APIs deep enough to act on the answer, not just observe it.

For ten years, "AI customer support" meant a brittle decision tree dressed up as a chatbot. That era is over. The new era isn't autonomous AI. It's an AI that drafts, and a human who decides. That's the product we're building.

Who we're for.

Stores doing 100 to 5,000 tickets a week. Founders who still answer support themselves at midnight. Small teams who can't afford Zendesk. Agencies who run support for their clients. Local administrations and back-office teams whose mail still lives on Exchange or IMAP. Anyone who'd rather keep their name on every reply than ship a robot to do it for them.

If that's you — welcome. We built this for you.