Changes this week

OfficeBy Serchai · Published on · 4 steps

How to set up your store's customer service with AI

Guide to automating customer service with AI: documentation the agent can read, an agent with Tidio, a knowledge base with FastGPT and weekly review.

ToolsTidio · FastGPT · Claude
Stack costFrom $41.17 + 99 CNY/mo
Updated

00Tools you will use

Stack: From $41.17/mo + 99 CNY/mo
Card 01/03 · Store agentFREE + $24.17

Tidio

3.6Fair

AI chat that resolves your store's repeat questions without a human agent.

PriceFree + from $24.17
JobChat, tickets and answers about specific orders, read from your documentation.
Read the review ↗
Card 02/03 · DocumentationFREE + $17

Claude

4.0Good

Anthropic's AI assistant for writing, analysing and thinking through documents.

PriceFree + from $17
JobTurns your notes into concrete answers before anything gets connected.
Read the review ↗
Card 03/03 · Knowledge baseFREE + 99 CNY

FastGPT

3.8Fair

Open-source platform for building RAG chatbots on your documents.

PriceFree + from 99 CNY
JobAnswers over manuals and specifications, sitting behind the agent.
Read the review ↗

TLDR: The bulk of a store’s queries are five repeat questions whose answers are already written on your site. Tidio puts an agent that resolves them by reading your documentation and escalates the rest to a person, from $24.17 a month. What decides the result is not the tool, it is rewriting those pages properly before connecting it, and reviewing weekly what the agent could not answer.

his guide is for anyone selling online watching customer service eat their evenings: small shops without a support team, direct-to-consumer brands, businesses where the owner answers messages at eleven at night. The goal is not removing human contact, it is having people handle what deserves a person.

The warning upfront: an agent connected over bad documentation answers badly at scale, which is worse than not answering. The real work sits in steps one and two.

1. Sort the questions you actually receive

Before touching any tool, open your inbox from the last two months and count. Do not estimate: count. The real list almost always looks like this:

The agent's syllabus · Queries by frequency2/5 answered on the site
Where is my order?IntegrationNot connected
Shipping times by zoneShipping pageConcrete
How to return and who pays the way backReturnsVague
Availability of sizes or variantsCatalogConcrete
Warranty status and scopeWarrantyVague

The right-hand column is the work of steps 2 and 3, in that order.

Note next to each what you normally answer. That document is the agent’s syllabus and, incidentally, reveals something uncomfortable but useful: most of those questions exist because your site does not answer them clearly.

Questions that appear once in a blue moon do not belong on this list. Automating the exception is the mistake that makes an agent look stupid exactly when the customer genuinely needs help.

2. Rewrite the documentation the agent will read

This is the step that decides accuracy. An agent answers with what it finds written, so if your returns page says “we accept returns within a reasonable period”, the agent will serve that vagueness to everyone.

Rewrite your three or four key pages with concrete answers: exact return window in days, who pays return shipping, what happens if the product arrives defective, delivery times by zone, what to do if the order does not arrive. Every concrete fact you write is a query you stop receiving, whether the agent answers it or the customer reads it directly.

To speed up the rewrite, Claude turns your notes into clear answers, from $17 a month and with a permanent free tier. Precision beats variety here: every sentence you write is a commitment a customer can hold you to. The review is yours, because you are writing commercial commitments and approximation has no place there.

3. Build the agent with Tidio

Tidio is the piece the customer sees: store chat, tickets and an AI agent that answers by reading your documentation. It connects with the usual commerce platforms, which lets it answer about specific orders rather than only general policy. Free plan and a card-free trial, with paid plans from $24.17 a month.

The most important configuration decision is when to escalate to a person. The temptation is letting the agent insist until it resolves, and that is a mistake. Configure early escalation, especially on issues with orders already paid for.

A customer would rather wait ten minutes for a human than receive three answers that do not help.

The criterion behind the agent's configuration

4. Review weekly what it could not answer

Here is the habit that turns a chatbot into a system that improves. Every week, a short pass over the conversations the agent escalated:

The weekly cycle

01The escalationsThe conversations the agent could not close, one by one.
02The sortingLegitimate question for humans, or gap in your documentation.
03The gap writtenWhat was missing goes into the page it belongs to.
04The load droppingNext month arrives with fewer of the same queries.

That cycle has a valuable side effect: your public documentation improves, so queries also drop among people who never open the chat.

If your product is technical and you need answers over manuals, specifications or extensive documentation, FastGPT builds a knowledge base on your own documents with more control at low cost, from 99 yuan a month, billed in its own currency. It sits behind the customer-facing agent as the layer that knows the product.

With support solved, the freed time usually goes to acquisition: the product photos and catalog descriptions guides cover that. The whole sector lives in AI for e-commerce.

Common mistakes

Connecting the agent over vague documentation. It multiplies your ambiguity across every customer at once. Write first, automate second.

Configuring the agent never to escalate. It saves billable conversations and destroys trust. Early escalation is a feature, not a failure.

Not reviewing the conversations. Without the weekly cycle, the agent stays frozen on what it knew on day one while your catalog and policies change.

Automating serious incidents. A lost order or a duplicate charge gets a person. The saving there costs a fortune in reputation.

Frequently asked questions

How many queries can the agent resolve?

With concrete, well-written documentation, the bulk of repeat questions. The proportion depends far more on your shipping and returns pages than on whichever AI model sits underneath.

How much does it cost?

Tidio has a free plan and a card-free trial, with paid from $24.17 a month. The important warning is that it bills by conversations, so measure your real volume during the trial before choosing a plan.

Do customers reject talking to an AI?

What they reject is not getting their problem solved. An agent that answers quickly and well, and hands off to a person as soon as it stalls, generates no complaints. One that insists with generic answers does.

Do I need to integrate it with my store platform?

That is what separates answering general policy from answering about the specific order in question. It works without integration, but at half its usefulness.

The steps, in short

  1. Sort the questions you actually receive

    Pull the real list of repeat queries from your inbox and rank them by frequency.

  2. Rewrite the documentation the agent will read

    Turn your shipping, returns and warranty pages into concrete, unambiguous answers.

  3. Build the agent with Tidio

    Connect the chat to your store, load the documentation and define when it must hand off to a person.

  4. Review weekly what it could not answer

    Use escalated conversations as a map of what your documentation is missing and close the gaps.

Office

Related guides

Which tool will you pick? See the full office ranking.

See the category ranking
What do you want to do?
Assisted decision · ES/ENRequirements · price · limitations · dated sources

What do you want to do?

Tell us in the same words you would use with another person.

We keep a sanitised query for 90 days to improve the engine. Privacy.