{{exampleVariable}}, which are dynamically filled with contact information, and “functions” like [endCall], which the agent can call during the conversation.
1. Identity & Context
Purpose
Defines the basic role of the call agent. The AI must know:- Who is speaking?
- For which company?
- In what role?
- In which language?
- What is the purpose of the call?
What belongs here?
- Agent name / persona (e.g.,
{{personaName}}) - Company / brand
- Role (e.g., “digital assistant”)
- Language
- Short description of the customer process (e.g., customer submitted an online request)
- Internal directives (e.g., silent execution, no internal info spoken aloud)
Example
2. Customer Data & Input Variables
Purpose
Defines all variables passed from the CRM or API into the call prompt. Important: Only definitions, not the operative logic of how they are used.What belongs here?
- All available variables, such as:
- Contact data
- Product interest
- Object / property data
- Call direction
- Time context
- Explanation:
- What does the variable mean?
- When is it considered empty?
- How is it used in the conversation?
Example
3. Operational Rules & Pronunciation
(These rules are product-agnostic and can be reused 1:1 for all scripts.)Purpose
Defines general behaviors, tone, formatting, and pronunciation. These rules apply globally, regardless of the specific script.What belongs here?
- Communication style (e.g., direct, structured)
- Handling names
- Handling interruptions
- AI transparency
- Number and formatting rules
- Brand and language settings
Example (general, can be used unchanged)
4. Conversation Guide (Script Structure)
Purpose
The central section. This contains the actual flow of how an outbound call is conducted. The script is always:- Numbered
- Linear
- Clearly structured
- With defined IF/ELSE sections
- Without unnecessary variants
What belongs here?
- Greeting & reference to the inquiry
- Qualification questions
- Product / property questions
- Timeframe questions
- Data gathering / confirmation (without technical validation details)
- Closing communication
- Farewell
Example (general outline)
5. Objection Handling
Purpose
Defines how typical objections are answered. This section is always separate, so the main script stays clean.What belongs here?
- Thematic categories:
- Time/availability
- Interest
- Process questions
- Identity/person
- Technical uncertainties
- Other cases
- For each objection:
- Trigger (“I don’t have time right now”)
- Standard response (short & word-for-word)
- Note: Return to the script afterward
Example
6. Instructions: How to Write a Good Script
Purpose
Provides clear rules for creating new call scripts.6.1 Numbering is mandatory
A good script is fully numbered:- 1
- 2
- 3
- …
6.2 Keep the main section as simple as possible
- Short, clear sentences
- No variants, no synonyms
- No unnecessary safety phrasing
- Objection handling not in the main flow
- Only ask absolutely necessary questions
6.3 Separate logic clearly
- Variables → Section 2
- Global rules → Section 3
- Flow → Section 4
- Objections → Section 5
6.4 Building blocks instead of continuous text
Every sentence must be written so the AI can say it exactly as-is.6.5 Examples help the AI
Every section should include at least one example showing how something should be structured.Template Structure
Here’s the recommended structure for a complete agent prompt:Best Practices Summary
- Structure is key - Use numbered sections consistently
- Separation of concerns - Keep variables, rules, flow, and objections in separate sections
- Be explicit - The AI will follow what you write literally
- Use examples - Show the AI what good looks like
- Keep it simple - Avoid unnecessary complexity in the main flow
- Test iteratively - Refine based on actual agent behavior