Hi i dont know whats been happening on VAPIs end but we have a template setup with the settings we like, so that its easier to maintain the voice agents that we're utilising. However it seems these settings get completely adjusted automatically and wiped out when vapi makes changes, or does something in the back end. We have settings to wait for the customer to speak but instead this is the 4th time these types of settings have changed and caused a massive impact that we have no visibility over until its too late. Could i speak to someone about this as its an ongoing issue that as we grow, and utilise this platform that costs 50%+ of our call cost, it causes a larger overhead for many of our agents we setup Thank you Daniel

Hi Daniel, I understand your frustration with the template settings being automatically changed without notice. This sounds like a serious issue affecting your operations, especially given that it's happened multiple times. I've escalated your concern to our technical team right away. Someone who specializes in template configuration and backend changes will reach out to you directly to address this recurring problem. Thank you for bringing this to our attention and for your patience while we work to resolve this. We definitely want to ensure your voice agents maintain the settings you've configured. 👍

Thank you for your quick response, I apprecaite you looking into this for us

Hey Daniel, hey Daniel, Sorry for your experience. When you mentioned automatic adjustment of settings causing issues, can you brief it more exactly what's happening for you and what you were expecting? If you can record a Loom video, it will be really helpful. And most likely, you are on the daily channel for your organization, and because of this, you receive daily updates, and things feel like they're broken for you (which is not true). So you have to change your organization channel from daily to weekly. To confirm on this, I'll also request you to share your organization ID so I could take a look.

Hi, the scenario is that: - we've setup a template with the settings we want - we duplicate the template to create new agents - So that the multiple AI agents utilisng the same settings. - we are utilising many of the agents for similar purposes. - our reporting and insights into calls being done, annoy customers with the bot interupting and the timing being messed up. - we then look into the settings and they are difference from what we have set in the template, and even the template is changed. this feels like a blanket change across all our agents. - we've also seen when new updates are made any settings are removed back to vapis default not our own previous settings if new settings are set. e.g. smart endpointing was set to on, then a feature was rolled out to select it, then the smart endpointing is removed, andi need to select a provider once again, when the reality is that vapi is the default and should have been a migration to ensure these customer settings are kept when rolling out updates.

when I say a channel, a channel means the production environment. We have two environments: one is daily and weekly. If your organization is on the daily environment, that means it receives daily updates. You might get features which are broken or require some fixes. On the other hand, if your organization is on the weekly channel, you receive only updates which are fixed, tested, and completely secure to use in your production environment. Going through your previous statements, I came to a conclusion that you might be on the daily channel, which is why I asked for your organization ID to confirm it. As per your last statement, assistant config got swapped/changed. Share the Assistant ID and the Organisation ID. I will do the review and let you know if there is anything on our side. We are transparent about it.

Hi,

Hi, checking if this is resolved/solved for you?

the last issue has been solved but the main issue here is the automated changing of settings by vapi when new features / branches are rolled out (my guess)

Hey Daniel, Thanks for pointing this out. If you can share some steps to reproduce it or a loom video describing the odd behavior, I can definitely try to get it fixed. I'm really sorry for your bad experience.