Overview
The Incoming Call Node triggers a workflow automatically when a customer calls your voice agent. This enables you to process call data, perform post-call actions, and integrate with other systems based on inbound customer interactions.
Use Cases
- Post-Call Processing: Automatically send follow-up emails or SMS after calls
- CRM Integration: Update customer records with call details
- Ticket Creation: Generate support tickets based on call content
- Analytics: Track and analyze inbound call patterns
- Lead Qualification: Score and route leads based on call outcomes
- Callback Scheduling: Schedule follow-up calls for unresolved issues
- Notification Systems: Alert teams about important customer calls
How It Works
- Customer calls your voice agent’s phone number
- Voice agent handles the conversation
- When call ends, Incoming Call Node is triggered
- Call details and transcript are passed to subsequent workflow blocks
- Automated actions are executed based on your workflow configuration
Outputs
The Incoming Call Node provides comprehensive call information that can be used by subsequent blocks:Bot_Number
- Phone number on which the customer called the voice agent
- The inbound line or SIP address
- Format: +[country code][number]
+91xxxxxxxxxx
Use_Case
- The voice agent that handled the call
- References the agent configured in your account
- Useful for routing different call types
customer_support, sales_inquiry
Call_Time
- Timestamp of when the call occurred
- Format: ISO 8601 date format
YYYY-MM-DDTHH:MM:SSZ - Includes timezone information
2025-12-10T14:30:00Z
Call_Status
- Final status of the call
- Possible values:
connected: Call was successfully connected and completedcouldn't connect: Call failed to connect
connected
Call_Duration
- Duration of the call in seconds
- Excludes ring time and connection delays
- 0 for failed connections
185 (3 minutes 5 seconds)
Call_Direction
- Direction of the call
- Always
inboundfor this node - Distinguishes from outbound calls
inbound
Customer_Number
- Customer’s phone number who made the call
- Format: +[country code][number]
- Can be used for callback or identification
+91xxxxxxxxxx
Customer_Details
- Customer information in JSON format
- May include: name, email, account ID, etc.
- Populated from your CRM or previous interactions
Transcript
- Complete transcript of the call conversation
- Includes speaker tags (Assistant vs Customer)
- Formatted text with timestamps
Workflow Examples
Example 1: Post-Call Email Follow-up
Workflow:- Incoming Call Node (trigger)
- AI Query Agent Node (analyze call and generate email)
- Send Email Node (send follow-up to customer)
Example 2: CRM Update
Workflow:- Incoming Call Node (trigger)
- Smart Filter Node (check if call was successful)
- Webhook Node (update CRM with call details)
Example 3: Callback Scheduling
Workflow:- Incoming Call Node (trigger)
- AI Query Agent Node (determine if callback needed)
- Schedule Callback Node (schedule follow-up call)
Example 4: Support Ticket Creation
Workflow:- Incoming Call Node (trigger)
- AI Query Agent Node (extract issue details)
- Webhook Node (create ticket in support system)
- Send Email Node (notify customer of ticket number)
Example 5: Lead Scoring
Workflow:- Incoming Call Node (trigger)
- AI Query Agent Node (analyze conversation for buying signals)
- Smart Filter Node (filter high-quality leads)
- Webhook Node (send qualified leads to sales team)
Configuration
Setting Up Inbound Telephony
Before using the Incoming Call Node, ensure you have:- Configured Inbound Trunk: Set up SIP trunk in Telephony Integration
- Mapped Voice Agent: Associate your agent with the inbound number
- Tested Connection: Make a test call to verify setup
Adding to Workflow
- Create or edit a workflow
- Add the Incoming Call Node as the first block
- Connect subsequent blocks to process call data
- Save and activate the workflow
Processing Call Data
Using Transcript Data
The transcript can be used for:- Sentiment Analysis: Determine customer satisfaction
- Intent Detection: Identify customer needs
- Information Extraction: Pull out order IDs, dates, etc.
- Quality Assurance: Review agent performance
- Training Data: Improve agent responses
Using Call Metadata
Call metadata (duration, status, time) can be used for:- Performance Metrics: Track average call duration
- Availability Analysis: Identify peak call times
- Success Rate: Monitor connection success
- Reporting: Generate call volume reports
Best Practices
Workflow Design
- Keep It Simple: Start with basic workflows and add complexity gradually
- Error Handling: Include fallback actions for failed steps
- Testing: Test workflows with sample calls before going live
- Monitoring: Regularly review workflow execution logs
Data Processing
- Validate Data: Check that required fields are present
- Handle Failures: Account for calls that couldn’t connect
- Privacy: Respect customer data privacy regulations
- Retention: Set appropriate data retention policies
Performance
- Async Processing: Use webhooks for long-running tasks
- Batch Operations: Group similar actions when possible
- Timeout Handling: Set appropriate timeouts for external calls
- Rate Limiting: Respect API rate limits for integrations
Integration
- Idempotency: Ensure actions can be safely retried
- Authentication: Secure all external API calls
- Error Logging: Log errors for troubleshooting
- Monitoring: Set up alerts for workflow failures
Monitoring and Analytics
Track Workflow Performance
Monitor your incoming call workflows:- Execution Count: How many times workflow triggered
- Success Rate: Percentage of successful executions
- Average Duration: Time to complete workflow
- Error Rate: Failed workflow executions
Call Analytics
Analyze incoming call patterns:- Call Volume: Calls per hour/day/week
- Peak Times: When most calls occur
- Average Duration: Typical call length
- Connection Rate: Successful vs failed calls
Business Insights
Extract valuable insights:- Common Issues: Frequently discussed topics
- Customer Sentiment: Overall satisfaction trends
- Agent Performance: Call handling effectiveness
- Conversion Rates: Leads to customers ratio
Troubleshooting
Workflow Not Triggering
Possible Causes:- Inbound trunk not configured correctly
- Agent not mapped to phone number
- Workflow not activated
- Verify telephony integration setup
- Check agent mapping in Integrations section
- Ensure workflow is saved and activated
Missing Call Data
Possible Causes:- Call disconnected before completion
- Transcript processing delay
- Network issues
- Check call status in Call History
- Wait a few minutes for transcript processing
- Review system status page
Workflow Execution Errors
Possible Causes:- Invalid configuration in subsequent blocks
- External API failures
- Timeout issues
- Review workflow execution logs
- Test each block individually
- Check external service status
Next Steps
AI Query Agent Node
Process call data with AI
Send Email Node
Send follow-up emails
Schedule Callback Node
Schedule follow-up calls
Webhook Node
Integrate with external systems
Transcripts may take 1-2 minutes to process after the call ends. Design your workflows to account for this delay if needed.