AI email reply templates for small business: drafts you can trust

Updated October 21, 2026 · App names checked against vendor documentation; vendors rename things, so search the step picker for the key word if a name differs.

Why most AI email replies go wrong

Ask a chatbot to answer a customer email and it will happily produce something fluent, friendly and wrong. It makes up a shipping time, a price range or a refund policy that sounds reasonable but isn't yours. The fix isn't a cleverer prompt. Give the AI one source of truth (your FAQ) and tell it to stop and hand the email to you when the answer isn't in there.

Set up that way, AI is good at the boring part: greeting the person by name, answering the actual question in the first sentence, and keeping the tone consistent. You stay in charge of anything that needs judgement.

Step 1: Write your FAQ doc (this is most of the work)

Open a Google Doc called something like Customer FAQ: AI source. Go through your sent mail from the last month and copy the questions you answer again and again. For most small businesses that's 15–25 questions. Write each answer the way you'd want it sent, including links.

Q: How soon can you come out? / How long does shipping take?
A: [your honest answer + link to booking or shipping page]

Q: How much does [service] cost?
A: [a range, or: It depends on X. We quote after a quick call: [booking link]]

Q: How do I reschedule or cancel?
A: [policy, notice period, link]

Q: What's your refund or guarantee policy?
A: [policy in plain words]

Q: Do you serve [area] / ship to [country]?
A: [answer]

Q: What should I do before you arrive / before my appointment?
A: [prep checklist]

Keep answers short and specific. If an answer depends on details (big jobs, custom orders), say so in the FAQ, and the AI will repeat that instead of inventing a number.

Step 2: The core AI reply prompt

This prompt does the heavy lifting. Paste it into the AI step of your automation and map in the FAQ text and the customer's email. The NEEDS HUMAN line is the safety valve: when the FAQ doesn't cover the question, the AI writes a short holding reply and flags it for you.

Business: [Your business name]. [One sentence on what you do and where.]
Tone: [friendly, plain-spoken, no jargon]. Sign off as: [Your name].

You draft customer email replies. Use ONLY the FAQ below. If the FAQ does not clearly answer the question, do not guess. Write a short reply saying we'll check and get back to them within [timeframe], and start your output with "NEEDS HUMAN:".

FAQ:
{{FAQ Document Text}}

Customer email:
From: {{From Name}}
Subject: {{Subject}}
{{Body Plain}}

Rules:
- Greet them by first name. Answer the question directly in the first sentence.
- Under 120 words, plain text, no subject line.
- Never make up prices, dates, order details, tracking numbers or policies.
- No legal, medical or financial advice.
- End with the sign-off name only.

Step 3: Add situation templates for the tricky emails

Some emails need a specific tone, not just a fact. Add one of these blocks under the rules in the core prompt, or build a separate automation path for each type (Paths in Zapier, a Router in Make, a Switch node in n8n).

PRICE QUESTION
If they ask about price and the FAQ gives a range, give the range and explain what changes it. If there's no range, say we quote after a short call and include [booking link]. Never estimate.

RESCHEDULE REQUEST
Confirm we can help, give the reschedule link [link] and our notice policy from the FAQ. Do not confirm a specific new time.

COMPLAINT OR UNHAPPY CUSTOMER
Start output with "NEEDS HUMAN:". Draft a calm, non-defensive reply: acknowledge the problem in their words, apologise that it fell short, say [Your name] will personally follow up by [timeframe]. No excuses, no refunds or discounts, no arguing about facts.

WHERE IS MY ORDER
If no tracking details are included in the data provided, start output with "NEEDS HUMAN:" and say we're checking the status now.

Complaints should always come to you. An AI-drafted apology is fine as a starting point, but read it and send it yourself.

Step 4: Build the automation (draft mode)

First, decide which emails go in. The simplest option is a Gmail label called Support: either apply it by hand as you skim your inbox, or have a filter or an AI inbox sorter apply it for you.

Zapier:

1. Trigger: Gmail › New Labeled Email, label Support.
2. Action: Google Docs › Get Document Content for your FAQ doc.
3. Action: ChatGPT (OpenAI) › Conversation (or AI by Zapier) with the prompt above. Map in the FAQ text, sender name, subject and body.
4. Action: Paths by Zapier: if the output starts with NEEDS HUMAN, send yourself a Slack or Gmail alert; otherwise continue.
5. Action: Gmail › Create Draft Reply on the same thread, using the AI text as the body.

Make: Gmail › Watch emails (filtered to your label) → Google Docs › Get Content of a Document → OpenAI › Generate a response → Router (NEEDS HUMAN or not) → Gmail › Create a draft email, with the thread set so it lands as a reply.

n8n: Gmail Trigger (label filter) → Google Docs node (Get) → OpenAI node → IF node checking for NEEDS HUMAN → Gmail node to create a draft reply, or a notification to you.

Drafts never go out on their own. You open Gmail, read the reply, fix anything, and press send. Most people stay in draft mode for good, because checking a draft takes seconds and writing one takes minutes.

Step 5: Test it with your own emails

1. Send yourself five realistic test emails from a personal address: two the FAQ answers, one about price, one complaint and one oddball question.
2. Label each one Support and check the drafts.
3. The oddball and the complaint should both come back flagged NEEDS HUMAN. If they don't, tighten the rules.
4. Look for anything the AI stated that isn't in your FAQ. If you find something, add "Do not mention X" to the rules or fix the FAQ.

Keep it getting better

• When you heavily edit a draft, update the FAQ. The doc is the system; the AI just reads it.
• Keep the FAQ under a few pages. Once it gets long, n8n's AI Agent node with a retrieval tool is the next step, but most small businesses never need it.
• Don't send what the AI doesn't need. Name, subject and body are enough. Never paste card numbers, passwords or health details into a prompt.
• Check costs once a month. AI usage is billed per request through an API key (separate from a ChatGPT subscription). Short replies cost very little, but check your provider's current pricing.

Related automations

Reply drafts work best alongside AI lead follow-up, which writes a first reply to new inquiries, and AI email sorting, which decides which emails need a reply in the first place. Not sure which tool to use? See n8n vs Zapier vs Make.