AI Assistants Overview
System Prompts
Learn how to create effective system prompts - the core intelligence of your AI assistant
The system prompt is the most crucial component of your AI assistant. It defines your assistant’s personality, behavior, knowledge, and capabilities. Think of it as the “brain” and “training manual” combined.
Quick Start with Templates
To get started quickly:
- Go to your assistant settings
- Find the system prompt field
- Click the “Templates” button nearby
- Choose a template that matches your use case
- Customize it for your needs
Language Support
Your system prompt can be written in any language, regardless of the spoken language setting:
- Write the prompt in your preferred language
- Set the spoken language separately in assistant settings
- The AI will follow the prompt’s instructions while speaking in the selected language
For example:
- System prompt in English, spoken language set to Spanish
- System prompt in German, spoken language set to French
- System prompt in Chinese, spoken language set to English
Why They Matter
Your system prompt:
- Shapes how the AI thinks and responds
- Defines conversation boundaries
- Provides essential knowledge
- Controls behavior and tone
- Determines handling of edge cases
Key Components
A good system prompt should include:
1. Role & Identity
2. Conversation Style
3. Key Information
4. Behavioral Guidelines
5. Response Framework
Best Practices
-
Be Specific
- Clear instructions get better results
- Include examples of good responses
- Define what NOT to do
-
Structure Matters
- Organize information logically
- Use bullet points and sections
- Keep related information together
-
Test and Iterate
- Start with a basic prompt
- Test various scenarios
- Refine based on call recordings
- Add handling for edge cases
Common Mistakes
- Too Vague: “Be helpful and professional” (Not specific enough)
- Too Rigid: Scripting every possible response (Reduces natural flow)
- Information Overload: Including unnecessary details
- Missing Guidelines: Not specifying how to handle common situations
Example Structure
Testing Your Prompt
-
Make test calls covering:
- Common scenarios
- Edge cases
- Difficult situations
- Various customer personalities
-
Review and adjust:
- Listen to call recordings
- Check response accuracy
- Verify tone consistency
- Test knowledge retention
Optimization Tips
- Start with Fast Engine for quick iterations
- Use call recordings to identify gaps
- Add examples of good/bad responses
- Include handling for unexpected questions
Pro Tip: Your system prompt is a living document - regularly update it based on actual call experiences and customer interactions.