That usually happens when the agent doesn’t recognize how to interpret the backend’s JSON structure — it expects a plain text result (string) but receives an object instead. Even though the response contains the price, the agent can’t read nested keys like "result": {"price": "1100"}.

Hi @Joshua , yes I tried returning the response in plain text(The price for the service is 1100) but still it does not pass on the voice agent

That’s interesting if it’s already returning plain text and still not reaching the agent, it’s likely an issue with how the tool output is being passed back to the speech module. I can take a quick look at your setup and pinpoint why the message isn’t being delivered properly it’s usually a simple fix once I see the flow. Would you mind messaging me a quick screenshot or JSON snippet of your tool’s response setup? I can help you sort it out right away.

do you mean this? https://cdn.discordapp.com/attachments/1426246111269748766/1427133672783609997/Screenshot_2025-10-13_111914.png?ex=68edc14e&is=68ec6fce&hm=cd2739ef3fcaf9eaa018a86c734dd97bc82c1949fcc945e432bfb3b5c6bb4ec8&

Yeah, I see what you mean — that confirms the backend’s fine but the agent isn’t catching the tool output properly. It’s most likely a mapping or tool-return handler issue inside your VAPI setup, not the text itself. I can take a quick look and fix the flow so it actually speaks the response back. if you don't mind you can just send me a request can walk you through the fix?