I'm using the new keypadInputPlan feature to take in account numbers, but when I provide the number followed by # (with # set as delimiter) or * (with * set), the assistant is unable to recognize it, regardless of whether or not I include a timeout of 10 sec or 0 sec. Is anyone else running into this? No callID relevant. Timestamp around 11:10 pm PT. 2 example settings shown https://cdn.discordapp.com/attachments/1347830438055514152/1347830438235996251/Screenshot_2025-03-07_at_11.15.40_PM.png?ex=67cd4069&is=67cbeee9&hm=1f4ab574c9d300b2aeb75c9d469b0144417c1310c360658589ccf2af81ef328e& https://cdn.discordapp.com/attachments/1347830438055514152/1347830438734856305/image.png?ex=67cd406a&is=67cbeeea&hm=4330a031e6f356508a54c574fc972a0180683ee208d91d42e74ac505809d8fc7&

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!

CallIDs include c57df875-242e-43c8-af41-1b2d85ee1deb (main example) 5fa49e32-0874-46de-8d7b-77492fcece12

allow me sometime to get back to you.

I’ve had this open for a week

are people really using this already in production ? I feel the calls are very random sometimes its snappy and quick and without any change it will take seconds before it responds eventhough latceny ms shows 750ms

Keypad input plan isn't supported yet. So, wouldn't suggest you to use this feature at the moment.

@Sahil what about this then? announcing something that does not work? https://docs.vapi.ai/changelog/2025/2/27

Hey, ChaloVega, the keypad input plan is working now which you can make use of it. For your further issues or inquiries, please create a new support ticket.