Deployment Overview
You’ve built and tested your AI agent. Now it’s time to deploy it to production and start handling real conversations. This guide provides an overview of all deployment options, security considerations, and best practices for going live.Deployment Options
Dasha BlackBox provides three primary deployment methods, each suited for different use cases:- Phone Deployment
- Web Widget
- API Integration
Make and receive real phone calls
- Inbound calls via dedicated phone numbers or SIP URIs
- Outbound calls scheduled via API or dashboard
- SIP trunk integration with compatible SIP providers (Bandwidth, Telnyx, etc.)
- Call transfers to human agents when needed
Pre-Deployment Checklist
Before going live, verify your agent is production-ready:Agent Configuration
- System Prompt Finalized: Clear, specific instructions tested with real scenarios
- LLM Model Selected: Appropriate model for your latency/quality/cost requirements
- Voice Configured: Natural-sounding voice with correct language and speed
- Temperature Tuned: 0.6-0.8 for most use cases (see Best Practices)
- Max Tokens Set: 150-300 for voice responses to prevent long monologues
Testing Validation
- Happy Path Tested: Common user scenarios work as expected
- Edge Cases Covered: Handles unclear input, off-topic questions, errors
- Voice Quality Verified: Clear pronunciation, natural prosody, correct speed
- Response Time Acceptable: Under 2 seconds for most interactions
- 10+ Test Conversations: Reviewed transcripts for quality and consistency
Integrations & Features
- Tools & Functions Working: All external APIs and integrations tested
- Webhooks Configured: Endpoints verified and receiving events correctly
- Transfers Set Up: Call transfer routes tested with real destinations (if applicable)
- Business Hours Defined: Schedule matches actual availability (if applicable)
- MCP Servers Connected: Model Context Protocol integrations verified (if applicable)
Security & Compliance
- API Keys Secured: Stored in environment variables, not hardcoded
- Origin Restrictions Set: Web integration origins whitelisted
- Webhook Signatures Verified: Security headers validated on your endpoint
- PII Handling Reviewed: Agent prompt includes data privacy guidelines
- Rate Limits Configured: Concurrency caps set to prevent abuse
Phone Deployment Overview
Deploy your agent to handle real phone calls via inbound or outbound channels.Inbound Calls
Every agent is automatically assigned a SIP URI when created. Customers can call this URI to reach your agent. How It Works:- Agent created → SIP URI auto-generated (e.g.,
sip:agent-abc123@sip.staging.dasha.ai) - Configure your phone provider to forward calls to the SIP URI
- Incoming calls automatically routed to your agent
- Agent conducts conversation using configured voice and LLM
- Bandwidth
- Telnyx
- Vonage
- Any SIP-compatible carrier
Inbound SIP URI displayed on agent detail page
Next Steps:
- Inbound Calls Guide - Configure phone provider to route calls
- Phone Numbers - Purchase and assign phone numbers
Outbound Calls
Schedule calls programmatically or via dashboard. Your agent calls customers at the right time. How It Works:- Configure Outbound SIP settings in agent (server, credentials, caller ID)
- Schedule call via API or dashboard with destination number
- Call placed at scheduled time using your SIP trunk
- Agent conducts conversation and completes objective
- Results sent via webhook when call ends
- SIP trunk credentials (server, auth user, password)
- Caller ID (from user/DID) for outbound calls
- Transport protocol (UDP or TCP)
- Optional: CPS (calls per second) limits
- Sales outreach and lead qualification
- Appointment confirmations and reminders
- Survey collection and feedback
- Customer follow-ups and notifications
- Outbound Calls Guide - Set up outbound calling
- Production Checklist - Pre-launch verification
Web Widget Deployment Overview
Embed your AI agent on your website as a voice or chat widget.Widget Features
The Dasha BlackBox widget provides a complete conversational UI: Communication Modes:- Voice Calls: WebRTC-based voice conversations
- Text Chat: Real-time text messaging
- Phone Calls: Click-to-call via phone (optional)
- Theme: Light or dark mode
- Position: Bottom-right, bottom-left, top-right, etc.
- Feature Gating: Enable/disable specific capabilities
- Branding: Matches your website design
- Token-based authentication
- Origin restrictions (CORS)
- Feature permissions
- Usage tracking
Deployment Process
1. Create Web Integration Navigate to your agent’s detail page → Web Integrations → Add Integration Configure:- Name and description
- Allowed origins (e.g.,
https://yoursite.com,*.yoursite.com) - Enabled features (AllowWebCall, AllowWebChat, etc.)
- Widget appearance (theme, position)
- Enter token name (e.g., “Production Website”)
- Click “Generate Token”
- Copy token immediately (shown only once)
- Deploy to staging/test environment
- Verify widget loads correctly
- Test voice and chat features
- Confirm origin restrictions work
- Check token authentication
- Web Widget Embedding - Complete embedding guide
- Widget Configuration - Advanced configuration options
- Widget Customization - Styling and branding
API Integration Overview
Build custom integrations using the Dasha BlackBox REST API.Common Integration Patterns
CRM Integration:API Best Practices
Authentication:- Store API keys in environment variables
- Rotate keys regularly
- Use separate keys for staging and production
- Never commit keys to version control
- Respect API rate limits (documented per endpoint)
- Implement exponential backoff for retries
- Batch operations where possible
- Monitor usage to avoid throttling
- Always check response status codes
- Handle network errors gracefully
- Log errors for debugging
- Implement retry logic for transient failures
- API Reference - Complete API documentation
- Webhooks Overview - Configure event webhooks
- Webhook Security - Secure your webhooks
Security Considerations
API Key Management
Best Practices:- Store Securely: Use environment variables or secret managers (AWS Secrets Manager, HashiCorp Vault)
- Rotate Regularly: Change API keys every 90 days
- Scope Appropriately: Use read-only keys where write access isn’t needed (future feature)
- Monitor Usage: Track API key usage for anomalies
Web Integration Security
Origin Restrictions:- Generate separate tokens for each deployment (production, staging, development)
- Use descriptive names: “Production Website”, “Mobile App”, “Partner Integration”
- Delete compromised tokens immediately
- Monitor token usage via integration analytics
- Set up alerts for unusual activity
Webhook Security
Validate webhook requests to prevent spoofing: Signature Verification:- Use HTTPS for all webhook endpoints
- Implement IP allowlisting (if supported)
- Rate limit webhook requests
- Log all webhook attempts for auditing
Scaling Considerations
Concurrency Limits
Dasha BlackBox limits simultaneous calls per agent to prevent abuse and ensure quality: Default Limits:- Free tier: 2 concurrent calls per agent
- Pro tier: 10 concurrent calls per agent
- Enterprise: Custom limits (contact sales)
- New calls queued automatically
- Calls execute when slot becomes available
- Queue has priority-based ordering
- Deadline ensures calls don’t queue indefinitely
Rate Limits
API endpoints have rate limits to ensure fair usage: Common Limits:- Call scheduling: 100 requests/second
- Agent updates: 10 requests/second
- Call listing: 50 requests/second
- Webhook delivery: 1000 events/second (receiving side should handle)
Cost Optimization
Model Selection:- Use
gpt-4.1-miniorllama-3.1-8b-instantfor high-volume use cases - Consider
deepseek-r1for 30x cost reduction vs GPT-4 - See LLM Configuration for model comparison
- Set max tokens to 150-300 for voice responses
- Use shorter system prompts when possible
- Implement prompt caching (where supported)
- Monitor token usage via analytics
- Cartesia and Dasha are cost-effective for high volume
- ElevenLabs for premium quality when needed
- See Voice & Speech for pricing comparison
Monitoring Production
Once deployed, continuous monitoring is essential:Key Metrics to Track
Agent Health:- Success Rate: Percentage of calls achieving their objective
- Error Rate: Failed calls, system errors, timeouts
- Average Duration: Call length trends over time
- Response Latency: Time from user speech to agent response
- Daily/Weekly Calls: Track usage trends
- Peak Hours: Identify high-traffic periods
- Queue Length: Monitor backlog during peaks
- Concurrent Calls: Watch for approaching limits
- Transfer Rate: Calls escalated to humans (lower is often better)
- User Satisfaction: Post-call analysis scores (if enabled)
- Conversation Length: Optimal range for your use case
- Tool Call Success: Function/integration execution success rate
Dashboard Monitoring
Use the Dasha BlackBox dashboard to monitor:- Dashboard Overview - High-level metrics and trends
- Call Management - Active and queued calls in real-time
- Call History - Search and filter past conversations
- Analytics - Detailed performance insights
- Agent Performance - Per-agent metrics and comparisons
Alerts and Notifications
Set up webhooks to receive alerts:- Error rate exceeds 5% in 1 hour
- Concurrency limit reached
- Webhook endpoint unreachable
- Unusual call volume spikes
- Average call duration exceeds 2x baseline
Performance Optimization
If you notice performance issues: Slow Response Times:- Switch to faster LLM (gpt-4.1-mini, groq models)
- Enable service tier priority (OpenAI)
- Reduce max tokens to 150-200
- Use faster TTS provider (Cartesia, Dasha)
- Optimize system prompt length
- Review error logs in Call Inspector
- Check external API/tool availability
- Validate webhook endpoint health
- Verify SIP trunk configuration
- Monitor LLM provider status
- Review conversation transcripts
- Refine system prompt based on patterns
- Adjust temperature for consistency
- Test different voices for clarity
- A/B test configuration changes
Production Deployment Checklist
Use this final checklist before going live:Configuration Verification
- System prompt tested with 50+ conversations
- LLM model finalized (temperature, max tokens, service tier)
- Voice provider and settings validated
- All tools and integrations tested end-to-end
- Business hours and schedule configured (if applicable)
- Call transfer routes tested with real destinations
- Webhooks receiving events correctly
Security & Compliance
- API keys stored securely (environment variables)
- Web integration origins whitelisted (no wildcard
*) - Webhook signatures implemented and verified
- Rate limits configured appropriately
- PII handling documented in system prompt
- Data retention policies understood
Testing & Validation
- 10+ happy path scenarios tested
- 10+ edge cases validated (errors, unclear input)
- Voice quality verified with real users
- Response times under 2 seconds
- Load tested with concurrent calls
- Failover and error recovery tested
Monitoring & Support
- Dashboard alerts configured
- Webhook monitoring set up
- Error tracking implemented
- Support team briefed on escalation
- Runbook created for common issues
- Rollback plan documented
Launch Strategy
- Start with 10-20% of traffic (if possible)
- Monitor metrics hourly on launch day
- Human fallback available for escalations
- Quick iteration capability (can update prompt rapidly)
- Post-launch review scheduled (24h, 1 week, 1 month)
Next Steps
Choose your deployment path:Phone Deployment
- Phone Numbers - Purchase and configure phone numbers
- Inbound Calls - Set up inbound call routing
- Outbound Calls - Configure outbound calling
Web Deployment
- Web Widget Embedding - Embed widget on your site
- Widget Configuration - Configure features and permissions
- Widget Customization - Customize appearance and branding
API Integration
- API Reference - Complete API documentation
- Webhooks Overview - Set up event webhooks
- Webhook Security - Secure your integrations
Production Readiness
- Production Checklist - Detailed pre-launch checklist
- Best Practices - Optimization and quality guidelines
- Monitoring - Track performance in production
API Cross-Refs
Agent Management:- POST /api/v1/agents - Create agent
- PUT /api/v1/agents/ - Update agent
- GET /api/v1/agents/ - Get agent details
- POST /api/v1/calls - Schedule call
- GET /api/v1/calls - List calls
- GET /api/v1/calls/ - Get call details
- GET /api/v1/calls/statistics/statuses - Call statistics
- POST /api/v1/web-integrations - Create integration
- POST /api/v1/web-integrations//tokens - Generate token
- PUT /api/v1/web-integrations/ - Update integration