An AI support assistant can answer customers instantly at any hour, reduce queues and free human agents for complex cases. A poorly launched one damages trust and creates legal risk. This guide covers the essential steps, whether you use a ready-made platform or build your own.

Step 1 — Choose the first use cases

Analyze your support tickets: which questions are most frequent, simple and well documented? Typical starting points:

  • order status and delivery questions;
  • returns and refund policies;
  • account and password help (with secure verification);
  • product information and setup;
  • opening hours, locations and contact details.

Avoid starting with complaints, billing disputes or anything involving legal or safety consequences.

Step 2 — Prepare the knowledge base

AI assistants usually answer using retrieval-augmented generation: they search your documentation and generate answers from it. The quality of answers depends on the quality of content.

  • Update and correct help articles; remove contradictions.
  • Write clear policies with explicit conditions and exceptions.
  • Fill gaps revealed by ticket analysis.
  • Assign owners to keep content current.

See our explainer on how retrieval-augmented generation works.

Step 3 — Define behavior and guardrails

Write clear instructions for the assistant:

  • answer only from approved sources, and say when it doesn’t know;
  • never invent policies, prices or promises;
  • maintain your brand tone;
  • refuse out-of-scope requests politely;
  • protect personal data and verify identity before account actions.

Step 4 — Design escalation

Make it easy to reach a human: a visible button, automatic handover after repeated failures or when customers express frustration, and transfer of the conversation history so customers don’t repeat themselves.

Step 5 — Connect actions carefully

If the assistant will take actions (refunds, cancellations, changes), start with low-risk ones, set limits (such as maximum refund amounts), require confirmation from the customer and log every action.

Step 6 — Test thoroughly

Build a test set of real questions, including tricky ones:

  • questions with exceptions (“can I return a sale item after 30 days?”);
  • ambiguous or incomplete questions;
  • attempts to manipulate the bot into unauthorized discounts or rude replies;
  • multiple languages if relevant.

Review answers for accuracy, tone and correct escalation. Re-test after changing content, prompts or models.

Step 7 — Launch gradually

Start with a portion of traffic or a single channel, monitor closely and expand as quality is proven.

Step 8 — Monitor and improve

Review samples of conversations weekly, track resolution and satisfaction, analyze unanswered questions to improve content, and keep humans responsible for quality.

Companies are accountable for what their assistants say. In Moffatt v. Air Canada (2024), a tribunal held the airline liable for incorrect fare information from its chatbot. Accurate content and good guardrails are not just quality issues — they are legal ones.

Example instructions for a support assistant

A starting point for the assistant’s system instructions might look like this:

You are the support assistant for [company]. Answer questions using only the provided help-center content. If the answer is not in the content, say you don’t know and offer to connect the customer with a human agent. Never promise refunds, discounts or exceptions beyond the written policy. Keep answers short, friendly and clear, and link to the relevant help article. Before discussing account details, ask the customer to verify their identity using the secure login. If the customer is upset, has asked twice for a human, or mentions legal action, safety or a complaint, hand over to a human agent with a summary of the conversation.

Adapt the instructions to your brand and policies, and test how the assistant handles each rule.

Common mistakes

  • Launching before cleaning up outdated help content.
  • Hiding the option to reach a human.
  • Measuring only deflection — the share of contacts the bot handles — rather than resolution and satisfaction.
  • Letting the assistant take actions without limits or logs.
  • Never reviewing real conversations after launch.

What to watch next

  • Customer support platforms adding autonomous agent features.
  • Evaluation tools for support assistant accuracy.
  • Voice-based AI support on phone lines.
  • Regulation on disclosure of AI in customer interactions.

Key takeaways

  • Start with frequent, simple, well-documented questions.
  • Answer quality depends on an accurate, up-to-date knowledge base.
  • Define guardrails and make escalation to humans easy.
  • Limit and log actions, and test with tricky real-world questions.
  • Launch gradually and monitor continuously; companies are liable for bot answers.

Frequently asked questions

Should I build or buy a support chatbot?

Most businesses start with a platform integrated with their help desk. Custom builds make sense for unique needs or very large volumes.

How long does a launch take?

A focused first version can take weeks; most effort goes into preparing content, testing and integration.

Should customers be told they are talking to AI?

Yes. Transparency builds trust, and some laws, including the EU AI Act, require disclosure that users are interacting with an AI system.