@sgs It's great to hear that you're going live next week! Regarding your concern, yes, it is technically possible for non-human or spam attacks to occur on any telephony system, including those that handle inbound calls. These attacks can be in the form of robocalls, spam calls, or even fraudulent call patterns designed to inflate costs. VAPI takes security seriously and has measures in place to help mitigate such risks. However, it's also important for you to implement additional safeguards to protect your system. Here are some steps you can take: 1. **CAPTCHA for Calls**: Implement a CAPTCHA-like system for calls to ensure that only humans can interact with your service. 2. **Call Analysis**: Use real-time call analysis to detect and block spam patterns. 3. **Blacklisting**: Maintain a blacklist of known spam numbers and block them proactively. 4. **Rate Limiting**: Set up rate limiting to prevent a high volume of calls from a single source in a short period. 5. **Anomaly Detection**: Monitor for unusual call patterns that could indicate an attack and set up alerts or automatic blocking. 6. **Whitelisting**: Allow calls only from known, trusted numbers if applicable to your use case. VAPI may already have some of these features built-in or available as add-ons. To ensure you have the right measures in place and to understand the specific capabilities of VAPI in this regard, I recommend reaching out to the VAPI support team. They can provide you with detailed information on the platform's anti-spam features and guide you on best practices for securing your inbound calling setup. Would you like me to assist you with anything else or provide more detailed guidance on setting up these safeguards?

let's say a mass attach happened then if it's because of Vapi we will do the needful required work.

Are there safeguards in place already? Is that what you are saying?

I see two maximum concurrent calls and limit billing value.