URGENT..... Twilio number is not connecting to mak...
# support
t
As can see in the most recent messages at end of this thread - The Option to prevent Vonage numbers from leaving Voice Mails is missing (*The Ai just starts talking to the Voice Mail as if its a person going through an entire pitch........) Can this please be added / updated ASAP πŸ™
v
@Tim Clark I'm here to help you integrate VAPI settings with make.com (formerly Integromat). To get started, could you please provide me with more details about the specific settings or data from VAPI that you're trying to use within make.com? This will help me understand what kind of correlation or connection you're aiming to achieve.
You can continue this conversation by mentioning me in the message.
t
@Vapi This is regarding the Knowldge base to be synced into make.com // also all the settings like smartendpointing, the interruption threashold and the other settings on Vapi to work for the outbound agent
v
@Tim Clark To sync the VAPI knowledge base into make.com and configure settings like smart endpointing and interruption threshold for the outbound agent, you'll need to follow these steps: 1. **Access VAPI Settings**: First, you need to access the VAPI settings where you can find the knowledge base and other configurations. 2. **API Integration**: Check if VAPI provides an API that allows you to retrieve the knowledge base and settings. You will need the API endpoints and the necessary authentication credentials. 3. **Make.com Scenario Setup**: Log in to your make.com account and create a new scenario. Use the HTTP module to make requests to the VAPI API endpoints. 4. **Retrieve Knowledge Base**: Use the HTTP "Make a request" action to call the VAPI API endpoint that provides the knowledge base data. 5. **Retrieve Settings**: Similarly, use the HTTP "Make a request" action to call the API endpoints for smart endpointing, interruption threshold, and other settings. 6. **Process Data**: Once you have the data in make.com, you can process it as needed, for example, by storing it in a database, using it in other modules, or triggering specific actions. 7. **Configure Outbound Agent**: Use the retrieved settings to configure the outbound agent within make.com, ensuring that the smart endpointing and interruption threshold are set according to the data obtained from VAPI. If you need the exact API endpoints and how to use them, or if you encounter any issues during the setup, please let me know, and I can provide further assistance. If VAPI has specific modules or integrations for make.com, that could simplify the process as well.
s
@Tim Clark can you share a loom video of what your trying to achieve and the issue are facing.
t
Hi @Shubham Bajaj - @Matthewgentiluomo Is our team member working on this atm - I have asked him to get a video of this to help clarify and send back here
s
you have to config this on either on your permanent assistant which has assistantId or pass temporary assistant with these config.
I suggest checking out create assistant first before create call.
m
@Vapi @Shubham Bajaj Hi guys is it possible to ad vonage into voicemail detection ?? These setting don't work when i put in a Vonage number and it keeps talking during the voicemail https://cdn.discordapp.com/attachments/1292839162801553450/1295206262610460672/Screenshot_2024-10-14_at_1.04.20_PM.png?ex=670dce54&is=670c7cd4&hm=c3b436cf1557a6aa557f4371d21969c328be7874f4b0589e60b5992b6c4c91af&
v
@Matthewgentiluomo To incorporate the assistant settings into the create call and use custom settings for your calls, you would typically need to configure these settings within the VAPI platform before initiating the call. If you're using a permanent assistant with an
assistantId
, you would configure the settings associated with that assistant. If you're passing a temporary assistant configuration, you would include these settings in the payload when creating the assistant. For voicemail detection with a Vonage number, if the settings you've provided are not working as expected, it could be due to a variety of reasons such as network latency, the voicemail system's behavior, or configuration mismatches. Here are some steps you can take to troubleshoot and resolve the issue: 1. **Review Configuration**: Ensure that the voicemail detection settings are correctly configured in VAPI. This includes the
voicemailDetectionTypes
,
machineDetectionTimeout
,
machineDetectionSpeechThreshold
,
machineDetectionSpeechEndThreshold
, and
machineDetectionSilenceTimeout
. 2. **Test Different Settings**: Experiment with different thresholds and timeouts to see if there's a configuration that works better with the Vonage voicemail system. 3. **Check Vonage Settings**: Review the settings on your Vonage account to ensure there are no conflicting configurations that might affect voicemail detection. 4. **Contact Support**: If you're still facing issues, it might be best to reach out to VAPI support for assistance. They may have specific guidance for integrating with Vonage or be able to help you troubleshoot the issue further. If you need to adjust the settings or require further assistance with the VAPI platform, please let me know, and I can guide you through the necessary steps or provide additional support.
m
Yeah I've already tried all these solutions and none worked, so I put in a Twilio number and it managed not to leave a voicemail with the correct settings. Conclusion is that we need to add Vonage as part of those setting so vonage numbers don't leave voicemails when they shouldn't anymore
v
@Matthewgentiluomo I understand that you've tried various solutions without success using a Vonage number, but the settings worked correctly with a Twilio number. It seems that the voicemail detection settings are compatible with Twilio but not with Vonage. To address this issue, you would need to work with the VAPI platform to see if they can extend their voicemail detection capabilities to include support for Vonage numbers. This might involve: 1. **Contacting VAPI Support**: Reach out to VAPI support to request the addition of Vonage to the list of supported providers for voicemail detection. 2. **Provider-Specific Settings**: Inquire if there are provider-specific settings or parameters that need to be adjusted for Vonage. 3. **Feedback to Vonage**: It may also be helpful to contact Vonage support to provide feedback about the voicemail detection issue and see if they have any insights or solutions from their end. 4. **Workaround Solutions**: In the meantime, consider using a workaround, such as using Twilio numbers for the calls where voicemail detection is critical, until a solution with Vonage is implemented. If you need assistance in contacting VAPI support or require further guidance, please let me know, and I'll do my best to assist you.
t
Hi @Shubham Bajaj @User @User Are you able to assist with the above to allow us to stop the Ai talking to Voice Mails for Vonage Numbers..? @Matthewgentiluomo Our VAPI tech is stuck with this which means we can't continue working with Vapi for our business till this is fixed - So we would say this is REALLY URGENT - Really appreciate your help to address this ASAP πŸ™
s
@Tim Clark / @Matthewgentiluomo Vonage doesn't support voice mail detection so you have to use twilio for it.
t
URGENT HELP PLEASE - 1st off Thankyou @Shubham Bajaj @Vapi @User @Sahil - @Matthewgentiluomo We have switched to Twilio - Unfortunately the number is not connecting / shows as invalid when it goes into make. - Any assistance is GREATLY appreciated. As we can't make calls for clients right now https://cdn.discordapp.com/attachments/1292839162801553450/1296279184263348315/WhatsApp_Image_2024-10-17_at_08.26.13_4e50a51e.jpg?ex=6711b591&is=67106411&hm=a8395123cfc3f306533ff91bdb26ae63b1a21bced51318707dc42dfefc3ec6eb&
v
@Tim Clark I understand the urgency of the situation. To assist you with the Twilio number not connecting or showing as invalid in make.com, please ensure the following: 1. **Twilio Number Format**: Verify that the Twilio phone number is in E.164 format, which includes the country code, area code, and phone number. For example, a US number should look like +1XXXXXXXXXX. 2. **Twilio Account Configuration**: Check that the Twilio number is active and properly configured in your Twilio account. Ensure that it's capable of making outbound calls. 3. **API Credentials**: Confirm that you're using the correct Twilio Account SID and Auth Token in make.com. These credentials must be accurate to authenticate API requests. 4. **Make.com Configuration**: In your make.com scenario, ensure that you're using the correct module for making calls and that the phone number field is correctly mapped to your Twilio number. 5. **Error Messages**: Pay close attention to any error messages you receive in make.com or from the Twilio API. They can provide clues on what might be going wrong. 6. **Twilio Support**: If the issue persists, consider reaching out to Twilio support for assistance. They can provide insights specific to your account and number status. If you have verified all the above and the issue remains unresolved, please provide me with any error messages or additional details you have, and I will do my best to assist you further.
s
read the error message.
You aren’t passing the number correctly
t
Thankyou @Sahil Is there any way you can assist further / how we should be passing the number / what has been done incorrectly
r
Can you share the input of that error node?
t
@Rish @ TalkFlowAI Appreciate your help..! @Matthewgentiluomo Is the person on our Team working on this atm - @Matthewgentiluomo Can you please share the info here
m
what do you mean by that? the JSON CODE?
r
Yes. The json input
m
ill message you personally πŸ™‚
s
@Tim Clark your expected to pass phone number with country code to make it work.
t
Ok, we managed to fix it now - Many thanks for your help @Shubham Bajaj
4 Views