Voicemail detection and format plan not working.
# support
v
@Bilal Abbasi I'm sorry to hear that you're experiencing issues with the features you've enabled. To assist you better, I'll need a bit more information about the problems you're encountering. Could you please provide me with the following details? 1. For the hangup on voicemail feature, could you describe what happens when a voicemail is detected? Is the call not hanging up as expected? 2. Regarding the replacement of numbers to digits, could you give me an example of where this is not working? Is it during a text-to-speech process or somewhere else? 3. For the format plan to replace address abbreviations, could you provide an example of an address that is not being formatted correctly? Once I have this information, I'll be able to help you troubleshoot the issues more effectively. If you have any error messages or logs that you could share, that would also be very helpful.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
b
@Shubham Bajaj I just tested and formatPlan replacement and numbertodigitcutoff is not working for me. Here is the callid 110d3ced-0904-42a0-8863-47095e50e89c
s
@Bilal Abbasi I checked today regarding
numbertodigitcutoff
. There is some confusion, so please give me some time to get back to you properly with examples and all possibilities.
@Bilal Abbasi The code searches for numeric strings (such as 123, 43, 321) using REGEX. It invokes the function with the parameters: yearCheckEnabled set to true, and numberToDigitsCutoff set to 1000. Since yearCheckEnabled is true, any integer less than 2025 is returned unchanged, as the code interprets it as a "year" and does not convert it to words. Therefore, numbers like 123, 43, and 321 remain numeric, with no alteration to the actual digits.
This implies that any integer below 2025 is considered a "year," prompting the code to immediately return the original digits (e.g., 123 remains "123"). Even if you adjust the numberToDigitsCutoff, the "year" check takes precedence and always returns the digits for any number less than 2025.
By design, when yearCheckEnabled is true and the number is less than 2025, the original digits are preserved.
So you have to pass english words for numbers less than 2025.
working_example
🔵 Voice Input Formatted: "two thousand twenty five 2024 two thousand twenty six two thousand twenty seven", Original: "2025 2024 2026 2027"
@Bilal Abbasi All the strange expansions ("thISLAND", "regaROADing", etc.) result from the formatReplacements step matching partial substrings inside words, instead of matching only whole words.Consequently, little sequences like “rd,” “ctr,” “ter” get replaced in the middle of words, producing “regaROADing,” “eleCENTERRACEic,” etc.
@Bilal Abbasi I need your help - I've written documentation about the formatting plan. Could you please review it and let me know if it helps you understand everything? I'm looking for raw, honest feedback. If it works well, I'll push it to the official docs. https://vapi.notion.site/Voice-Formatting-Plan-182008c8393f809f8153fef6a847eba8?pvs=4
b
Thanks @Shubham Bajaj So this document makes 100% sense to me, and i am thinking to change the address from the variable i am passing to VAPI. I thank you for taking your time and getting this document ready. Thanks heaps.
3 Views