I´m testing the transfer call function with transferPlan object , i need to set an specific language but i didnt see where set it

@chessBullet I'm here to help! To set a specific language for the transfer call function, you would typically need to specify the language within the transferPlan object or as a parameter in the function call, depending on how the API is designed. If the API documentation does not clearly state where to set the language, it might be an oversight or the feature may not be directly supported. However, if you're looking to include a call summary in Spanish when transferring the call, you might need to set the language preference for the summary generation before initiating the transfer. This could involve setting a language parameter or configuring the system to generate summaries in Spanish by default. If you can provide me with the exact name of the function you're using or more details about the API, I could give you more specific guidance. If this feature is not documented, you may need to reach out to the API support team for further assistance. Please let me know how I can assist you further!

the function is transferCall

@chessBullet The

transferCall

function allows you to transfer a call to a specified destination. However, if you're looking to set a specific language for the call transfer, this would typically be handled outside of the

transferCall

function itself. The language setting would usually be part of the system that handles the call after the transfer, or it could be a parameter set before initiating the transfer, depending on how your voice API is configured. If you need to set a specific language for the call transfer, you may need to configure the destination system to handle the language preference. If the

transferCall

function in VAPI supports language settings, it would be specified in the documentation or the API parameters. Since it's not mentioned in the context provided, it's likely that the language setting is not a direct feature of the

transferCall

function. If you have a specific language parameter that needs to be passed along with the

transferCall

function, please provide more details or check the documentation for the correct way to include language settings in your transfer plan. If this is not available, you might need to contact support for more information on how to implement language preferences in call transfers.

When use transfer call i want to send the summary call, but i cant to send the summary call in spanish

@chessBullet I understand that you want to send the call summary in Spanish when using the

transferCall

function. If the function itself does not provide an option to set the language for the call summary, you may need to generate the summary in Spanish before initiating the transfer and then include it as part of the transfer data. Here's what you can do: 1. Generate the call summary in Spanish before the transfer. 2. Ensure that the summary is formatted correctly and ready to be sent. 3. Use the

transferCall

function and include the pre-generated Spanish summary in the appropriate field or parameter that is designated for additional call information or notes. If you are unsure about where to include the summary or how to ensure it is in Spanish, please consult the API documentation for the

transferCall

function or reach out to the API support team for specific instructions on handling language preferences for call summaries. If there is a specific function or method within the VAPI to set the language for summaries, please provide more details or the function name, and I will assist you further. If this functionality is not documented, contacting support would be the best course of action.

Yes the summary call is in spanish but the voice no, the voice is english @Vapi

@chessBullet If the call summary is in Spanish but the voice delivering the summary is in English, you will need to adjust the voice settings to use a Spanish-speaking voice. This typically involves specifying a voice ID that corresponds to a Spanish voice when setting up the voice assistant or when generating the voice output. Based on the context you provided earlier, here's an example of how to set up a voice assistant that speaks Spanish using Azure's voice services:

json
{
  "voice": {
    "provider": "azure",
    "voiceId": "es-ES-ElviraNeural"
  }
}

In this example,

es-ES-ElviraNeural

is the voice ID for a Spanish-speaking neural voice from Azure. You would need to replace the voice ID in your current setup with the ID of a Spanish-speaking voice to ensure that the voice output is in Spanish. If you are using the

transferCall

function and need to include a voice summary in Spanish, make sure that the system or service handling the call after the transfer is configured to use a Spanish voice ID. If you have control over the voice settings, update them accordingly. If not, you may need to coordinate with the destination system's administrators to ensure they support and have configured a Spanish-speaking voice. If you need further assistance with configuring the voice settings or if the

transferCall

function requires additional parameters to specify the voice language, please refer to the API documentation or contact the API support team for more detailed guidance.

I can to include this JSON in transferPlan Object?

@chessBullet To include specific voice settings in the

transferPlan

object for the

transferCall

function, you would typically need to follow the API's schema for including such configurations. If the API allows for voice settings to be specified within the

transferPlan

, you would include the JSON configuration for the voice as part of the

transferPlan

