AI Customer Support for a One-Person Business: Setup Guide

Support in a one-person business means every channel lands on you: email, the chat bubble on your site, app-store reviews, the odd DM. AI customer support for a one person business works when it answers the questions you have already answered a hundred times, drafts the rest for you, and hands anything involving money, anger or doubt straight back to you. This guide gives you a setup table by volume and channel with prices as of October 2026, an escalation template that defines exactly when the AI must stop, and reply macros you can paste today.

Prices come from each vendor’s official pricing page, read on October 19, 2026. For more setups like this, see the AI workflows category.

What AI support can and cannot do when you are the whole team

Think of support as three jobs. Answering known questions. Drafting replies to new ones. Deciding.

AI is good at the first two. It can match “how do I restore my purchase?” to the paragraph you wrote about it, and it can turn a rambling bug report into a clean draft reply plus a note for your to-do list. It is bad at the third job, and the third job is where a small business wins or loses a customer: approving an exception, judging whether a complaint is fair, spotting that one email is really a legal problem.

My own setup is small. I have shipped apps, so app-store users write in, and I have sold an ebook directly. I run several online businesses alone on Claude, GPT and Hermes, with Google Calendar holding the day together. The rule I’d apply to support follows from that: the AI reads and drafts, and a person decides and sends.

One boundary for this article: I have not run Intercom, Zendesk, Help Scout, Tidio, Crisp, Chatbase or Gorgias in my own business. Everything about those tools below is based on their pricing pages and documentation, not on my use.

Start with the questions you already answer

Before any tool, write one document. Call it the support source doc. Every AI support product on the market asks for something like it, under names like knowledge base, guidance or training data, and a general assistant like Claude needs it just as much.

Put five things in it:

• Your refund policy, in plain words, with the exact cases where you say yes.
• The ten questions you answer most, each with the answer you would give.
• Known bugs or limits, and the workaround for each.
• Where each product is sold (your store, App Store, Google Play), because that decides who can refund.
• The handoff rules from the escalation template below.

This doc does more for answer quality than any vendor choice. A bot that has no written refund policy will improvise one. That is the failure you are trying to prevent.

The setup table: what to automate at your volume and channel

This table maps the channel and rough volume you have to the setup that fits. “What stays human” is the same column on every row on purpose. Prices are as of October 2026, from each vendor’s pricing page as displayed on October 19, 2026; several pages show annual billing by default, so month-to-month can cost more.

Two notes the table cannot hold. Gorgias prices its helpdesk by ticket volume, from 50 to 5,000 tickets a month, not per agent. It charges for its AI Agent only when it resolves a conversation. Its pricing page did not show dollar figures in the version I could read, so check it directly if you sell on Shopify. Chatbase lists no free plan, only a 7-day trial, and its credits count messages rather than conversations.

What 50 AI resolutions a month costs

Per-resolution pricing looks cheap until you add the base plan. Here is the same workload, 50 conversations the AI closes alone in a month, priced from the pages above for one person, as of October 2026.

Read the definitions before comparing. Fin counts a resolution when the customer asks for no further help after Fin’s last answer. Help Scout charges once per conversation that AI Answers resolves without human help, and lets you set a monthly spending cap that switches AI Answers off for the rest of the cycle. That cap is worth setting on day one.

Free trials change the first month. Fin offers 14 days with unlimited outcomes and no card required. Help Scout gives a 3-month trial of unlimited AI Answers resolutions from account creation.

Email only, low volume

Do not buy a helpdesk yet. Turn on Gmail templates, save an acknowledgement (“Got it, I reply within one business day”), and set a filter on your support address to send it automatically. Gmail Help confirms a filter can send a template as an automatic reply.

Then draft with the assistant you already pay for. Paste the customer’s message and your source doc, ask for a reply under 120 words, and send it yourself. If your inbox mixes support with everything else, the AI email automation setup covers the filters and prompts for the rest of the mail.

App-store reviews and in-app messages

App users have two doors: a review, which is public, and your support contact. Apple’s App Review Guidelines (1.5) ask that your app and its Support URL include an easy way to contact you. Make that a real address that lands in the same inbox as everything else.

For reviews, App Store Connect lets the Account Holder, an Admin, or a user with the Customer Support role respond. Only one response per review shows on your product page, edits are marked as edited, and a response can take up to 24 hours to appear. Have AI draft the reply. Post it yourself, because it is public and it stays.

This is the channel I know firsthand. The useful AI job here is sorting: is this a bug, a refund request, a feature wish, or someone who missed a setting? Each goes somewhere different, and the refund one goes somewhere you may not control (see the refund table below).

Website chat

Chat creates an expectation of a fast answer. If you cannot be there, the bot’s main job is to answer from your docs and, when it cannot, take an email address and promise a reply time you will meet.

Tidio and Crisp both start free, but the free tiers differ in the part that matters: Crisp’s free plan includes no AI credits, while Tidio’s free plan includes 50 billable conversations a month and a lifetime 50 free Lyro conversations. If you want AI answers in chat for free, Tidio’s tier is the one that includes them, as of October 2026.

Helpdesk with an AI agent

