Call Forwarding problem with Twilio
# support
j
I am using a Twilio number on my outbound ai caller. Then, during the call with a lead, the AI can transfer the call into a live team agent (which uses JustCall number and Hubspot as CRM). However, the main issue is that JustCall and Hubspot detects the Twilio number as the one who is calling -- so all of the forwarded calls are logged as the Twilio's number. Is there a way to put the lead's number as the one who's calling in the JustCall and Hubspot during the call transfer?
v
Yes, you can configure the caller ID settings to display the lead's number during the call transfer in both JustCall and Hubspot. Here’s how you can do it: ### For Twilio: 1. **Transfer Call Function**: When transferring the call, you can specify the
callerId
parameter in your Twilio API call. Set it to the lead's number to ensure that it appears as the caller ID during the transfer.
Copy code
bash
   curl -X POST \
     -H "Authorization: Bearer <Your Twilio Auth Token>" \
     -H "Content-Type: application/json" \
     -d '{
       "type": "transferCall",
       "destinations": [
         {
           "type": "number",
           "number": "insert-phone-number-id-here",
           "callerId": "{{lead.number}}",
           "numberE164CheckEnabled": false
         }
       ]
     }' https://your.destination.url
### For JustCall: 1. **Dynamic Caller ID Setup**: In JustCall, you can also set the caller ID during the transfer. Make sure to include the lead's number in the transfer configuration.
Copy code
json
   {
     "type": "transferCall",
     "destinations": [
       {
         "type": "number",
         "number": "insert-phone-number-id-here",
         "callerId": "{{lead.number}}",
         "numberE164CheckEnabled": false
       }
     ]
   }
### For Hubspot: 1. **Configuration**: Ensure that Hubspot is set up to accept the caller ID from the transfer. If the AI agent is configured to pass along the original caller ID, the recipient will see the lead's number. ### Key Considerations: - Make sure that the lead's number is verified and owned by your telecommunication provider to avoid any issues with call rejection. - Check the documentation for each platform to ensure that you are following the latest guidelines and requirements. By implementing these configurations, you should be able to have the lead's number displayed during the call transfer in JustCall and Hubspot. If you need further assistance, feel free to ask! 😊 Sources:
- [Configuring Caller ID Settings in Twilio for Call Transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/1341368675680391178) - [Detailed Report on Caller ID Customization in JustCall for Transferred Calls](https://discord.com/channels/1211482211119796234/1211483291191083018/1329106554041012265) - [Detailed Report: Hubspot and Caller ID Customization During Call Transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/1335170913502498866)
Message marked as helpful by @Jerome Matthew! 🎉
j
Where exactly in Twilio can I configure this API Call (or should I do this in Make.com)? @Vapi Support Bot
v
You can configure the API call directly in Twilio by using their API to set the caller ID during the call transfer. Here’s how you can do it: 1. **Twilio Console**: You can manage your Twilio settings and API calls through the Twilio Console. However, the actual API call for transferring calls with a specific caller ID needs to be made programmatically, typically from your application or server. 2. **Using the API**: You would use the Twilio API to make the call transfer. Here’s a sample API call you can use:
Copy code
bash
   curl -X POST \
     -H "Authorization: Bearer <Your Twilio Auth Token>" \
     -H "Content-Type: application/json" \
     -d '{
       "type": "transferCall",
       "destinations": [
         {
           "type": "number",
           "number": "insert-phone-number-id-here",
           "callerId": "{{lead.number}}",
           "numberE164CheckEnabled": false
         }
       ]
     }' https://your.destination.url
3. **Make.com Integration**: If you prefer a no-code solution, you can also use Make.com to set up the API call. Make.com allows you to create scenarios that can automate the process of transferring calls and setting the caller ID without writing code. ### Key Considerations: - Ensure that the lead's number is verified and owned by your telecommunication provider to avoid any issues with call rejection. - Check the Twilio documentation for the latest updates and features regarding API calls. If you need more detailed guidance on using Make.com or Twilio, feel free to ask! 😊 Sources: - [Configuring Caller ID Settings in Twilio for Call Transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/1341368675680391178) - [Detailed Report on Caller ID Customization in JustCall for Transferred Calls](https://discord.com/channels/1211482211119796234/1211483291191083018/1329106554041012265)
- [Detailed Report: Hubspot and Caller ID Customization During Call Transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/1335170913502498866)
s
@Jerome Matthew checking if this is resolved for you?
j
@Shubham Bajaj what should I put in the URL section in performing this API call?
s
@Jerome Matthew You don’t need to provide the server URL. The caller ID works without it. It’s an inbuilt Vapi tool that we’ll handle on your end. You just need to define the tool and its destinations.
Let me know if you require further help.
2 Views