Best Practices

​

Overview

​

Phone Number Organization

​

Naming Conventions

✅ Good:
- 'Customer Support - Primary'
- 'Sales - North America'
- 'Emergency Hotline - 24/7'
- 'Billing Inquiries - Business Hours'

❌ Avoid:
- 'Number 1'
- 'Test'
- 'Temp'
- 'New Number'

• Format: [Department] - [Region/Function]
• Examples:
  • ‘Support - Primary’
  • ‘Sales - Eastern Region’
  • ‘HR - Recruiting’
• Makes searching and filtering easier
• Improves team collaboration

• Operating hours: ‘Support - 24/7’ vs ‘Support - Business Hours’
• Language: ‘Support - Spanish’, ‘Support - Arabic’
• Function: ‘Appointments - Scheduling’, ‘Appointments - Reminders’

​

Documentation

• Spreadsheet or database of all phone numbers
• Purpose and use case for each number
• Associated Voice Agent details
• Provider information
• Cost tracking
• Emergency contacts

• Keep copies of SIP trunk settings
• Record webhook URLs and configurations
• Note any special routing requirements
• Document provider account details (not credentials)

• Log when numbers are added or removed
• Record assignment changes
• Note configuration updates
• Maintain changelog for auditing

​

Voice Agent Assignment

​

Strategic Assignment

• Specialized agents for specific phone lines
• Customer support agent → support line
• Sales agent → sales line
• Appointment agent → appointment line
• Clear separation of concerns

• High-volume lines → well-tested, robust agents
• Low-volume lines → can use experimental agents
• Monitor call volume and adjust assignments

• Assign region-appropriate agents
• Consider language and dialect
• Time zone awareness
• Cultural sensitivity

​

Assignment Management

1. Assign agent to test number first
2. Make test calls
3. Verify behavior thoroughly
4. Monitor first production calls closely
5. Adjust as needed

• Frequent changes can cause confusion
• Customers expect consistency
• Test thoroughly before assigning
• Plan assignments carefully

• Check Call History regularly
• Review first few calls in detail
• Monitor for errors or issues
• Gather feedback from users

• Maintain backup Voice Agents
• Document fallback procedures
• Plan for agent failures
• Test disaster recovery

​

Provider Management

​

Twilio Best Practices

• Keep account in good standing
• Maintain sufficient balance
• Set up auto-recharge
• Enable spending alerts
• Monitor usage regularly

• Rotate Auth Tokens periodically
• Use subaccounts for separation
• Enable two-factor authentication
• Monitor for suspicious activity
• Review access logs

• Use appropriate number types (local, toll-free)
• Consider geographic routing
• Monitor call quality metrics
• Review Twilio debugger regularly
• Optimize for cost efficiency

• Follow Twilio’s compliance requirements
• Register business information
• Comply with TCPA regulations
• Maintain do-not-call lists
• Document consent for outbound calls

​

SIP Trunk Best Practices

• Document all SIP settings thoroughly
• Use TCP for reliability (most cases)
• Test thoroughly before production
• Maintain configuration backups

• Use strong authentication credentials
• Rotate passwords regularly
• Implement IP whitelisting
• Monitor for unauthorized access

• Ensure stable network connectivity
• Configure proper firewall rules
• Allow Hamsa’s IP addresses
• Monitor network latency
• Have redundant connections

• Maintain good relationship with carrier
• Document all configurations together
• Plan changes in advance
• Test in non-production environment
• Have carrier support contacts ready

• Test connections regularly
• Monitor call quality
• Track connection failures
• Review carrier reports
• Set up alerting for issues

​

Security Best Practices

​

Credential Management

• Never share credentials publicly
• Don’t commit to version control
• Use secure password managers
• Rotate regularly (quarterly minimum)
• Limit access to authorized personnel

• Store securely in environment variables
• Rotate periodically
• Monitor usage for anomalies
• Revoke if compromised
• Use separate keys for dev/prod

• Use strong passwords (16+ characters)
• Include special characters
• Avoid dictionary words
• Change after staff changes
• Don’t reuse across systems

​

Access Control

• Grant minimum necessary permissions
• Review access regularly
• Remove access for departed staff
• Use role-based access control
• Audit permission changes

• Document who has access to what
• Maintain up-to-date access lists
• Regular access reviews
• Clear onboarding/offboarding procedures
• Emergency access procedures

​

Monitoring and Auditing

• Review Call History for anomalies
• Check for unexpected calls
• Monitor call costs
• Review failed calls
• Look for patterns indicating issues

• Unusual call volumes
• Failed authentication attempts
• Excessive costs
• Configuration changes
• Provider issues

• Track all configuration changes
• Log phone number additions/deletions
• Record assignment changes
• Monitor API usage
• Keep logs for compliance

​

Testing Best Practices

​

Pre-Production Testing

1. Test in browser first
2. Make test calls to your own phone
3. Try various scenarios
4. Test error handling
5. Verify all features work
6. Test at different times
7. Test from different locations

