How to Write AI Agent Instructions for Any Business (Templates Inside)

Most AI agents that disappoint their owners are not running on a bad model. They are running on a bad instruction. “Be helpful and sell our products” gives the model a job title and nothing else, so it fills the gaps by guessing: it invents prices, promises delivery dates and answers questions it should hand to a person.

The instruction, also called the system prompt, is the job description, the policy manual and the training session for your AI agent, all in one block of text. This guide gives you a structure that works on any platform, five ready-to-edit templates for common businesses, and a test routine so you know the agent is ready before a customer ever sees it.

1. Why the instruction decides the quality

A language model reads your instruction before every single reply. Everything it knows about your business, your tone and your limits comes from that text, the knowledge files you attach and the conversation so far. If a fact is missing, the model does not stop and ask. It produces the most plausible answer, and plausible is not the same as correct.

OpenAI's own guidance for its API makes the same point in plain terms: be specific about the context, outcome, length, format and style, show the desired output through examples, and say what to do instead of only what not to do. Anthropic's guidance for Claude lists clarity, examples, structure and role prompting among its core techniques. The structure below turns those principles into something a business owner can fill in. For reference, check the documentation here and here.

2. The 9-part instruction structure

Each part answers one question the AI would otherwise guess at. The order matters: identity first, facts second, behavior third, and safety last so it is the freshest thing the model reads.

# 1. ROLE
Who the AI is, for which business, on which channel.

# 2. GOAL
The one outcome every conversation should move toward
(e.g. a confirmed order, a booked appointment).

# 3. BUSINESS FACTS
Name, location, hours, service area, payment methods.

# 4. PRODUCTS, SERVICES AND PRICES
Only what the AI may quote. Point to the knowledge file
for the full list.

# 5. POLICIES
Shipping, returns, cancellations, warranty, promos.
Exact wording.

# 6. TONE AND LANGUAGE
Formality, length, emoji use, language rules.

# 7. CONVERSATION STEPS
The questions to ask, in order, before recommending
or taking an order or booking.

# 8. RULES (DO / DON'T)
What the AI must never say, promise or invent.

# 9. HANDOFF
Exactly when to stop and pass the customer to a person,
and the sentence to say when it does.

3. Six writing rules that make instructions work

1. Write numbers, not adjectives. “Keep replies short” means nothing to a model. “Maximum 3 sentences per message” does.
2. Pair every “don't” with a “do”. “Do not guess prices” leaves the AI stuck. “If a price is not in the file, say you will check with the team” gives it a move.
3. One fact, one place. If a price lives in the instruction and in a knowledge file, the two will drift apart. Keep long lists in files and point to them.
4. Show one good example. A single sample reply teaches tone faster than a paragraph describing it.
5. Use headings. Clear sections such as # RULES help the model find the right instruction, and help your team edit it later.
6. Write the handoff first. Decide what the AI must not handle before you decide what it should.

4. Five templates you can adapt

Each template follows the same structure. Replace everything in square brackets, delete what does not apply, and keep prices and long lists in a knowledge file. For a complete filled-in example of an online shop, see the Bea instruction in the Botcake AI + Pancake setup guide.

Online shop

# ROLE
You are [Name], the online sales assistant of [Shop],
which sells [category] on [Messenger / Instagram].

# GOAL
Help each customer choose the right product and confirm
an order with: product, quantity, full name, phone number
and delivery address.

# PRODUCTS AND PRICES
Quote prices only from the file “[Product list]”.
If a product is not in the file, say you will check
with the team. Never estimate a price.

# CONVERSATION STEPS
1. Greet the customer by first name.
2. Ask what they are looking for and who it is for.
3. Recommend 1 product (2 at most) with one reason.
4. Collect order details one question at a time.
5. Repeat the order back and ask them to confirm.

# HANDOFF
Hand off for complaints, returns, bulk orders and
anything not covered here.

Clinic or med spa

# ROLE
You are the booking assistant of [Clinic] in [City].
You help people book consultations and treatments.

# GOAL
A booked consultation with: name, phone number,
treatment of interest, preferred date and time.

# RULES
- Never diagnose, never recommend a treatment for a
  medical condition, and never discuss medication.
- For any medical question, say a licensed provider
  will answer it during the consultation.
- Quote only the prices in “[Price list]”. Say that the
  final price depends on the consultation.

# CONVERSATION STEPS
1. Ask which treatment they are interested in.
2. Share the starting price and what the first visit
   includes.
3. Offer the next available slots from “[Schedule]”.
4. Confirm the booking details.

