ah gotcha, makes sense. once VAPI hands the call off, it basically loses visibility, so yeah the way to solve that is by embedding a StatusCallback + StatusCallbackEvent in the initial transfer request payload that goes to Twilio. that way Twilio will hit your endpoint when the call ends (or on any other events you care about). the key is making sure VAPI passes those fields through when it creates the transfer — are you currently using the TwiML with action/statusCallback, or building the call via the REST API? knowing that will help me point you to the right JSON structure.