I am pointing the bot workflow to: f7780849-87cb-46f8-ba08-e8bbb499fc72 but when I call in it is go to workflow: 9af4908a-0e1c-439e-8240-cffff69ac733 Part of bug: No phone number/SIP trunk yet talks to bot

To resolve the issue of calls going to the wrong workflow, please ensure that the phone number or SIP trunk is correctly linked to the desired workflow. You can do this by checking the

workflowId

associated with your phone number settings. Here’s how you can verify or update the workflow ID using the API: 1. **Get the Phone Number Details**:Use the GET endpoint to retrieve the phone number details and verify the

workflowId

. For example:

bash
   curl https://api.vapi.ai/phone-number/<id> -H "Authorization: Bearer <token>"

[Phone Numbers GET](https://docs.vapi.ai/api-reference/phone-numbers/get) 2. **Update the Workflow ID**:If necessary, update the workflow ID using the PATCH endpoint to ensure it points to

f7780849-87cb-46f8-ba08-e8bbb499fc72

. To do this, send a PATCH request with the correct

workflowId

. By ensuring that the correct workflow ID is linked to your phone number, calls should be routed appropriately. Let me know if you need further assistance.