• Agent answers correctly
• Audio quality is good
• Agent understands inputs
• Tools execute properly
• Knowledge base accessible
• Call completes properly
• Webhooks fire correctly
• Costs are as expected

• Happy path (everything works)
• Error scenarios (what could go wrong)
• Edge cases (unusual inputs)
• Stress testing (high volume)
• Network issues (connectivity problems)

​

Production Monitoring

• Monitor first production calls closely
• Review transcripts in detail
• Check for any issues
• Adjust configuration as needed
• Gather user feedback

• Check Call History daily
• Review failed calls immediately
• Monitor success rates
• Track average call duration
• Watch for cost trends

• Random sampling of calls
• Review transcripts regularly
• Check for agent errors
• Verify knowledge base accuracy
• Monitor customer satisfaction

​

Cost Optimization

​

Monitoring Costs

• Review costs in Call History
• Export data for analysis
• Compare to budget
• Identify cost drivers
• Look for anomalies

• Establish monthly budget
• Set up spending alerts
• Monitor against targets
• Adjust as needed
• Plan for growth

• Peak calling times
• Average call duration
• Cost per call
• Most expensive routes
• Optimization opportunities

​

Reducing Costs

• Configure agents for efficiency
• Use clear, concise prompts
• Minimize unnecessary chatter
• Handle errors gracefully
• End calls appropriately

• Local numbers often cheaper
• Toll-free for customer-facing
• Consider geographic rates
• Bundle with provider plans
• Negotiate volume discounts

• Test in browser when possible
• Limit test call duration
• Use test mode features
• Plan tests efficiently
• Don’t over-test

• More efficient for campaigns - use Batch Calls instead of individual calls
• Better concurrency management
• Lower per-call cost
• Easier tracking
• Automated execution
• Learn more: Creating Batch Calls

​

Performance Optimization

​

Call Quality

• Optimize LLM settings
• Use appropriate model
• Configure timeout settings
• Balance speed vs quality
• Monitor response times

• Ensure stable connectivity
• Monitor latency
• Check bandwidth availability
• Use quality carriers
• Have redundancy

• Choose quality voice models
• Test different voices
• Balance naturalness vs speed
• Consider language/accent
• Monitor customer feedback

​

Reliability

• Multiple phone numbers for critical services
• Backup Voice Agents ready
• Alternative providers configured
• Failover procedures documented
• Regular disaster recovery testing

• Real-time call monitoring
• Automated health checks
• Alert systems configured
• On-call procedures
• Incident response plans

• Regular configuration reviews
• Update agents periodically
• Refresh knowledge bases
• Test all components
• Keep documentation current

​

Compliance and Legal

​

Regulatory Compliance

• TCPA compliance (USA)
• GDPR requirements (Europe)
• Local telemarketing laws
• Recording consent laws
• Data retention requirements

• Obtain proper consent
• Maintain do-not-call lists
• Respect quiet hours
• Provide opt-out mechanisms
• Document compliance efforts

• Secure call recordings
• Protect customer data
• Implement retention policies
• Follow privacy regulations
• Document data handling

​

Recording and Consent

• Disclose recording in agent greeting
• Comply with local laws
• Store recordings securely
• Implement retention policies
• Provide access when required

• Obtain before calling
• Document consent
• Honor opt-outs immediately
• Make opt-out easy
• Maintain records

​

Incident Response

​

Preparation

• Document common issues
• Create troubleshooting guides
• Maintain contact lists
• Test procedures regularly
• Train team members

• Provider support numbers
• Internal escalation paths
• On-call personnel
• Backup contacts
• After-hours procedures

​

Responding to Issues

1. Check Call History for errors
2. Verify phone number configuration
3. Test connection (SIP)
4. Check provider status
5. Review agent configuration
6. Contact provider support if needed
7. Document issue and resolution

1. Review call transcripts
2. Check agent configuration
3. Verify knowledge base
4. Test tools and integrations
5. Monitor network quality
6. Adjust configuration
7. Retest thoroughly

• Notify affected stakeholders
• Provide status updates
• Document resolution
• Conduct post-mortem
• Implement preventive measures

​

Continuous Improvement

​

Regular Reviews

• Review all phone numbers
• Check assignment appropriateness
• Analyze call volumes
• Review costs
• Update documentation

• Comprehensive configuration review
• Security audit
• Cost optimization analysis
• Performance evaluation
• Compliance check

• Complete system review
• Provider relationship review
• Strategic planning
• Budget review
• Technology updates

​

Optimization Cycle

1. Monitor - Track metrics and gather data
2. Analyze - Identify patterns and issues
3. Plan - Develop improvement strategies
4. Implement - Make changes carefully
5. Test - Verify improvements
6. Document - Record changes and results
7. Repeat - Continuous improvement

​

Knowledge Sharing

• Regular training sessions
• Documentation updates
• Best practice sharing
• Lessons learned reviews
• Cross-training for coverage

• Keep guides current
• Share troubleshooting tips
• Document new patterns
• Create runbooks
• Maintain FAQ

​

Related Documentation