Thank you @Shubham Bajaj @User @AiTitus 🙂 I was able to add that but on call logs it shows no assistant assigned and due to that I am not able to get insights of call on dashboard like chatdash Is there a way to get insights for this chatbots in chatdash bcx there they only ask for agent id but in calls logs at vapi shows no assistant assigned and even chatdash is blank when I connect it to my agent? https://cdn.discordapp.com/attachments/1353567886358089829/1353568049634213919/image.png?ex=67e21ffb&is=67e0ce7b&hm=669a8cda7b34cc7715ccc592243d2bae92289b7ba35ff812614c4cb8f52e3133&

I see you're having trouble getting insights in chatdash because your Vapi call logs show "no assistant assigned." To help troubleshoot this issue more effectively, could you please share: 1. How are you currently configuring your phone number in Vapi? Are you using the dashboard or API to assign an assistant? 2. Have you verified that your assistant ID is correctly set on your phone number? This is crucial for [utilizing Voice AI with that number](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336652401733668864). 3. Are you using any webhook configurations or server URLs for dynamic assistant assignment? 4. Have you checked if there are any error messages in the Vapi logs that might indicate why the assistant isn't being assigned? 5. Did this issue start happening recently after any configuration changes, or has it always been this way? This information will help me provide more targeted troubleshooting steps for your specific situation! 🕵️‍♂️ Sources: - [Discord Thread about Assistant ID Configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336652401733668864) - [Troubleshooting Chatdash Integration with Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586) - [Vapi Call Logs and Assistant Assignment](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334857584238399549)

Hello @Vapi Support Bot 1. I am using API because I am creating an transient agent. So I did not assign any agent to number...agent is select using the servel url connected to make. 2. Yes the ID is correct agent is working great picks up calls but I cannot see insights in main vapi dasboard too. 3.Yes I am using serverl url connected to make and based on data I am starting agent using api call 4.No error as agent is working but not getting insights https://cdn.discordapp.com/attachments/1353567886358089829/1353569784129785878/image.png?ex=67e22198&is=67e0d018&hm=5c2603f7a17f65877c557e08630f93cd84e8d9e87dcab21fb4ea4b5909376f25& https://cdn.discordapp.com/attachments/1353567886358089829/1353569784356147241/image.png?ex=67e22198&is=67e0d018&hm=fdf1d409d7130adea192aabe1e375cd85bb53f53579ba6f563f20414c92fb097& https://cdn.discordapp.com/attachments/1353567886358089829/1353569784649744424/image.png?ex=67e22198&is=67e0d018&hm=27e5509d4f9b46c764839545f8cea53f4e4ac2796f26800fc9f8eb00697cd9b0&

Hi there! 👋 I see you're having trouble with call insights because your Vapi call logs show "no assistant assigned" despite your agent working correctly. I can't provide specific details about how chatdash processes agent IDs with transient agents, but I can definitely help with the "no assistant assigned" issue in your Vapi call logs! Based on your setup using a server URL with Make.com to dynamically select agents, here's what's happening: When you use a server URL approach instead of directly assigning an assistant to a phone number, the call logs may not properly record the assistant assignment. According to the [troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), the webhook response format needs to include the "assistantId" for proper tracking:

json
{
  "assistantId": "your-assistant-id-here"
}

To fix this issue, you should: 1. Check your webhook response format - Make sure your Make.com scenario is returning the proper format with the assistantId field in the response. This is crucial for Vapi to track which assistant handled the call. 2. Verify assistant configuration - Even when using server URLs, the assistant needs to be properly configured in Vapi for tracking purposes. According to [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), this is essential for dashboard integration. 3. Consider direct assignment as a test - As a troubleshooting step, try directly assigning an assistant to your phone number temporarily to see if insights appear. This can help determine if the issue is with the server URL implementation or something else.

@Vapi Support Bot This is my payload for this it says id should not be there https://cdn.discordapp.com/attachments/1353567886358089829/1353570482137465003/image.png?ex=67e2223f&is=67e0d0bf&hm=468c366e5b1316a9f7b0b2f2238260a0733bc48fcb5e05b9c0b83cf6cfc1a233&

Hi there! 👋 I can see from your payload that there might be an issue with how the assistant ID is being passed to Vapi, which is why your call logs show "no assistant assigned" and you're not getting insights in chatdash. Based on the information I found, your payload structure doesn't match what Vapi expects for proper assistant tracking. According to [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), the webhook response format needs to include the "assistantId" field directly in the root of the JSON response:

json
{
  "assistantId": "your-assistant-id-here"
}

