We've added new API capabilities for Twilio developers, enabling advanced handling and redirection of unanswered calls to streamline call workflows.
What's New
1. New Options for Redirecting Unanswered Calls
Twilio developers can now override the default unanswered call behavior and regain control with these options:
- Return to Twilio Studio Flow: Add &returnTo=flow&returnToId={FLOW_SID} to the URL to redirect the call back to a Twilio Studio flow, enabling custom workflow handling.
- Send to TaskRouter Workflow: Use &returnTo=taskQueue&returnToId={WORKFLOW_SID} in the URL to route the call to a TaskRouter Workflow, connecting to Twilio Flex or another workflow.
- Redirect to Twilio Function: Append &returnTo=postEndpoint&returnToId={ENCODED_TWILIO_FUNCTION_ENDPOINT} to the URL for redirection to a Twilio Function endpoint, allowing for additional custom processing.
2. Default Unanswered Call Handling
When updating calls with Spoke’s redirect URL, standard business rules now apply:
- User Extensions: Redirects to user voicemail if unanswered.
- Team Extensions: Follows the team's "unanswered" call flow, which can route to another group, voicemail, or an external number.
Security Recommendation
For Twilio Functions, we recommend verifying Twilio’s X-Twilio-Signature header to enhance security. See Twilio documentation for more information.