object. Here's a hypothetical example of how you might include it:

json
{
  "transferPlan": {
    // ... other transfer plan settings ...
    "voiceSettings": {
      "language": "es-ES",
      "voiceId": "es-ES-ElviraNeural"
    }
  }
}

In this example,

voiceSettings

is a made-up key that represents where you might specify the voice configuration within the

transferPlan

. The actual key and structure would depend on the API's documentation. Please note that the above is just an illustrative example. You will need to consult the documentation for the

transferCall

function to determine the exact structure and keys required to include voice settings in the

transferPlan

. If the documentation does not provide this information or if the feature is not supported, you may need to reach out to the API support team for assistance. If you provide the exact structure of the

transferPlan

object or the documentation for the

transferCall

function, I can give you more precise guidance on how to include the voice settings.

in the dpocumentation i didnt found this example with voiceSettings @Vapi

@chessBullet If the documentation for the

transferCall

function does not include an example or mention of how to include

voiceSettings

within the

transferPlan

object, it's possible that the function does not directly support changing the voice settings as part of the transfer process. In such cases, voice settings are often configured separately from the call transfer functionality. You may need to set the voice preferences (such as language and voice ID) at a higher level in the system or within the configuration of the voice service you are using. If you need to ensure that the transferred call continues with a Spanish-speaking voice, you might have to: 1. Configure the destination system (the system to which the call is being transferred) to use a Spanish voice by default. 2. If the destination system allows dynamic voice settings, pass the voice configuration as metadata or additional information, which the system can then interpret and apply to the call. Since the

transferCall

function does not seem to support

voiceSettings

directly, I recommend reaching out to the support team for the Voice API you are using. They can provide you with specific instructions on how to achieve the desired voice language settings for transferred calls or clarify if there's a way to include such settings that may not be documented. If you have any other questions or need further assistance, please let me know!

how to connect with support? @Vapi

@chessBullet To connect with support for the Voice API you're using, you can typically follow these steps: 1. **Check the Documentation**: Often, the API documentation will include a support section with contact information or instructions on how to get help. 2. **Visit the Official Website**: Go to the official website of the Voice API provider. Look for links to support, help center, or contact us pages. 3. **Support Portal or Ticket System**: Many providers have a support portal where you can submit a ticket detailing your issue. You may need to create an account or log in to access this feature. 4. **Email**: If an email address is provided for support inquiries, you can send a detailed message explaining your issue and asking for assistance. 5. **Phone Support**: Some providers offer phone support. If a support number is listed, you can call and speak to a technician. 6. **Community Forums**: Some issues can be resolved with the help of community forums where you can post your question and get answers from other developers or support staff. 7. **Live Chat**: If the provider offers a live chat service on their website, you can use this feature to talk directly with support personnel. 8. **Social Media**: Some companies respond to support queries through their social media channels like Twitter, LinkedIn, or Facebook. Remember to have your account information, API details, and a clear description of your issue ready when you contact support. This will help them assist you more efficiently. If you need help finding the contact information for the Voice API support team, please provide the name of the API or the company that provides it, and I can assist you further.

@Shubham Bajaj this json is correct? "transferPlan": { "mode": "warm-transfer-with-summary", "summaryPlan": { "enabled": true, "messages": [ { "role": "system", "content": "Please provide a summary of the call." }, { "role": "user", "content": "Aqui está el resumen de la llamada:\n\n{{transcript}}\n\n" }, "voice": { "provider": "azure", "voiceId": "es-ES-ElviraNeural" } ] } }

@chessBullet The JSON structure you've provided seems to be intended for a

transferPlan

that includes a warm transfer with a summary and specifies voice settings. However, there appears to be a small formatting issue with the JSON structure. The "voice" object should be part of the "summaryPlan" or another appropriate section, but it's currently placed within the "messages" array, which is likely incorrect. Here's a corrected version of the JSON, assuming that the "voice" settings should be at the same level as "messages" within "summaryPlan":

