Pretty much the title. When I run the bot as an inbound agent, structured data runs. I'm not too sure why it doesn't work at all. Like tokens are not even spent.

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

@Vapi, I think it's something to do with by outbound being transient that's why it's not working.

@UtotNiSam I see, if your outbound setup is transient, it might not maintain the state or context needed for structured data to function correctly. Structured data often relies on persistent states to track and manage the flow of information. If the transient nature of your outbound calls is causing the structured data not to trigger, you may need to look into ways to maintain state across calls or ensure that the necessary context is passed each time the bot is activated. To resolve this, you might consider: 1. Ensuring that each outbound call has the necessary context to trigger structured data. 2. Checking if there's a way to maintain state or session information in your outbound setup. 3. Reviewing the structured data configuration to ensure it's set up to handle transient scenarios. If you need further assistance with the specifics of your setup, please provide more details or reach out to the support team for more in-depth troubleshooting.

@Vapi how can I receive proper end of call reports from a transient bot?

@UtotNiSam To receive proper end-of-call reports from a transient bot, you would typically need to ensure that the bot is configured to log interactions and outcomes at the end of each call. Since you mentioned that the data is blank, it could be due to a few reasons: 1. **Logging Configuration**: Ensure that your bot is set up to log the necessary information at the end of each call. This might involve setting up specific logging parameters or ensuring that the bot's code captures the required data before the call ends. 2. **State Management**: For transient bots, it's crucial to manage the state effectively so that the data isn't lost at the end of the call. You may need to implement a way to store call data temporarily and then log it before the call ends. 3. **End-of-Call Triggers**: Make sure that the triggers or events that are supposed to capture the end-of-call data are correctly implemented. If these triggers are not firing as expected, the data will not be captured. 4. **Structured Data Configuration**: If you're relying on structured data for reports, double-check the configuration to ensure it's set up to handle transient scenarios and that it's capturing the data correctly. 5. **API Integration**: If your bot sends data to an external server or API for logging, verify that the integration is working correctly and that the server is receiving and processing the data. 6. **Error Handling**: Implement robust error handling to capture any issues that might be causing the data to be blank. This can help you identify and fix the underlying problem. If you've checked these areas and the issue persists, you may need to provide more specific details about your bot's configuration and the context in which it's operating. If necessary, reach out to the support team for more detailed assistance.

The API works it's receiving the end call report, but for some reason structured data is blank. I double checked my trancient assistant generation and the structured data prompt is there. To add further context, I used the get assistant api request and used that as the basis of my trancient bot.

Hey @UtotNiSam To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!