How to create a FAQ assistant in Microsoft Copilot: step by step

This tutorial shows how to create a FAQ assistant in Microsoft Copilot that answers frequently asked questions from your team or your customers. A FAQ assistant helps reduce response time, improves answer consistency, and serves as a starting point to automate internal knowledge.

Prerequisites

• Account with access to Microsoft Copilot (appropriate license).
• List of questions and answers (CSV or text file) or a small knowledge base.
• Text editor (VS Code, Notepad) and access to a browser.
• Permissions to create and test prompts/assistants in the Copilot environment.

Step 1: Prepare the knowledge base

Organize the questions and answers in a simple format. A CSV with "question" and "answer" columns is sufficient. This makes loading and testing in Copilot easier.

question,answer
"Como redefinir a password?","Siga estes passos: 1) Aceda a account.microsoft.com; 2) Seleccione 'Esqueci a password'; 3) Siga as instruções de verificação."
"Qual o horário de suporte?","Suporte disponível das 09:00 às 18:00, segunda a sexta."

Step 2: Create a clear system prompt

In Copilot, the system prompt defines the assistant's behavior. Be explicit about tone, answer format, and when to ask for clarifications.

System: "És um assistente de FAQ da equipa de suporte. Responde de forma curta e clara (máx. 3 frases). Se a pergunta não for clara, pede um exemplo ou contexto. Indica sempre os passos concretos quando existirem."

Step 3: Upload the knowledge base to Copilot

If your Copilot environment allows attaching files or sources, upload the CSV. Alternatively, copy the main Q&A into the prompt as initial context. Use short snippets to avoid exceeding token limits.

Context: "FAQ:
- Como redefinir a password? -> Siga estes passos: ...
- Qual o horário de suporte? -> Suporte disponível das 09:00 às 18:00..."

Step 4: Build interaction examples (few-shot)

Provide examples of question → answer to teach the style. This improves consistency and is useful to signal the desired format to the model.

Example 1:
User: "Como posso mudar a password da minha conta?"
Assistant: "Aceda a account.microsoft.com, seleccione 'Esqueci a password' e siga a verificação."

Example 2:
User: "Qual o horário de suporte?"
Assistant: "Suporte disponível das 09:00 às 18:00, segunda a sexta."

Step 5: Test real questions and handle common errors

Run tests with real questions, synonyms and incomplete questions. Check for incorrect or overly vague answers and adjust the prompt or the knowledge base.

1. Test: Clear question — should return the exact FAQ answer.
2. Test: Ambiguous question — the assistant should ask for clarification.
3. Test: Out-of-scope question — the assistant should indicate it does not know and suggest human contact.

User: "Não consigo entrar na conta"
Assistant (esperado): "Pode clarificar se é problema de password ou de verificação? Se for password, siga: account.microsoft.com > 'Esqueci a password'."

Step 6: Refine and add actions (optional)

If your Copilot supports integrations, add actions like creating a ticket or sending a link. Define safe commands and confirmation messages in the prompt.

System: "Se o utilizador pedir para abrir um ticket, pergunta 'Deseja abrir um ticket agora?' e, com confirmação, crie o ticket com os campos: assunto, descrição e contacto."

Verify the result

Validate with multiple users: test frequent questions, ambiguities and out-of-scope scenarios. Confirm the assistant responds with a consistent format, asks for clarifications when needed and does not invent information (hallucinations). Correct false answers by updating the FAQ or adjusting the prompt.

Conclusion

After implementing the FAQ assistant in Microsoft Copilot, monitor interactions, collect questions that were not answered correctly and update the knowledge base. Next step: integrate automatic ticket creation or satisfaction metrics to measure impact. Tip: start with 20–50 Q&A and iterate with real feedback.