In a SQUAD, how do I prevent one assistant from an...
# support
b
I'm using the same voice and had it working to appear as a single conversation with a single assistant. However, the first assistant has - all of a sudden - started announcing that she is going to transfer the call to her assistant who will be able to offer further assistance. This is NOT what I want to happen. Is there a way to prevent this behavior?
v
@BrentPope I understand that you're experiencing an unexpected behavior where the voice assistant is announcing a transfer to another assistant, which is not part of your intended design. To address this, we need to check your VAPI settings to ensure that the assistant is configured correctly. Could you please provide more details about your current setup? Specifically, I need to know if there have been any recent changes to your voice application or if this behavior started without any modifications on your end. Additionally, it would be helpful to know if you're using any specific features or conditions that might trigger this transfer announcement.
You can continue this conversation by mentioning me in the message.
c
@BrentPope I entered this: Note: Do not tell the caller you are transferring to a different assistant.
In the TASK section of my 1st assistant and seems to be working by not saying it is transferring.
I'm running into the problem of initial assistant not transfering to specified assistant or or assistant in squad isn't picking up. Do you mind sharing the setup. I creating the squad within the platform and routed each sub assistant back to the original assistant.
PS - I know negative prompting isn't the best but seems to improve it
s
Through API call, you can remove this part or change it.
b
Hi Christian, thanks for the tip. I tried that briefly and it didn't work, although I haven't spent much more time on it. I think it may be because I had removed a reference to the [SCRIPT] for the assistant to follow. That was because I moved my script to the second assistant so it looked like it didn't belong in this prompt. But, I have found that by bounding what I want each assistant to say within a [SCRIPT] and [END SCRIPT] structure AND specifying which parts are for it to say (I put the parts I want it to speak in single quotes and tell it that everything else in the script is reference material for it) it seems to help keep the assistant from wandering too far. Anyway, I added back the [SCRIPT] reference and put the relevant part in my first assistant prompt but haven't tested it yet. Here it is, I'll comment again after I get a chance to do some testing. Your comments appreciated:
Sorry, I don't understand. I am creating this squad from Make.com through the API. Could you elaborate?
s
He was saying make api call to change default say/response messages during assistants transfer. Each assistant/tool/function has default messages array and there are 4 types of messages. You require to change the default behaviour of
request-start
message type. Checkout api from here: https://api.vapi.ai/
b
the link just opens this: 🥺 what if 👉👈 we could talk to our computers jk... unless?
s
api.vapi.ai/api#/
the above is correct url
b
Hey again Christian, I played around with the prompt and it seems to be working a lot better. Here it is in markdown so you can read it directly:
c
Hi @BrentPope glad it is working out better for you. I'll take a look at the prompt!
b
I don't have request-start in my squad json, and I wouldn't know what to change it to. Could you provide the json structure of that key, and the possible values? Is there any documentation on this feature I could read?
Also, the only place I see request-start is in tools. Is the assistant transfer in a squad considered a tool?
s
Just use the request-start and provide the message as empty string
s
All tools functions squads work on same principle.
b
I still don't understand. I assume I just need to add -- "request-start":"" SOMEWHERE in the squad structure and I've tried a LOT of variations. Could you please let me know where it goes? Thanks,
s
Over the squad we don't have request-start it is for tools. For the squads we have message where we link assistant to destinations.
b
I tried that, doesn't work. Here is what it looks like: "assistantDestinations": [ { "type": "assistant", "message": "OK", "request-start":"", "description": "Transfer the user to Izzy", "assistantName": "Izzy" } ]
When I add the request-start the assistant can't be retrieved.
s
My mistake Vapi Squads doesn't have request start they only have message. which is similar to the request-start of tool call.
b
I tried setting message to empty string. All that does is cause it to freeze. It gets to that point and waits for the caller to say something. Then it still says it is transferring the call. And yes I do have assistant speaks first set to true. That doesn’t seem to do anything.
s
can you share your config and the prompt>
4 Views