Voice Agent can't read the response(results) data
# support
d
I have just setup a voice agent that makes a tool call to an api endpoint that returns data in this format: { "results": [ { "toolCallId": "call_pKkNod7t791RIuox", "result": "Organization: EduTech University\nIndustry: Education\nAccount Status: Active\nAccount Tier: Standard\nOpen Tickets: 4\nSatisfaction Score: 4.3/5.0\nPrimary Contact: Dr. Mary Wambui (Director of ICT)\nEmail: mary.wambui@edutech.ac.ke\nPhone: +254-724-890123\nLast Contact: 2024-09-14\nContract Value: KES 8,500,000\nServices: Campus Network Infrastructure, Educational Technology Solutions, Student Data Security, Remote Learning Platforms" } ] } The above is dummy data. The voice agent keeps saying that it is still waiting for a response yet the api request was made and responded appropriately according to vapi.ai api docs. Kindly help fix this. https://cdn.discordapp.com/attachments/1417564133200494623/1417564134039617718/image.png?ex=68caf0fa&is=68c99f7a&hm=c9edf240cfe07e6a1ffc2db382b9787d88e422f57f24c429c7240278bb6c6939& https://cdn.discordapp.com/attachments/1417564133200494623/1417564134525894837/image.png?ex=68caf0fa&is=68c99f7a&hm=8ee79f6dfe6d2be3aa03cd427ce4466f26db6d058d2ec2697b5a22a45950ac91&
v
Try updating your API response to include a
message
property alongside the
result
, which helps Vapi know what to say to the user. For example:
Copy code
json
{
  "results": [
    {
      "toolCallId": "call_pKkNod7t791RIuox",
      "result": "Organization: EduTech University\nIndustry: Education\nAccount Status: Active\n...",
      "message": "Here are the details for EduTech University: Account is active, 4 open tickets, satisfaction score 4.3 out of 5. Primary contact is Dr. Mary Wambui."
    }
  ]
}
This should prompt the voice agent to read the message aloud and mark the tool as completed. See [Vapi changelog April 2025](https://docs.vapi.ai/changelog/2025/4/26) for details. Source: - [Changelog](https://docs.vapi.ai/changelog/2025/4/26)
c
Hey, Could you provide the call ID where you experienced this issue? We want to review the logs to identify the cause. Also, please share: - The exact timestamp of when this happened - The response you expected to get - The response you actually received This information will help us figure out what went wrong.
2 Views