Skip to main content
Prompt Engineering is the most important part of your agent, it can make or break your agent. This guide will share our findings on how to write prompts that agents can follow more reliably. This guide is a work in progress and will be updated as we learn more. If you have any suggestions or feedback, please let us know. To check some of the prompts we have created, you can look at templates in Dashboard (create a new agent and select a template to start). ​

Using Ask Co-Pilot

If you’re unsure how to craft an effective prompt, don’t worry. Ask Co-Pilot can guide you through the process. It will ask you a series of relevant questions, step-by-step, to help you formulate a clear and concise prompt. This interactive approach ensures you cover all necessary details and get the best possible response from the AI Agent.

Existing Context

The AI Agent already has information from the profile and can access certain known details:
  • You do not need to restate the AI Agent’s name or characteristics.
  • You do not need to provide the current time.
  • If the person the AI is interacting with is already in its contact database, there’s no need to reintroduce their details.

Sectional Prompts

When writing prompts, it is important to break down the system prompts into smaller sections, where each section has its focus, like identity, style, guideline, task & goals. This has a couple of benefits:
  • reusable
  • easier to maintain
  • easier for LLM to understand
The AI Agent can understand all languages specified in the profile. Feel free to write the prompt in any of these languages to get the most natural and contextually rich response.

Identify

You are a friendly AI assistant for TruFlow AI. …

Style Guardrails

Be concise: … Be conversational: … …

Response Guideline

Return dates in their spoken forms: … Ask up to one question at a time: … …

Task

  1. Greet the user …

Task

  1. Ask for user’s name.
  2. Ask if user needs a refund, need a replacement, or just retriving information.
  • if user needs a refund, transition to refund state.
  • if user needs a replacement, transition to replacement state.
  1. If user is just retriving information, ask for the order number. …

Task

  1. Inform user why you are calling.
  2. Ask for user’s name.
wait for user response
  1. Ask if user needs a refund, need a replacement, or just retriving information.
wait for user response
  • if user needs a refund, transition to refund state.
  • if user needs a replacement, transition to replacement state.
  1. Ask for the order number.
wait for user response …