Move here when one inbox plus chat stops working: you lose threads, or you want a public help center the AI can read. If your volume is low, Help Scout’s per-resolution model with a spending cap is the most predictable of the options above. If you already run Zendesk or Gorgias, Fin can sit on top, but budget for its 50-outcome minimum.

When AI must hand off to you: the escalation template

Paste this block into your helpdesk’s AI guidance field, a Claude Project’s instructions, or a custom GPT. It is written so the AI has no room to negotiate with itself.

SUPPORT RULES — follow before answering anything.

Answer only from the SUPPORT SOURCE DOC. If the answer is not in it, hand off.

Hand off to the owner (do not answer, do not promise) when the message:
1. Asks for a refund, credit, discount, chargeback, or exception to any policy.
2. Shows anger, threatens a review, a dispute, or legal action, or mentions a lawyer, regulator, or the press.
3. Is about account access, a payment that failed or was charged twice, or personal data (export, deletion, privacy).
4. Reports a bug you cannot match to a known issue in the doc.
5. Asks for a human, or repeats the same question after your answer.
6. Involves safety, health, a minor, or anything you are less than sure about.

When you hand off:
- Tell the customer a person will reply, and give the reply time from the doc.
- Never state a refund decision, a price change, or a date you were not given.
- Write a one-line summary for the owner: who, what they want, which rule triggered, order or purchase channel if known.

Always say you are an AI assistant in your first reply.

Rule 5 matters more than it looks. A customer who asks the same thing twice has already decided the bot failed. Continuing to answer makes it worse.

Copy-paste reply macros

These are for you or the AI to send at the handoff. Replace the brackets. Keep them short; long apologies read as scripts.

Refund request, your own store:

Hi [name], thanks for writing. I handle refunds myself, so I'm looking at your order now and will reply by [day]. If you can, send the order number or the email you bought with.
— [your name]

Refund request, App Store purchase:

Hi [name], sorry it didn't work out. App Store purchases are refunded by Apple, not by me. You can request one at reportaproblem.apple.com: sign in, choose "Request a refund," pick the purchase. If something in the app is broken, tell me what you saw and I'll fix it.
— [your name]

Bug report:

Hi [name], thanks for the detail. I haven't seen this one before, so I've logged it. Could you tell me your device, OS version, and app version? I'll write back when I know more, by [day] at the latest.
— [your name]

Angry message or a threat to leave a bad review:

Hi [name], I read your message and I'm taking it from here personally. I want to fix this properly, so I'll reply by [day] with what I can do.
— [your name]

Account, billing, or data request:

Hi [name], this needs a person, so I've picked it up myself. For your security I'll only discuss account details by reply to this email. Expect an answer by [day].
— [your name]

“I want to talk to a human”:

Hi [name], you've got one. I'm [your name], I run [business], and I'll reply to your message myself by [day].

Notice what none of them do: promise an outcome. They promise a reply time. That is a promise one person can keep.

Refunds: who actually controls them

The most common support mistake for app sellers is promising a refund you cannot issue. Who holds the button depends on where the customer paid.

Google adds one detail worth knowing: if the payout already went out, a refunded amount is deducted from a future payout. The App Store and Google Play payouts guide covers how refunds show up in payouts and year-end forms.

Physical goods add a federal layer. The FTC’s Mail, Internet, or Telephone Order Merchandise Rule expects you to ship within the time you state, or within 30 days if you state none. If you cannot, you must offer the buyer the choice to accept a delay or cancel for a prompt refund. After a cancellation, cash-type payments are refunded within seven working days, and credit you extended is handled within one billing cycle. The FTC guide says the Rule does not cover services. Put those deadlines into your source doc so the AI never promises something slower.

This is not licensed legal advice. I am not a lawyer; read the FTC guide linked above for your own case.

Telling customers they are talking to AI

The FTC’s artificial intelligence page, as of October 2026, lists enforcement actions against companies that made deceptive claims about AI, but no general federal rule that a support bot must identify itself. The FTC Act still bars unfair or deceptive practices, and a bot that lets a customer believe a person approved their refund is exactly the kind of thing that goes wrong.

Disclose anyway. Your first AI reply should say it is an AI assistant and that you, a person, handle refunds and anything unusual. If you sell into other countries or states, check their rules on bots; this article only covers the FTC.

Weekly upkeep: fifteen minutes that keep the bot honest

AI support decays when nobody reads its transcripts. Once a week, look at three things:

• Every handoff. Was the trigger right? If the same question escalates twice, write its answer into the source doc.
• Every AI answer a customer replied to with “that’s not what I asked.” Those are gaps in your doc, not in the model.
• Your spend against any cap you set.

I put this kind of recurring check on Google Calendar as a fixed block, because a review with no time slot does not happen. If you already run a weekly review, add support to it; the Claude for business operations guide covers using Claude for that kind of recurring pass.

If a tool’s AI keeps answering outside your doc after two rounds of fixes, switch it to draft-only. A bot that drafts for you is still most of the time saved.

This week, write your support source doc and paste the escalation template under it. Everything else in this article can wait until that file exists.