Issues when calling the numbet
# support
a
When i test my bot trough vapi, everything works. When I call it on the designated number, first of all it talks in a slowed and deep voice, second the functions dont work. It is supposed to be an appointment setter, but when calling the number it gives a made up one. Thanks in advance. @Sahil @User
v
@Adm420419 It sounds like you're experiencing a couple of different issues with your voice bot when it's accessed via a phone call. Let's address each one: 1. Voice Quality (Slowed and Deep Voice): This could be due to various factors such as network latency, codec issues, or the telephony service provider's voice processing. It's important to ensure that the voice settings are consistent across different platforms. You might want to check the voice configuration in your VAPI setup and compare it with the settings used during testing. 2. Functions Not Working (Appointment Setter Issues): If the bot is not setting appointments correctly when called, there might be a problem with the integration between the telephony interface and the bot's appointment-setting functionality. This could be due to incorrect handling of the telephony input, issues with the backend service responsible for setting appointments, or a misconfiguration in the bot's logic when handling voice calls. To assist you further, I would need more specific details about the configuration and the code you're using for the appointment setting functionality. If you can provide that, I can give you more targeted advice. Otherwise, I recommend checking the following: - Ensure that the bot's logic for appointment setting is correctly triggered during a phone call. - Verify that the backend service (if any) used for setting appointments is accessible and functioning as expected during a phone call. - Check for any errors or warnings in the logs when the bot is accessed via the designated number. - Test the bot's functionality with different phone devices to rule out device-specific issues. If you've already checked these and the problem persists, please reach out to support for more in-depth troubleshooting.
You can continue this conversation by mentioning me in the message.
a
1. Never had these issues before 2. Same settings are used when testing
s
@Adm420419 Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!
a
When calling the number: 50d5efc2-39b2-48b0-86b5-6bb65d855b92 When testing trough Vapi: 9501e8f0-4987-47a9-997b-2860681ce177 It happens trough the whole call @Shubham Bajaj
Also when calling trough vapi, I get the correct date (7.10.2024) and when calling trough the number the bot responds with the date 19.06.2024 - I have never used this date with the bot, I have no idea where it gets it from @Shubham Bajaj @Sahil
s
@Adm420419 I went through the call with ID 50d5efc2-39b2-48b0-86b5-6bb65d855b92, but it's not in English so I couldn't perform any analysis or debugging. Additionally, you only shared the call IDs without proper descriptions as requested. Could you please provide: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead https://cdn.discordapp.com/attachments/1326231305519890482/1326935628616568873/Screenshot_2025-01-09_at_20.56.44.png?ex=67813c9b&is=677feb1b&hm=f42242466fd1f832bafde221fad4e8bfc66e95abfce59365613428f2fb162f73&
a
Do you need the call in english? I didnt include the timestamp because it happens trough the whole call. The assistent picks up and talks in a deep and slowed voice. Trough the call. If you would read what i wrote, you would see that i mentioned this in the very beginning of the post - as that is the main issue. @Shubham Bajaj
s
@Adm420419 Allow me some time to confirm the issue details with the voice provider.
a
Sure ill be waiting 👍 @Shubham Bajaj
s
@Adm420419 here's your call transcript
Copy code
AI: Hello,\nUser: Hello, I would like to make an appointment.\nAI: Sure day, of course, I can help you. I'll take a second to look at the first available date. One moment please, I can offer you a date on the 19th\n
First, the appointment setter wasn't working due to an old KB provider. Remove the Canonical KB and try the call again - this should resolve the issue. Regarding the voice, I suggest changing the voice provider to 11labs if it's available, as this is purely a voice provider issue. Alternatively, you can use a custom voice provider. Lastly, you have enabled smart endpoint which only works for English transcription - disable this or you will have issues with user input not transcribing properly.
Copy code
json
      "knowledgeBase": {
        "topK": 2,
        "fileIds": [
          "fa705d30-6823-4295-ad55-01bc145b2d2f",
          "80d77be5-2f99-4c07-9a12-472f167a8fb3",
          "71e7bcde-9645-4629-968f-97f4326a5c43"
        ],
        "provider": "canonical"
      }
Copy code
json
    "start_speaking_plan": {
      "smartEndpointingEnabled": true,
      "transcriptionEndpointingPlan": {
        "onNumberSeconds": 0.8,
        "onNoPunctuationSeconds": 0.9
      }
    },
Yeah one more for KB you can follow this document to add new provider
Trieve
in place of
canonical
https://docs.vapi.ai/knowledgebase
@Adm420419 do let me know how it goes.
2 Views