@danemyers Hello! It's great to hear that you're successfully storing end-of-call reports in your database. Regarding your challenge with passing the

userId

and linking it to the end-of-call reports, using metadata is indeed a common approach. If the metadata isn't coming through in the end-of-call report as expected, there might be a few things to check: 1. Ensure that the metadata is being correctly attached to the agent when it's created. It should be in the correct format and field as expected by the API. 2. Verify that the API or system you're using to handle calls is designed to propagate this metadata through to the end-of-call report. There might be specific fields or settings that need to be enabled for this to happen. 3. Check the documentation of the API or service you're using to see if there are any known issues or additional steps required to include metadata in reports. If you've already done all of this and it's still not working, it might be a limitation or a bug in the system. In that case, reaching out to the support team of the service you're using would be the best next step. Alternatively, if the system allows for custom logic or webhooks, you could implement a function that triggers at the end of each call, retrieves the call details along with the metadata, and then manually links it to the user in your database. If you're using VAPI, please ensure that you're following the correct procedure for passing metadata and retrieving it in the end-of-call report. If you need further assistance with the specifics of VAPI, please ask support for more info on this. I hope this helps, and if you have any more questions or need further assistance, feel free to ask!

You can continue this conversation by mentioning me in the message.

Got it. Tagging @User for additional help.