The assistant doesn't announce the dynamic message...
# support
a
The transfer-destination-request is working and makes the transfers. The thing is that I would like the assistant to announce the name of the person that it is transferring the call to. As you can see, I have it in the message but it doesn't say it and instead says 'transferring the call now'. How can I modify it to say that message? Here is the server response that I have. As I said, the transfer to the number works but it doesn't say the message and says 'transferring the call now'. { "destination": { "type": "number", "message": "I will transfer the call to {{11.nombre}}", "number": "{{11.numero_telefono}}", "numberE164CheckEnabled": true, "callerId": "{{11.numero_telefono}}" } }
a
HeyAlex Contreras Thank you for creating the ticket! A member of our team will reach out to you shortly.
a
@Shubham Bajaj the knowledge base is working now, thanks. Can you help me with this new issue?
v
@Alex Contreras To ensure that the assistant announces the name of the person it is transferring the call to, you need to make sure that the
message
field in your server response is being utilized correctly by the assistant. The message should be dynamically replaced with the actual name of the person before the assistant reads it out. If the assistant is not saying the message as intended, it could be due to a couple of reasons: 1. The template variable
{{11.nombre}}
is not being replaced with the actual name when the message is processed. 2. The assistant's transfer call functionality might not be configured to read the
message
field from the server response. To resolve this, you can check the following: - Ensure that the template variable
{{11.nombre}}
is correctly populated with the person's name before the response is sent to the assistant. - Verify that the assistant's transfer call functionality is designed to read and speak the
message
field from the server response. If you have access to the assistant's configuration or script, you can look for the part of the code that handles the transfer call and make sure it is programmed to read the
message
field and use it as the announcement. If you're not sure how to make these changes or if the problem persists, please ask support for more info on this. They will be able to provide you with specific guidance based on the system you are using.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
Hey @Alex Contreras To help track down this issue, could you share: - The call ID This would really help me figure out what went wrong!
a
@Shubham Bajaj Call ID: 58274797-5b81-47aa-9824-f98059fbf9d7 c3f90ef3-ac2a-469b-8cd3-847eb87a0a83 1f908716-8552-46de-8095-d8dc1ae4ad3d
hi @Shubham Bajaj here is the update you told me to do but now it directly transfers the call without saying anything: { "type": "transferCall", "destinations": [], "messages": [ { "type": "request-start", "contents": [], "content": "", "conditions": [] } ], "function": { "name": "probandoCambioDeLlamada" } }
@Shubham Bajaj I'm making a transfer-destination request, just to clarify
@Shubham Bajaj did you find a solution?
s
@Alex Contreras I just made by mysefl few tests, let me check with the team, and get back to you!!
a
@Shubham Bajaj thank you so much, I appreciate it!
s
@Alex Contreras it's an bug and I have created a ticket for it. I will let you know once it is resolved.
a
Hi @Shubham Bajaj , thanks for your help! Do you think this will take more than five days? I just need to inform the client that we can't add that dynamic message