Incoming call flow
# support
n
So it seems when you have 2 calls inbound (Vapi phone number) at the same time or closely one after another the second call will receive a 429 error. It might be that as long as the phone number being used the issue may persist. Agree this is an edge case however is there a solution or work around?
c
Hi Noid, The 429 error typically indicates too many requests in a short period, often due to rate limiting. Here are some options to handle concurrent inbound calls: 1. **Increase Your Number Capacity**: If you're encountering this often, consider upgrading to a plan that supports more concurrent calls. 2. **Load Balancing**: Implement a load balancer to distribute call requests more evenly across available lines. 3. **Use Multiple Numbers**: Distribute your inbound calls across multiple Vapi numbers to prevent any single number from hitting the limit. 4. **Queue Unanswered Calls**: Use call queuing to handle calls until an agent is available, reducing the chance of hitting rate limits. For more detailed configurations, you might want to explore specific telephony integrations that support higher capacity needs. If you have specific telephony providers like Twilio or Vonage, checking their configurations could also offer solutions. You can refer to our [Outbound Calling](https://docs.vapi.ai/calls/outbound-calling) documentation for additional insights into handling multiple lines and managing high call volumes.
n
thanks for the advice
c
No worries. Let us know if you have any questions
3 Views