Your current payload has an "assistant" field with a value of "88. JSON string" and an "assistantOverrides" object, but it's missing the explicit "assistantId" field that Vapi needs to properly track which assistant handled the call. To fix this issue: 1. Modify your webhook response format in Make.com to include the "assistantId" field directly in the root of the JSON response. 2. Ensure the assistantId value is a valid UUID of an assistant that exists in your Vapi account. 3. If you're using transient agents, you might still need to create a permanent record of the assistant in Vapi for proper tracking, even if you're dynamically selecting which one to use. Would you be able to modify your Make.com scenario to return the proper format with the assistantId field? This should help Vapi properly track your calls and populate the dashboard insights. Source: - [Troubleshooting chatdash integration with Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586)

@Vapi Support Bot Just to confirm this is the assistant id https://cdn.discordapp.com/attachments/1353567886358089829/1353570873600249897/image.png?ex=67e2229c&is=67e0d11c&hm=030a7ad0f85b3a7aea25484618c3d01f145726e0eaa8eb2b16f430f0df3a199c&

Yes, I can confirm that "9ed2e839-fd4a-43b0-86af-b5a857340310" is the assistant ID you've shared! 👍 Based on our previous troubleshooting, this is the ID you'll need to include in your webhook response format. As mentioned earlier, you should modify your Make.com scenario to return a response with this format:

json
{
  "assistantId": "9ed2e839-fd4a-43b0-86af-b5a857340310"
}

According to the [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), including this assistantId field directly in the root of your JSON response should help Vapi properly track which assistant handled the call, allowing your dashboard and chatdash to display the correct insights. Is there anything else you'd like help with regarding this implementation? Source: - [Troubleshooting chatdash integration with Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586)

once i get id I am using this @Vapi Support Bot https://cdn.discordapp.com/attachments/1353567886358089829/1353571320771641425/image.png?ex=67e22307&is=67e0d187&hm=1d0c47e4c682a87890d2642bb58af1bbec80e0d24a3dab6c1d022d3571d41f1f&

Hi there! 👋 I see you're sharing some code related to your implementation, but I'm unable to determine exactly how this "omit" function relates to the assistant ID configuration issue we've been discussing. Based on our previous troubleshooting, the key issue is that your webhook response needs to include the "assistantId" field directly in the root of the JSON response. According to the [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), the correct format should be:

json
{
  "assistantId": "9ed2e839-fd4a-43b0-86af-b5a857340310"
}

Looking at your previous payload, it appears you're using an "assistant" field with a value of "88. JSON string" and an "assistantOverrides" object, but missing the explicit "assistantId" field that Vapi requires for proper tracking. The code snippet you shared with the "omit" function seems to be removing certain fields from your data object. If this is part of your Make.com scenario, you'll want to ensure that after any omissions, you're still including the crucial "assistantId" field in your final response. Would you be able to modify your webhook implementation to ensure the assistantId is included directly in the root of your JSON response? This should resolve the "no assistant assigned" issue in your call logs and enable insights in chatdash. Is there anything specific about implementing this change in your Make.com scenario that you'd like help with? Source: - [Troubleshooting chatdash integration with Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586)

One question @Vapi Support Bot So if I am using this still I can get insights right?

Hi there! 👋 Based on the information I've found, you should be able to get insights if you modify your webhook response to include the assistantId field directly in the root of your JSON response. According to the [troubleshooting documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586), the webhook response format needs to include the "assistantId" field for proper tracking:

json
{
  "assistantId": "9ed2e839-fd4a-43b0-86af-b5a857340310"
}

Your current setup with the "omit" function might be removing fields from your data object, but what's crucial is that the final response sent to Vapi includes this assistantId field. If you're using the "omit" function but still ensuring the assistantId is included in the final response, then yes, you should be able to get insights. The key is making sure that regardless of what other processing you're doing, the final webhook response that Vapi receives contains the assistantId in the correct format. This is what allows Vapi to properly track which assistant handled the call and populate your dashboard with the appropriate insights. Is there anything else you'd like to know about implementing this change in your Make.com scenario? Source: - [Troubleshooting chatdash integration with Vapi](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344225187939352586)

upon checking error log it says to delete this 5 things

Hey Parth, can you share your organization ID so I could take a look if there were calls being made or not on 24 March?

1413b37a-5903-4246-b306-1e06824d2d7d

@Parth0774 , you have made around 83 calls on 24th March. Wait for some time; it will appear in the analytics dashboard. If it doesn't appear even after waiting for some time, let me know. I'll make sure that we get it fixed for you.

Hello @Shubham Bajaj I am wokring right now it is 115 calls but if u see still it shows 0 on 24 https://cdn.discordapp.com/attachments/1353567886358089829/1353921918922915870/image.png?ex=67e3698c&is=67e2180c&hm=87c935c1b52897431338c18121dccaad8ce4a7c6dfec7bcd3a390ba8cf1fe5a8&