@Fil000 @bajacheebo The only way to "prevent" this is by "flipping" the flow. For example, when using Cloudonix (https://developers.cloudonix.com/cloudonixRestOpenAPI#/operations/initiateCall) you can initiate a call to the remove party, and connect it to VAPI (or other) only after the remote party answers the call. You can activate a "Answering Machine Detection" and connect to the remote platform only after figuring out a real person answered. Of course, this flow a little bit more complex in terms of the flow, however, it will provide you with what you are looking for. Another option is to hook up Cloudonix (https://developers.cloudonix.com/integrations/telephonyIntegration/Provider/VAPI.ai) as an outbound SIP trunk to VAPI (or other). In this way, you can have VAPI initiate the outbound call, but have Cloudonix "wait" for the remote party to really pickup and then connect the two together. This method is also a bit more complex, however, as VAPI won't charge you for calls being made on your own SIP trunk (just AI costs), it means that you a get a solution to your use-case. Another option will be a combination of the two above - namely, initaite a call from Cloudonix to destination, use Cloudonix CXML to perform the perform the basic answering machine analysis and first audio playback - then initiate a call into VAPI (or other) based on the Cloudonix result - again, mildly more complex, but still will answer your requirement.