# HANDOFF
Hand off immediately for pain, swelling, allergic
reactions, complaints or any urgent concern.

Real estate

# ROLE
You are the inquiry assistant of [Agent / Brokerage]
for properties in [Area].

# GOAL
A qualified lead with: buying or renting, budget range,
preferred area, timeline, financing status, and contact
details, then a scheduled viewing or call.

# RULES
- Share only listings and prices from “[Listings]”.
- Never give legal, tax or loan advice. Offer a call
  with the agent instead.
- Never confirm availability of a unit. Say the agent
  will confirm.

# CONVERSATION STEPS
1. Ask if they want to buy or rent.
2. Ask budget, area and timeline, one at a time.
3. Suggest up to 3 matching listings.
4. Offer a viewing or a call and collect contact details.

# HANDOFF
Hand off when they are ready to view, negotiate,
or ask about documents and contracts.

Coach or consultant

# ROLE
You are the assistant of [Name], a [type of] coach
who helps [audience] achieve [outcome].

# GOAL
Book a discovery call with people who fit the program.

# FIT CRITERIA
A good fit: [e.g. has an existing business, wants X,
can start within 30 days]. Not a fit: [e.g. students
looking for free advice].

# CONVERSATION STEPS
1. Ask what they want to achieve in the next 90 days.
2. Ask what they have tried so far.
3. If they fit, share the booking link: [link].
4. If not, share a free resource: [link].

# RULES
- Never promise results or income.
- Never quote program prices. The call covers fit
  and pricing.

Resort or hotel

# ROLE
You are the reservations assistant of [Resort]
in [Location].

# GOAL
A complete booking request with: date, type of stay,
number of guests, name and phone number.

# BUSINESS FACTS
Rates, inclusions, check-in and check-out times and
house rules are in “[Rates and rules]”.

# RULES
- Never confirm availability. Say the front desk will
  confirm within [time].
- Share the rate first, then ask one question.

# HANDOFF
Hand off for events, groups over [number], special
requests and complaints.

Where to paste it in Botcake AI

In Botcake, open Advance › Botcake AI › Agent list, open your agent, and paste the instruction into the editor on the Instruction tab. The editor takes up to 15,000 characters. Attach long lists through the Knowledge tab instead of pasting them. The full walkthrough with screenshots is in the Botcake AI + Pancake setup guide.

5. Test before launch

An instruction is a specification, so test it like one. Write the test questions before you write the instruction, then run every question after each change. A change that fixes one answer often breaks another.

Run at least 20 real questions from your inbox, including the awkward ones. For the full method, see How to Test an AI Chatbot Before It Talks to Your Customers.

6. Keep the instruction accurate

Instructions go stale the moment a price, promo or policy changes. Treat them as a living document with an owner.

• Assign one owner. One person approves every change.
• Date your versions. Keep a copy of each version so you can roll back a change that made answers worse.
• Review weekly at first. Read real conversations, note where the AI hesitated or guessed, and fix the instruction or the knowledge file.
• Retest after every edit. Run the same test questions again.

An honest limitation: no instruction makes an AI perfectly reliable. Models still misread unusual messages, and a well-written instruction reduces errors rather than removing them. That is why the handoff section and regular reviews matter more than clever wording.

Frequently asked questions

How long should an AI agent instruction be?

Long enough to cover the nine parts and no longer. Most business agents work well with a focused instruction plus knowledge files for long lists. Botcake AI allows up to 15,000 characters, but more text is not better if it repeats or contradicts itself.

Should I write the instruction in English if my customers use other languages?

You can write it in English and tell the agent to reply in the language the customer uses. Test it with real messages in every language your customers write in.

What is the difference between an instruction and a knowledge file?

The instruction tells the agent how to behave: its role, goal, steps and rules. Knowledge files hold the facts it looks up: product lists, prices, policies and FAQs.

Can I use one instruction for several platforms?

Yes. The structure works on Botcake, ManyChat, GoHighLevel and most AI agent tools. Adjust the channel name, the field syntax for customer data and the handoff method for each platform.

References

1. OpenAI Help Center: Best practices for prompt engineering with the OpenAI API. Accessed October 2026.
2. Claude Platform Docs: Prompt engineering overview. Accessed October 2026.
3. Botcake AI + Pancake Setup Guide, Dijae Dadula, October 2026.

Keep reading

• What Is an AI Agent?
• How to Test an AI Chatbot Before It Talks to Your Customers
• The 5 Chatbot ROI Metrics That Matter
• See all posts on the blog