I have had a few times where the call stops or gets dropped. What is the approach to continue a call from that point? Lets add an example in case it helps: 1. got user name 2. got user favorite color ### call drops ### I would like to call back and continue from this point. Hello, {{username}} who's favorite color is {{favorite_color}}. What is your favorite food? Thanks

@chris.happy.dad I'm sorry to hear that you've experienced dropped calls. To ensure a smooth continuation of the call after a drop, you can implement a system that saves the conversation state at each step. This way, when you call back, you can retrieve the last saved state and continue from there. Here's how you can handle it: 1. After each piece of information is gathered (like the user's name and favorite color), save the state to your server or database. 2. If the call drops, use the saved state to resume the conversation. 3. When you call back, use the saved information to personalize the greeting and continue the conversation. For example, if you have already gathered the user's name and favorite color, and the call drops, upon re-establishing the call, your system would fetch the saved data and you could start with: "Hello, [username] who's favorite color is [favorite_color]. What is your favorite food?" This approach requires your system to be set up to handle state management and to trigger callbacks with the saved context. If you need assistance setting up this feature or have any other questions, please let me know!

Add all the previous message which you received

@Sahil When you say add all previous messages, this is what I need to understand. How do you build this upon initiation? I think it is imperative that the entire message stack exist for the analyze feature to work. I know the client can send (I have not tried it, only seen in the api), seems like you want to build out the messages before you initialize.

As far as I could tell he was just updating the variables not the messages. If you figure out a way to push messages into the stack please let me know. I will test it when creating the assistant and also maybe event:message:call:monitor:controlUrl might work if I catch it on call in progress (as it starts up).