Global Innovation Group
Insights · October 29, 2026

AI Customer Service for Small Stores: What to Automate First

If you run a small online store, your support inbox is probably the same few questions in different words. Where is my order. Can I return this. Will it fit. When is it back in stock. Do you ship to me. None of them is hard to answer. Answering them at 11 p.m. on a Sunday, while you are also packing orders, is the problem.

An AI support agent can take a real share of that load, but only if you set it up in the right order. Put it on the wrong questions first and it costs you money and trust. Below is the order we recommend, plus two rules every seller with California customers should know before an automated agent talks to a buyer.

Step one: count your inbox before you buy anything

Pull the last two to four weeks of customer messages from every place they arrive: email, site chat, social DMs, and marketplace messages. Sort each one into a bucket: order status, returns and exchanges, product questions (sizing, materials, compatibility), shipping times and regions, discount or checkout problems, and everything else.

The buckets tell you what to automate. If most of your messages are order status and policy questions, an agent can answer them from data you already have. If most are one-off product questions that need someone who has handled the product, automation will help less, and you should know that before you pay for it.

Related reading: Your customer data lives in four inboxes. Here is the way out.

Automate first: answers that already exist in writing

The safest first job for an AI agent is a question whose correct answer is already written down and checkable: an order's tracking status from your store platform, your return window, your shipping regions, your exchange steps. The agent's job is to find the right fact, say it plainly, and link the policy page it came from.

This is where grounding matters. An agent that answers from your actual policy text and order data is looking things up. An agent that answers from general knowledge is guessing, and a confident guess about a refund is the most expensive kind of mistake a small store can make.

There is a real case on this point. In Moffatt v. Air Canada (2024), a British Columbia tribunal held the airline liable after its website chatbot told a customer they could apply for a bereavement fare after booking, which contradicted the airline's own policy page. The tribunal rejected the argument that the airline was not responsible for what its chatbot said, writing: "It makes no difference whether the information comes from a static page or a chatbot." That is a Canadian small-claims decision, not U.S. law. The lesson travels anyway: what your agent says, your store said.

Related reading: AI for small shops and online brands

Keep human: anything that changes money or a promise

Refund exceptions, damaged or wrong items, chargebacks, upset customers, wholesale requests, and anything touching a customer's health or safety should go to a person, with the conversation attached so the customer does not have to repeat themselves. The agent can collect the order number and photos, then hand off.

Shipping delays belong in this bucket for a legal reason. The FTC's Mail, Internet, or Telephone Order Merchandise Rule says that when you cannot ship within the time you stated (or within 30 days if you stated no time), you must offer the buyer a choice: accept the delay or cancel for a prompt refund. Any revised ship date you give also needs a reasonable basis. An agent that improvises a new date to calm someone down can put you on the wrong side of that rule. Let it send a delay notice you have approved, with the cancel option included, and let a person set the new date. This is general information, not legal advice.

Label the agent as automated

California's bot disclosure law (Business and Professions Code section 17941) makes it unlawful to use a bot to communicate with a person in California online with the intent to mislead them about its artificial identity in order to incentivize a sale. The same section says you are not liable under it if you disclose that it is a bot, and the disclosure has to be clear and conspicuous.

The practical version is simple. Name the agent as an automated assistant in the chat window and in its first message, and give the customer an obvious way to reach a person. It costs nothing, and it keeps the agent honest about what it is.

When an AI agent is the wrong purchase

If your store gets a handful of messages a day, saved replies, a clear FAQ page, and your platform's order-status page may be all you need. If most of your messages need product expertise only you have, the better first step is writing that expertise down (sizing notes, compatibility tables, care instructions) so a person or an agent can answer from it later.

An agent also cannot fix whatever is generating the tickets. If one product drives most of the return questions, the fix might be a better photo or a clearer size chart, not a faster reply.

What a sensible first install looks like

Narrow on purpose: one channel, the order-status and policy buckets only, answers grounded in your real policy pages and store data, a visible automated-assistant label, and a clean handoff to a person for everything on the keep-human list. Before it answers a live customer, test it against real past questions and read every answer.

At GIG, that support agent is usually what our Foundation plan covers, at a published floor of $800/mo, month-to-month, with final scope in writing after a free consult. You keep the accounts, the policy documents, and the playbook.

Related reading: AI systems · Inside the $1,500 AI Audit

Common questions

Can an AI agent process refunds on its own?

It can be connected to do that, but we do not recommend it as a first step. Let the agent collect the order number, the reason, and photos, then route the refund decision to a person. Refunds are where a wrong answer costs real money.

Do I have to tell customers they are chatting with AI?

In California, Business and Professions Code section 17941 makes it unlawful to use a bot to mislead someone about its artificial identity to incentivize a sale, and disclosing that it is a bot is the safe harbor. Labeling the agent clearly is the simple way to stay on the right side of it. This is general information, not legal advice.

How many messages does a store need before an AI agent is worth it?

There is no honest universal cutoff. Count your messages for two to four weeks and look at the mix. If routine order-status and policy questions are a large share and they are eating hours you would rather spend elsewhere, it is worth a conversation. If not, saved replies and a better FAQ page may be enough.

Sources

Global Innovation Group installs systems like this for small businesses at published floors, month-to-month, in tools you own — and says “not yet” when the numbers don’t work.

Take the free 2-minute leak check