Agent Goes Silent After Greeting
Your agent responds to the initial greeting but then stops responding to the caller’s inputs.
Symptoms
- Agent picks up the call and delivers the initial greeting message
- After the caller responds, the agent becomes unresponsive
- No error messages appear in the dashboard
- The call doesn’t disconnect, but the agent won’t speak or act further
- This happens consistently across multiple test calls
Common Causes
- Using GPT Nano model — Do not use. The GPT Nano model has persistent failures in production and frequently becomes unresponsive after the initial prompt.
- Exhausted OpenAI API key — If you’re using a “Bring Your Own” (BYO) OpenAI API key, it may have reached its rate limit or credit limit.
- Poor prompt structure — Overly complex, contradictory, or poorly formatted system prompts cause the model to “freeze”.
- Knowledge base too large — Massive knowledge bases (>50MB) can cause timeout issues and processing delays.
Critical:
Do not use GPT Nano for production. Switch to GPT 4.1-mini or GPT 4.1 immediately — this resolves most “agent goes silent” issues.
How to Fix
Step 1: Check Your LLM Model Selection
- Go to Agent Settings → Model Configuration
- Check which model you’re currently using
- If you’re using GPT Nano: Immediately switch to GPT 4.1-mini (recommended for most use cases) or GPT 4.1 (if you need higher reasoning capability)
- Save changes and make a fresh test call
Step 2: Verify Your OpenAI API Key (if using BYO)
- Navigate to Integrations → OpenAI
- Check if you have a custom API key configured
- Log into your OpenAI account and verify:
- Your account has available credits
- The API key hasn’t expired
- Your usage hasn’t exceeded your rate limits
- If key is exhausted: Remove the custom key to fall back to Dialora’s default OpenAI integration
- Click Save and test again
Step 3: Simplify Your Agent Prompt
- Go to Agent Configuration → System Prompt
- Review your prompt for:
- Contradictory instructions (e.g., “be helpful but never answer questions”)
- Excessive nested conditions or complex logic
- Instructions that conflict with the agent’s core functions
- Simplify to 3–5 core instructions maximum
- Test with a cleaner version of your prompt
Step 4: Reduce Knowledge Base Size
- Go to Knowledge Base → Manage Files
- Check the total size of your uploaded files
- If exceeding 50MB:
- Remove outdated or redundant documents
- Split large PDFs into smaller chunks
- Archive infrequently used content
- Re-upload your optimized knowledge base
- Test the agent again
Prevention Tips:
- Always use GPT 4.1-mini or GPT 4.1 for production agents
- Test your prompts incrementally — start simple and add complexity gradually
- Monitor your OpenAI usage if using a BYO key; set up billing alerts
- Keep knowledge bases under 50MB and review them quarterly
- Test every configuration change on a short test call before deploying