I’ve been running into an issue with inbound agent switching. When I change the inbound agent assigned to a phone number multiple times within a short period, the UI immediately shows the correct (new) agent, but when I call the number, the call is still answered by the previously assigned agent. It usually takes around 20–30 minutes before the correct agent actually starts answering the calls. This delay is making it difficult to quickly switch agents when needed. Could you please check why this happens and if there’s a way to ensure the agent updates take effect instantly?

Suggestion: To help resolve the delay in agent switching, try updating the phone number-to-assistant assignment using the API directly, which may bypass any UI caching issues. For example, use the following PATCH request:

bash
curl -X PATCH https://api.vapi.ai/phone-number/{id} \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"assistantId": "new_assistant_id"}'

If the issue persists, please report it with the affected phone number and steps to reproduce so the support team can investigate backend propagation or caching delays. [See API reference](https://docs.vapi.ai/api-reference/phone-numbers/update?explorer=true) Source: - [Update Phone Number (API Reference)](https://docs.vapi.ai/api-reference/phone-numbers/update?explorer=true)

It's still not helpful

I can help you look into why the reassignment takes 20–30 minutes to reflect, likely related to call routing cache or number provisioning delays. A possible fix is forcing a refresh or adjusting how inbound mappings are cached. Have you already tried re-provisioning the number after switching agents? I’d be happy to walk you through an instant-update workaround. @Uros Jovanovic

Hey @Lordvickthor thank you for offering the walk-through, that would be perfect!

Perfect! I can walk you through the process step by step so we can resolve this quickly. Let’s continue the discussion privately to go over the details and get it working instantly.