I am building a AI Receptionist where the flow depends on user keypad input - so I need to use keypadInputPlan

Hi there! 👋 Based on the documentation I've found, there isn't a direct reference to a tool specifically named

keypadInputPlan

, but I can help you implement DTMF (keypad input) functionality for your AI Receptionist. Currently, Vapi has some limitations with DTMF handling - it can send DTMF tones but cannot directly receive them. Here's how you can work around this: 1. Set up a custom webhook to handle incoming calls instead of directly associating your Twilio number with Vapi:

python
@app.post("/twilio/inbound_call", response_class=PlainTextResponse)
async def receive_call_data(
AccountSid: str = Form(...),
ToZip: Optional[str] = Form(None)):
    # Process call data and forward to Vapi when necessary

2. Use Twilio Flex as an intermediary to capture DTMF inputs before sending calls to Vapi. This helps capture key inputs like caller phone numbers and project numbers. 3. Integrate with Make.com for workflow automation to process the DTMF inputs once captured. 4. Define clear transfer logic within your AI model based on the keypad inputs received. For number formatting in voice responses, you can configure settings like:

json
{
"voice": {
  "chunkPlan": {
    "formatPlan": {
      "numberToDigitsCutoff": 100000
    }
  }
}
}

I hope this helps get you started! Let me know if you need more specific guidance on any of these steps. Sources: - [Webhook Setup](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343397177182912553) - [DTMF Functionality](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341108728115757138) - [Transfer Logic Setup](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341892594044633099)

Hey, unfortunately, it is not supported, but I’d love to know about your use case in detail.