Overview
The Actions & Tools section is the powerhouse of your AI agent’s operational capabilities. Here you configure what your agent can do during and after calls - from transferring conversations to human agents or SIP systems, to making intelligent API calls, and setting up sophisticated callback protocols.This section transforms your agent from a simple conversationalist into a fully integrated business automation tool that can take real actions and connect with your existing systems.
Call Transfer
Configure how your agent intelligently transfers calls to human agents, departments, or external phone systems when needed.Transfer Configuration
Enable Transfer Capability
Toggle the “Call Transfer” option to activate the transfer functionality for your agent.
Choose Transfer Destination
Select between traditional phone numbers or SIP trunk endpoints based on your infrastructure.
Configure Transfer Logic
Define when and how your agent should initiate transfers using smart prompting.
Transfer Types
- Phone Number
- SIP Trunk
Traditional Phone TransferPerfect for transferring to mobile phones, landlines, or traditional business numbers.
- Format: Use international format (+1234567890)
- Best for: Human agents, customer service departments, sales teams
- Reliability: High compatibility with all phone systems
- Cost: Standard telephony rates apply
Transfer Prompt Configuration
The transfer prompt is crucial - it teaches your AI agent exactly when to transfer calls. Here are professionally crafted templates:- Spanish
- English
- French
Advanced Transfer Settings
Context Preservation: When transferring calls, the agent can provide context to the human operator:- Customer’s name and contact information
- Reason for the call and main topics discussed
- Specific questions or requests that triggered the transfer
- Customer sentiment and interaction history
- Warm Transfer: Agent briefly speaks with the human before connecting the customer
- Cold Transfer: Direct transfer without agent introduction
- Conference: Three-way call with agent, customer, and human
End Call Strategy
Configure intelligent call termination with sophisticated answering machine detection and strategic conversation ending.Call Termination Logic
Configure Detection Phrases
Set up language-specific phrases that indicate answering machines or voicemail.
Answering Machine Detection
Our advanced detection system recognizes voicemail and answering machines across multiple languages:Detection Accuracy: 95%+ accuracy rate in identifying automated systems
Languages Supported: Spanish, English, French, German, Italian, Portuguese
Response Time: Detection typically occurs within 3-5 seconds of answering
- Spanish
- English
- French
- “En este momento no podemos atenderle”
- “Deje su mensaje después de la señal”
- “Gracias por llamar, en estos momentos…”
- “Bienvenido al buzón de voz de…”
- “Este es el contestador de…”
Strategic Call Ending
Beyond answering machine detection, configure professional call termination for various scenarios: Natural Completion Triggers:- Customer explicitly says goodbye or indicates call completion
- Agent has successfully completed the stated objective
- All customer questions have been answered satisfactorily
- Meeting or appointment has been successfully scheduled
- Customer declines service and requests no further contact
- Call duration exceeds maximum configured time
- Customer becomes unresponsive for extended period
- System detects inappropriate or abusive language
Webhook Tools
Create powerful API integrations that allow your agent to interact with external systems during conversations.Webhook Fundamentals
Real-time Integration: Execute API calls during live conversations
Dynamic Parameters: Use conversation data to populate API requests
Response Processing: Agent can react to API responses and continue conversation Error Handling: Graceful fallbacks when APIs are unavailable
Response Processing: Agent can react to API responses and continue conversation Error Handling: Graceful fallbacks when APIs are unavailable
Creating Webhook Tools
Configure Tool Identity
- Name: Clear, descriptive name (e.g., “create_lead”, “check_availability”)
- Description: Explain when the AI should use this tool
- Trigger Conditions: Define conversation scenarios that should activate the tool
Set API Endpoint
- URL: The complete webhook endpoint URL
- Method: Choose GET, POST, PUT, PATCH, or DELETE
- Authentication: Configure headers for API security
Parameter Configuration
Each webhook parameter supports sophisticated data mapping:| Property | Description | Options | Example |
|---|---|---|---|
| Name | Parameter identifier | Custom string | customer_name |
| Type | Data validation | string, number, boolean, integer, array, object | string |
| Required | Mandatory field | true/false | true |
| Description | AI understanding | Natural language | ”Customer’s full name from conversation” |
| Value Source | How to get value | LLM extraction, static value, conversation metadata | LLM prompt |
| Extraction Prompt | AI instruction | Natural language | ”Extract the customer’s full name” |
Advanced Parameter Types
- Query Parameters
- Body Parameters
- Header Parameters
URL ParametersAdded to the URL query string for GET requests or as additional parameters.Best for:
- Search queries
- Filtering parameters
- API keys and tokens
- Simple data passing
Webhook Execution Settings
Configure how and when webhooks execute: Execution Timing:- Immediate: Execute during the active call
- Deferred: Execute after the call ends
- Conditional: Execute based on conversation outcome
- Interruption Control: Should agent pause while waiting for API response?
- Pre-tool Speech: Force agent to announce action before executing
- Tool Call Sound: Play typing sound during execution
- Response Timeout: Maximum wait time for API response (5-60 seconds)
- Retry Logic: Automatic retries on failure
- Fallback Messages: What to say if API fails
- Graceful Degradation: Continue conversation without API data
Practical Webhook Examples
- CRM Integration
- Appointment Booking
- Inventory Check
Lead Creation Webhook
Authentication Methods
- Bearer Token
- API Key
- Basic Auth
Recall Protocol
Set up sophisticated automatic callback systems for comprehensive customer follow-up when initial calls don’t achieve their objectives.Recall System Architecture
Smart Scheduling: Intelligent timing based on customer behavior and business rules
Success Detection: Automatic recognition of completed objectives to prevent unnecessary callbacks
Compliance Built-in: Respects Do Not Call lists and regulatory requirements Escalation Paths: Gradually increase intervals and change strategies over time
Compliance Built-in: Respects Do Not Call lists and regulatory requirements Escalation Paths: Gradually increase intervals and change strategies over time
Recall Configuration
Define Success Conditions
Specify what constitutes a successful call that doesn’t require follow-up.
Recall Timing Strategies
| Attempt | Timing | Use Case | Success Rate |
|---|---|---|---|
| 1st Recall | 15-30 minutes | Busy signal, no answer | 35% |
| 2nd Recall | 2-4 hours | Same day follow-up | 25% |
| 3rd Recall | Next business day | Professional follow-up | 20% |
| 4th Recall | 3-5 days later | Persistent but respectful | 15% |
| 5th Recall | 1-2 weeks later | Final attempt | 10% |
Success Condition Examples
Objective Achievement:- Customer provided required information (contact details, preferences)
- Meeting or appointment successfully scheduled
- Purchase decision made (positive or negative with clear finality)
- Information successfully delivered (pricing, product details, etc.)
- Customer explicitly requested no further contact
- Customer scheduled their own callback time
- Customer was transferred to human agent successfully
- Customer asked to be contacted via different method (email, text)
- Full conversation completed with all questions answered
- Customer showed clear lack of interest with polite decline
- Answering machine message successfully delivered
- Technical issues prevented meaningful conversation
Advanced Recall Features
Dynamic Scheduling:- Previous conversation summaries
- Customer preferences and objections
- Best times to call based on answer patterns
- Failed attempt reasons and adjustments needed
- Automatic DNC (Do Not Call) list checking
- Time zone awareness for appropriate calling hours
- Frequency limits (max calls per day/week)
- Opt-out recognition and processing
Caller ID Configuration
Set up professional caller IDs for outbound calls to improve answer rates and brand recognition.Caller ID Management
Caller ID Best Practices
Number Selection:- Use local area codes when possible (increases answer rates by 20-30%)
- Choose memorable, professional-looking numbers
- Avoid numbers that look like spam (avoid 555, repeated digits)
- Use toll-free numbers for national campaigns
- SMS verification for mobile numbers
- Voice verification for landlines
- Business documentation for toll-free numbers
- Compliance with carrier requirements
- A/B test different caller IDs
- Monitor answer rates by time of day
- Adjust caller ID based on campaign type
- Use different numbers for different business units
Best Practices
Call Transfer Optimization
-
Clear Trigger Definition
- Define specific, unambiguous scenarios for transfers
- Avoid vague conditions that could cause unnecessary transfers
- Include escalation paths for different types of issues
-
Context Preservation
- Ensure human agents receive comprehensive call context
- Include customer information, conversation summary, and specific needs
- Provide clear reason for transfer to minimize customer frustration
-
Fallback Planning
- Configure backup numbers for failed transfers
- Set up alternative routing for business hours vs. after hours
- Have contingency plans for system outages
Webhook Development
-
API Design Principles
- Use descriptive, semantic naming for webhook tools
- Ensure APIs return meaningful success/error responses
- Implement proper HTTP status codes and error messages
- Design for idempotency to handle retries safely
-
Security Implementation
- Always use HTTPS endpoints
- Implement proper authentication (Bearer tokens, API keys)
- Validate and sanitize all incoming data
- Use rate limiting to prevent abuse
-
Performance Optimization
- Keep API response times under 5 seconds when possible
- Implement proper caching strategies
- Use asynchronous processing for long-running operations
- Monitor webhook performance and success rates
End Call Strategy
-
Cultural Adaptation
- Adapt detection phrases to local language variants
- Respect cultural norms for call termination
- Use appropriate farewell messages for different regions
- Consider local business customs and communication styles
-
Continuous Improvement
- Monitor call completion rates and reasons
- Analyze answering machine detection accuracy
- Adjust prompts based on false positives/negatives
- Regular review of termination criteria effectiveness
Recall Protocol Management
-
Compliance First
- Implement robust Do Not Call list checking
- Respect time zone restrictions and business hours
- Provide clear opt-out mechanisms in every interaction
- Document consent and preferences carefully
-
Strategic Timing
- Use data-driven approach to optimize callback timing
- Consider customer behavior patterns and preferences
- Avoid over-communication that could damage relationships
- Balance persistence with respect for customer wishes
-
Success Measurement
- Track callback success rates by attempt number
- Measure customer satisfaction with follow-up processes
- Monitor complaint rates and opt-out requests
- Optimize based on actual conversion data
Troubleshooting Common Issues
- Transfer Problems
- Webhook Failures
- Recall Issues
Failed Transfers:
- Check phone number format (use international format)
- Verify SIP URI syntax and network connectivity
- Test transfer destinations manually
- Review carrier compatibility and routing
- Ensure transfer prompts include context instructions
- Verify human agent training on receiving transferred calls
- Check integration between systems
- Review call logging and recording setup
Integration Examples
Complete Sales Follow-up Workflow
Coming Soon
Our development roadmap includes exciting new capabilities to further enhance your agent’s operational power:
| Feature | Description | Timeline | Impact |
|---|---|---|---|
| 📧 Email Integration | Send personalized emails during or after calls | Q2 2024 | Medium |
| 💬 SMS Integration | Text message capabilities for follow-up | Q2 2024 | High |
| 📱 WhatsApp Integration | WhatsApp Business API for messaging | Q3 2024 | High |
| 🔄 Multi-step Workflows | Complex, branching automation sequences | Q3 2024 | Very High |
| 📊 Advanced Analytics | Detailed performance metrics and optimization insights | Q3 2024 | Medium |
| 🤖 AI-Powered Optimization | Automatic improvement of webhook and transfer performance | Q4 2024 | Very High |
Next Steps
Input Parameters
Configure dynamic variables and data inputs for personalized conversations
Output Settings
Set up data extraction and webhook delivery for comprehensive automation

