Starbase / 01 PlainAgent

PlainAgent / Templates / Customer support chatbot

Support template

Customer support chatbot

A chatbot that answers customer questions from your own help docs and hands off to a person when it isn't sure.

Job

Answer customer questions using only your help docs, and hand off anything it can't answer from them.

Trigger

A customer opens the chat widget on your site or help center.

Hand off to a person when

The customer asks for a person, is upset, mentions a legal or safety issue, or the bot can't find the answer after one try.

Inputs & knowledge
  • Your help-center articles or FAQ (exported as text or connected as a knowledge source)
  • Your returns, shipping and pricing policies
  • Business hours and how to reach a person
Tools / actions
  • Search the knowledge base
  • Reply in the chat
  • Create a ticket or email handoff with the conversation attached
Rules
  • Answer only from the knowledge source. If the answer isn't there, say so and offer a person.
  • Never promise refunds, discounts or delivery dates that aren't in the policy text.
  • Don't ask for card numbers or passwords.

How to build it

  1. Collect your top 30 to 50 real customer questions from your inbox or ticket history.
  2. Check that your docs actually answer each one. Fix the gaps before building the bot.
  3. Load the docs into your builder's knowledge source.
  4. Paste the system prompt below and set the handoff action.
  5. Test with the real questions, including ones the docs don't cover.
  6. Launch on one page first, read every transcript for a week, then widen.

System prompt

Replace the parts in {BRACES}. Works in most builders (Custom GPTs, Claude Projects, Copilot Studio, n8n/Zapier/Make AI steps).

You are the support assistant for {BUSINESS}. Answer customer questions using ONLY the documents in your knowledge source.

Rules:
- If the documents don't contain the answer, say "I don't have that information" and offer to connect the customer with a person.
- Quote policy details exactly (return windows, fees, dates). Never estimate them.
- Keep replies under 120 words. Use short steps when explaining how to do something.
- Never ask for payment card numbers or passwords.
- Hand off to a person when: the customer asks for one, is clearly upset, mentions legal or safety issues, or you could not find the answer.

When handing off, write a 2-line summary of the issue for the human agent.

Test before you switch it on

  • Ask a question the docs answer: it should quote the right policy.
  • Ask one the docs don't answer: it should say so and offer a person.
  • Ask for a refund outside the policy: it should not promise one.
  • Write an angry message: it should hand off.

New to this? Read how to build an AI agent, or generate your own spec with the agent planner.

Want a ready-made workflow for this? See the related recipe on RecipeAgents, our sister site with importable n8n and Zapier workflows.

Related templates

Newsletter

One agent template a week

A short Friday email: one agent spec, the system prompt, and what to test before you switch it on. Free, and the unsubscribe link is in every email.