json
{
  "transferPlan": {
    "mode": "warm-transfer-with-summary",
    "summaryPlan": {
      "enabled": true,
      "messages": [
        {
          "role": "system",
          "content": "Please provide a summary of the call."
        },
        {
          "role": "user",
          "content": "Aqui está el resumen de la llamada:\n\n{{transcript}}\n\n"
        }
      ],
      "voice": {
        "provider": "azure",
        "voiceId": "es-ES-ElviraNeural"
      }
    }
  }
}

In this corrected JSON, the "voice" object is now correctly placed within the "summaryPlan" object, but not inside the "messages" array. Please note that this structure is based on the assumption that the "voice" settings are allowed within the "summaryPlan" according to the API's schema. If the API documentation does not specify where to place voice settings, or if the "voice" object is not recognized by the API, this JSON structure may not work as intended. If you're unsure about the correct placement of the "voice" settings, or if the API documentation does not provide clear guidance, it's best to reach out to the API support team for clarification. They can provide you with the correct JSON structure for including voice settings in your

transferPlan

.

model.each value in tools.each value in destinations.transferPlan.summaryPlan.property voice should not exist @Vapi

@chessBullet Based on the error message you've received, it seems that the

voice

property should not be included within the

summaryPlan

object of the

transferPlan

. The API model does not recognize the

voice

property in that location, which means that the API does not allow for voice settings to be specified there. Given this information, you will not be able to set the voice settings directly within the

transferPlan

object for the

transferCall

function. The voice settings must be configured elsewhere, possibly at a system level or within the voice service you are using. If you need to use a Spanish voice for the call summary, you will likely need to: 1. Pre-configure the voice service to use a Spanish voice by default. 2. Ensure that the destination system to which the call is being transferred is set up to handle calls in Spanish. Since the

voice

property is not allowed in the

summaryPlan

, you should remove it from your JSON configuration to avoid errors. If you require further assistance on how to proceed with setting a Spanish voice for your call summaries, please reach out to the API support team for guidance on the correct approach.

the destination system is a cellphone, only i want to use a specific voice for the translate the summary call in spanish

@chessBullet If the destination system is a cellphone and you want to use a specific voice to translate the call summary into Spanish, you will need to handle the voice translation before the call is transferred. Since the

voice

property is not allowed within the

summaryPlan

object, you cannot set the voice settings directly through the

transferPlan

. Here's what you can do: 1. **Generate the Summary**: Create the call summary in Spanish as you have been doing. 2. **Text-to-Speech (TTS) Conversion**: Use a Text-to-Speech service with a Spanish voice to convert the summary text into audio. You would select a Spanish voice from the TTS provider (like "es-ES-ElviraNeural" from Azure, as you mentioned). 3. **Attach the Audio**: If the API allows, attach the generated audio file to the call or make it accessible to the recipient in some way. This could be through a link to the audio file or by playing the audio file into the call before transferring. 4. **Transfer the Call**: Use the

transferCall

function to transfer the call to the cellphone without including the

voice

property in the

transferPlan

. Since the

transferCall

function does not support specifying the voice settings, you will need to use a separate TTS service to generate the audio in the desired voice. After generating the audio, you can then proceed with the call transfer. If you need assistance with using a TTS service or have any other questions, please let me know!

@chessBullet heck the message property for setting spanish content, do let me know if you have more doubts.

json
{
  "type": "number",
  "number": "insert-number-here",
  "description": "insert-description-here",
  "message": {
    "type": "custom-message",
    "contents": [
      {
        "type": "text",
        "text": "insert-spanish-message-here",
        "language": "es"
      }
    ]
  },
  "transferPlan": {
    "mode": "warm-transfer-say-summary",
    "summaryPlan": {
      "enabled": true, 
      "messages": []
    }
  }
}

yes this property is for user message, but my cuestion is in this property "summaryPlan": { "enabled": true, * "messages": []* }. beacuse, when transferring the call to a user, the assistant tries to read the transcript call in English and since it is in Spanish it sounds very strange

@chessBullet add this to the system prompt:-

DO GENERATE TRANSCRIPTION IN SPANISH LANGUAGE ONLY.

Do let me know how it goes, after making the changes.