How to Build a Custom AI Assistant: Instructions, Knowledge Files and Testing

If every time you open a chat you have to explain who you are, what your company does and how you want answers, you're repeating work. A custom assistant stores that context permanently: instructions, reference documents and the tone you want. It's the natural next step after mastering prompts, and it doesn't require coding. In this lesson, which wraps up the Intermediate level, you'll build a complete one.

1. Decide if it's worth it
2. Write the instructions
3. Prepare the documents
4. Test with 20–30 questions
5. Share and maintain

What a custom assistant is

It's a version of your AI assistant configured for one specific job. It has three parts:

Where to build one (and what changed in 2026)

Each platform has its own version, and in late 2026 several are changing names and formats. Here's the situation as of November 2026:

In Microsoft 365 Copilot, you build agents with its Agent Builder. Check your tool's help pages before you start. What you learn here (instructions, documents and testing) carries over to any format: platforms change the packaging, but the contents are yours.

When it's worth building one

Build an assistant when at least two of these are true:

• You repeat the same task several times a week (answering inquiries, writing product descriptions, reviewing copy).
• The task always needs the same context or documents.
• You want consistent results, in the same format and tone.
• Other people on the team need to do the same task.

Good bets: customer replies, a style-guide reviewer, internal policy Q&A, sales proposals or a course tutor.

The instructions: a professional template

Instructions are the most important part. Use this structure, which expands on the formula from lesson 3:

# IDENTITY AND GOAL
You're the customer support assistant for Ridgeline Coffee, an
online specialty coffee store based in Portland, Oregon. Your goal
is to resolve customer questions quickly, warmly and accurately.

# AUDIENCE
Retail customers, many on their phones. Use short sentences and
avoid jargon.

# KNOWLEDGE
Answer only from the attached documents (catalog, prices, shipping,
returns, FAQ). If something isn't in them, say you don't have that
information and offer to connect the customer with a person. Never
make up prices, delivery times or promotions.

# HOW TO RESPOND
- 80 words max unless they ask for detail.
- Friendly, professional tone.
- End with a question only if you need information to help.

# SPECIAL CASES
- Damaged or late order: apologize, ask for the order number and
  refer them to support@ridgeline-coffee.example. Don't promise refunds.
- Health questions (caffeine, pregnancy, medical conditions): don't
  give advice; suggest they talk to a health professional.
- Topics unrelated to the store: say you can only help with
  Ridgeline Coffee questions.

# EXAMPLE RESPONSE
Customer: "Do you ship to Phoenix?"
Assistant: "Yes! We ship to all 50 states. Orders to Phoenix arrive
in 3 to 5 business days, and shipping is $6.95 (free on orders of
$40 or more). Anything else I can help with on your order?"

If you're stuck, ask the AI to interview you and draft the instructions:

I want to build a custom assistant for [task]. Ask me, one at a
time, the questions you need about: the goal, who will use it, the
documents it will consult, tone, special cases and what to do when
it doesn't know the answer. At the end, write the instructions with
these sections: IDENTITY AND GOAL, AUDIENCE, KNOWLEDGE, HOW TO
RESPOND, SPECIAL CASES and EXAMPLE RESPONSE.

Expected result: six to eight questions and a draft in the template's structure. Review two things closely: what it does when the answer isn't in the documents, and whether the special cases match your real policies.

Preparing the knowledge documents

The assistant can't be better than the information you give it. Before uploading files:

1. Update them: last year's price list will produce wrong answers with total confidence. Put an effective date on every document.
2. Remove contradictions: if two documents give different deadlines, the assistant will pick one more or less at random.
3. Use clear titles and short sections: "Return policy," "Shipping to Alaska and Hawaii."
4. Write FAQs in question-and-answer format.
5. Prefer text to images: a scanned price table can be misread.
6. Check confidentiality: don't upload anything that every user of the assistant shouldn't see.

FREQUENTLY ASKED QUESTIONS · effective 10/01/2026

How long does shipping take within Oregon and Washington?
1 to 2 business days. Orders placed before noon Pacific ship the same day.

Can I return coffee if I didn't like it?
Yes, if the bag is unopened, within 15 days of delivery.
Opened bags are only replaced if they're defective.

Test before you share

Never launch an assistant without testing it. Prepare 20 to 30 questions with the expected correct answer, covering five types:

A reasonable split for a first set of 20 questions:

Count how many answers are correct. When one fails, decide whether the problem is in the instructions (a missing rule or example) or the documents (missing or contradictory information), fix it and rerun all the tests. Launch when it gets nearly every case right and invents nothing in any of them. Log each round in the Prompt tests tab of the workbook.

Sharing and maintenance

• Decide who can use it: just you, your team, the whole company or the public. For external customers, website and messaging chatbots (lesson 14) give you more control.
• Explain what it's for and what it isn't, with 3 or 4 sample questions.
• Name an owner who updates the documents when prices or policies change.
• Review conversations periodically (if the platform allows it and privacy rules permit): the questions it can't answer are the next ones to add to its documents.

Common mistakes when building assistants

# IDENTITY AND GOAL
You're the company's editor. You review copy (customer emails, social
posts, proposals) so it follows the attached style guide and reads
clearly.

# HOW TO RESPOND
1. List the problems you found in a table:
   Original sentence | Problem | Style guide rule | Suggested fix
2. Below it, give the full corrected text.
3. If the text already complies, say so in one line and don't
   invent changes.

# RULES
- Apply only the style guide's rules; don't change the author's
  personal style if it doesn't break any.
- Don't change numbers, names or facts. If a fact looks wrong, flag
  it with "VERIFY" without correcting it.

# KNOWLEDGE
Style guide (effective March 2026).

Summary

• A custom assistant combines permanent instructions, knowledge documents and capabilities.
• It pays off for repetitive tasks that need the same context and consistent results.
• The instructions must say what to do when the answer isn't in the documents.
• Keep documents current, consistent and well structured, with an effective date.
• Test with 20 to 30 varied questions, including trick ones, before sharing, and keep a copy of everything outside the platform.

You've finished the Intermediate level! You can now prompt, structure, analyze and save your context in your own assistant.

Next lesson: AI Automation and AI Agents Without Coding. The Advanced level begins: you'll connect AI to your apps to build automations and learn what AI agents are and the safety rules they need.