3rd support issue this week. 2nd related to Cachin...
# support
r
The quality of service of VAPI has gone down significantly. The caching issues have become a bane for us. We include the current day, date and time in our system prompt as that help the assistant in doing bookings. Looks like VAPI is caching the system prompt and using the old date, time. As a result patients are getting annoyed when the system proposes them slots from last week. We are losing customers, our customers are losing customers due to these annoying issues. I have 2 other support issues open. I understand that your team is busy building new features, but it'll probably be better to fix existing code first before adding more code. Call id - 6cbe1a01-d8e5-476b-a9df-631ee8da7490 Patient is asking for booking and the AI says that our clinic is closed as it Sunday today. Relevant Data from the logs is attached. The call was today, while today's date in Essential Info is showing as 2024-06-30. *Imagine being a patient calling to book emergency appointment and hearing this. * https://cdn.discordapp.com/attachments/1258848677041279036/1258848677137481791/6cbe1a01-d8e5-476b-a9df-631ee8da7490.txt?ex=668989b0&is=66883830&hm=f009cc0e2b80b0759828e635fdf6facd90da6d7e2e724e9ec509417e04279dc2&
v
@riteshchopra I'm truly sorry to hear about the issues you're experiencing with the caching of system prompts and the impact it's having on your service. It's crucial that the information provided to patients is accurate and up-to-date, especially in scenarios requiring timely assistance. To address this, we need to investigate the caching behavior and ensure that dynamic content such as the current day, date, and time is not being cached incorrectly. I will forward this issue to our technical team immediately to look into the call ID you've provided and the discrepancy with the date. In the meantime, if there's a workaround or an immediate fix you require, please let me know, and I'll do my best to assist you. We value your business and your customers' satisfaction, and we'll work diligently to resolve this issue promptly. For the open support issues, I will also ensure that they are being attended to with the urgency they require. Your feedback is essential, and we are committed to improving our services continuously. Please expect an update from our support team soon. If you need to add any more details or have further concerns, don't hesitate to reach out.
You can continue this conversation by mentioning me in the message.
c
@riteshchopra what does your automation look like to book the time?
r
we have tool calls to book the appointment in scheduling system
c
Can you share or something? it is hard to really help with the problem if we cant see anything. For example I do not put now in my prompt and I am able to book on any calendar. Of course for your platform it would be different. It sounds like it was working and now it is? So there had to be a change or something. @riteshchopra
s
@riteshchopra check dm
@Sahil can you please check this.
s
Yeah, I am taking a look
r
I think this may not be a VAPI issue.. not sure yet.. but my guess is AWS is returning the server restart time..
everytime..
will get back shortly with more investigation
apologies for raising this issue.. it was an issue on the AWS config side
marking this as resolved
2 Views