No changes are taking effect
# supportb
bsolo
12/01/2025, 7:49 PMHi,
I am attempting to update certain settings on my VAPI agent, but any time I save the changes and test a new call, none of the changes I made seem to take effect.
The biggest ones I am noticing are the voice itself (always seems to default to ElevenLabs voice), as well as the background audio (always defaulting to office sound).
I have tried to create a new agent with all new settings, but still it seems to just ignore all of them and just use the defaults. Can anyone advise me on what could possibly be going wrong?
v
Vapi Support Bot
12/01/2025, 7:49 PMIt looks like many VAPI agent settings—such as voice provider and background audio—must be set via the API, not the dashboard. Try updating your agent using the API with a payload like:
Copy code
json
{
"voice": { "provider": "your-provider" },
"backgroundSound": "off"
}b
bsolo
12/01/2025, 8:10 PMWhat’s the point of a dashboard if it doesn’t even work?
bsolo
12/01/2025, 8:44 PMWhen I create a brand new agent, with completely new settings, I still get the exact same agent as before. It's almost like no matter what settings I do, the same exact assistant is being used for all the calls. I have checked the logs as well, and I can see that the correct assistant is being used, but the call is still a completely different assistant
bsolo
12/01/2025, 8:45 PM@Vapi
a
Ajcreator01
12/01/2025, 9:17 PMHey! This issue usually happens when the agent is running from an older cached config. Even if you update the settings, the live agent might still be using the previous version.
Here are the main things to check:
1. Publish the agent after saving
Saving alone doesn’t update the live agent. Make sure you hit Save → Publish, then test again.
2. Confirm your call entrypoint is linked to the updated agent
If you're using Twilio or a dialer, they might still be calling an older agent ID.
3. Check your audio override settings
Sometimes background audio + ElevenLabs fallback forces defaults.
Make sure no fallback voices or scenes are overriding your custom settings.
If you want, drop me a message and I can take a quick look at your setup this is something I fix often and I can help you get it working properly.
b
bsolo
12/01/2025, 9:49 PMThis doesn’t seem to be the case, because even brand new agents don’t conform to the new settings
bsolo
12/01/2025, 10:16 PMIf I initiate a call through the API, it appears to use the same defaulted agent, but if I start a call through the VAPI UI, it applies the correct agent. When I inspect the call information, all the information looks good on both calls. The assistant ID seems to be correct, and all the other settings are applied, but the actual agent on the phone is completely off.
c
Chiranjeet Mishra
12/03/2025, 3:03 PMHi bsolo,
It sounds like you're experiencing issues with your agent settings not updating properly. Here are some steps to help resolve this:
1. Publish Changes: After saving any changes in the dashboard, ensure you hit the "Publish" button. Saving alone doesn't update the live agent.
2. Check Call Entry Point: Ensure your integration (e.g., Twilio or a dialer) points to the updated agent ID. Sometimes, these services may have cached older settings.
3. Inspect API vs Dashboard Settings: Some settings, such as voice provider and background audio, might require updates through the API rather than the dashboard. You can use the following payload to update your agent via the API:
Copy code
json
{
"voice": { "provider": "your-provider" },
"backgroundSound": "off"
}