setting the squad seems to work when using simple squad: { members: [ {assistantId: ...}, {assistantId: ...} ] } Nevertheless as soon as I add assistantDestinations to make transitions semaless it raises this error. Here is what my server returns: {"squad":{"members":[{"assistant_id":"5f4faadd-5888-4ad7-a504-8f3035830b94","assistant_destinations":[{"assistant_name":"faq","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"0c2fd21f-d0bf-4353-a76d-0348b879cb75","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"beecc680-7d5b-4c2c-bc1f-771dbc0aefdf","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"faq","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"67ed59f3-2ad6-44b2-b244-4e4f0a4ac83f","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"faq","message":" "}]}]}} @Shubham Bajaj any input appreaciated, i'm struggling for 2 days to make that happen in production because of the absence of documentation I just don't know where to find this informations...

message has been deleted

thank you very much but These threads are not relevant unfortunately @Vapi

@paul gaston I'm sorry to hear that the provided information wasn't helpful. It seems like you're encountering an issue with setting up a squad with assistant destinations in your system. The error could be related to the format or the content of the

assistant_destinations

you're providing. To better assist you, could you please provide more details about the error message you're receiving? Knowing the exact error message or code can help pinpoint the issue. Additionally, it would be helpful to know if there are any specific requirements or formats that your system expects for the

assistant_destinations

field. If the error message is not clear or if you're unsure about the requirements, it might be necessary to consult the documentation for your system or reach out to the technical support team for the API or platform you're using. If there's any other way I can assist you, please let me know!

Of course: https://cdn.discordapp.com/attachments/1309482988290965514/1309483900187185152/message.txt?ex=6741bf6a&is=67406dea&hm=8a1eb29709de30b99946eb2f78dd0e44674538c6f44a730f873e70cde8e69e17&

@paul gaston It seems there might have been an issue with your response as it came through empty. Could you please try sending the details of the error message again? I'm here to help you resolve the issue you're facing with setting up the squad and assistant destinations.

my server response: {"squad":{"members":[{"assistant_id":"5f4faadd-5888-4ad7-a504-8f3035830b94","assistant_destinations":[{"assistant_name":"faq","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"0c2fd21f-d0bf-4353-a76d-0348b879cb75","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"beecc680-7d5b-4c2c-bc1f-771dbc0aefdf","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"faq","message":" "},{"assistant_name":"booking","message":" "}]},{"assistant_id":"67ed59f3-2ad6-44b2-b244-4e4f0a4ac83f","assistant_destinations":[{"assistant_name":"manager","message":" "},{"assistant_name":"spelling","message":" "},{"assistant_name":"faq","message":" "}]}]}} vapi response, somewhere in the payload appears: "assistantRequestError"=>"Invalid Assistant."

@paul gaston It appears that the error message "Invalid Assistant" suggests there might be an issue with the assistant identifiers or the way they are being referenced in the

assistant_destinations

. Here are a few steps you can take to troubleshoot the issue: 1. **Verify Assistant IDs**: Ensure that the

assistant_id

values you are using are correct and correspond to valid assistants in your system. 2. **Check Assistant Names**: Make sure that the

assistant_name

values in

assistant_destinations

match exactly with the names of the assistants you have set up. This includes checking for correct spelling and case sensitivity. 3. **Message Content**: The

message

field currently contains a space (" "). If the API expects a non-empty message or a specific format, this could be causing the error. Verify if there are any requirements for the content of the

message

field. 4. **API Documentation**: Since you mentioned a lack of documentation, if there is any available, review it thoroughly for any specific requirements or constraints regarding the setup of

assistant_destinations

. 5. **Contact Support**: If after checking the above points the issue persists, it may be necessary to contact the support team for the API or platform you're using. They may be able to provide more detailed insights into the error and how to resolve it. If you have access to any logs or more detailed error messages, those could also be very helpful in diagnosing the problem. If you need further assistance, please provide any additional information you can, and I'll do my best to help you.

i think i understand it's about the case

@paul gaston Certainly! To contact support, you can send an email to the VAPI support team. Here is the email address for your convenience: [support@vapi.ai](support@vapi.ai) Please include as much detail as possible about the issue you're facing, including the error message "Invalid Assistant" and the context in which it occurs. This will help the support team understand your situation better and provide you with the assistance you need. If there's anything else I can do for you in the meantime, please let me know!

@Vapi can you provide an example of seamless transition within ssquads as a respons to assistant request?

@paul gaston Certainly! A seamless transition within a squad involves configuring assistant destinations so that when certain conditions are met, the conversation can be handed off from one assistant to another without the user noticing any disruption. Here's an example of how you might configure a seamless transition within a squad:

json
{
  "squad": {
    "members": [
      {
        "assistant_id": "assistant-1-id",
        "assistant_destinations": [
          {
            "assistant_name": "booking",
            "message": "Please handle this booking request."
          }
        ]
      },
      {
        "assistant_id": "assistant-2-id",
        "assistant_destinations": [
          {
            "assistant_name": "faq",
            "message": "Please provide the user with FAQ assistance."
          }
        ]
      }
    ]
  }
}

In this example, when the first assistant (

assistant-1-id

) encounters a booking request, it will pass the conversation to the assistant named "booking" with a message to handle the booking request. Similarly, if the second assistant (

assistant-2-id

) needs to provide FAQ assistance, it will transition to the assistant named "faq" with an appropriate message. The

assistant_name

should correspond to the name of the assistant you want to transition to, and the

message

is what you want to pass along to the next assistant, which could be a command, a prompt, or context for the next assistant to continue the conversation. Please note that the actual implementation of seamless transitions will depend on the capabilities and configuration options provided by the VAPI platform you are using. If you need more specific guidance, please consult the documentation or contact support for further assistance.

are you sure about the case @Vapi ?

@paul gaston I apologize for any confusion. The case sensitivity of the

assistant_name

field can indeed be a critical factor, as most systems differentiate between "AssistantName", "assistantname", and "Assistantname". It's important to use the exact case as defined in your system for the assistant names. If the assistant names are case-sensitive and you've used the wrong case in your

assistant_destinations

, it could lead to the "Invalid Assistant" error you're encountering. Make sure that the

assistant_name

in each

assistant_destination

matches the case exactly as it is registered in your system. If you're unsure about the case sensitivity or the correct format of the assistant names, please refer to your system's documentation or reach out to the support team for clarification. They should be able to provide you with the correct names and cases for your assistants.

Hey @paul gaston duplicate ticket to the previous tickets please, check the previous ticket shared the solution over there.