Hi, Issue Summary I have create automation that dials certain numbers which have a menu system. The assistant is required to "press" or "select" option 2 in the IVR menu to go through to the sales team. However, the assistant ends the call almost immediately the initial call speaks and tries to redirect the assistant. It seems it is not able to trigger the dtmf. Affected Call IDs: - daf7217b-314f-4ff7-b3c9-13d841c3cf55 (After issuing the digit, it did not carry on the conversation) - 32c7a6f1-05bd-4566-86bf-b384b354b322 - 56394288-28fd-4e57-b5e9-0b173b1ae948 These call IDs refer to a similar assistant but this time they are not transient. A couple of the transient calls that had this issues are: - 0288d672-f5de-43e8-aa35-52704c0fa901 - 45a39737-6819-4a18-809a-1efe91ad5c14 I'd like to know what needs to be in place to make it more reliable. The solution for my client will be transient agents. So please focus on that solution more.

For transient assistants with DTMF issues, try removing the

assistant

property from your payload and only use

assistantId

. According to information I found, "The transient has precedence over assistantID so, when you tried to make the call transient took precedence over assistantID" [Discord](https://discord.com/channels/1211482211119796234/1336765707760963676). Example payload:

json
{
  "assistantId": "your-assistant-id",
  // Remove the "assistant" property
  "phoneNumber": "+1234567890"
}

Source: - [Discord](https://discord.com/channels/1211482211119796234/1336765707760963676)

Thanks for the quick response. So are you suggesting I create the assistant first, then use it's ID for the call? Or have a static assistant whilst parsing parameters? The issue is that quite a bit changes during the build up of the prompt and others. But please, confirm. This Call ID -- daf7217b-314f-4ff7-b3c9-13d841c3cf55 -- was for a static assistant. It sent the DTMF digit but could not resume the call after the call was routed to participant at the receiving end.

For calls not resuming after DTMF input, the issue may be related to call status changes. After gathering DTMF digits, Twilio changes the call status to "in-progress" while VAPI expects "ringing" status. Try using a conference call approach to transfer the call after DTMF input:

javascript
// After gathering DTMF input
const twiml = new VoiceResponse();
const dial = twiml.dial();
dial.conference('ConferenceRoom123', {
  startConferenceOnEnter: true
});
// Then connect Vapi to this conference

According to Discord discussions, this approach helps maintain the connection after DTMF processing. Source: - [Discord](https://discord.com/channels/1211482211119796234/1342459464346767492)

Cc: @Shubham Bajaj