wavy
11/21/2024, 11:12 AMwavy
11/21/2024, 11:12 AMVapi
11/21/2024, 11:12 AMgather action in your call flow, which waits for the user to press a key on their phone's keypad. Once a key is pressed, the input is sent to your specified endpoint, and you can then handle the input accordingly.
For example, if you have an endpoint set up to handle DTMF inputs, you might have logic like this:
- If the user presses 1, the application performs Action A.
- If the user presses 2, the application performs Action B.
The specific implementation details would depend on the API's documentation and the capabilities of your endpoint. If you need more detailed instructions or assistance with setting up your endpoint to handle DTMF inputs, please let me know, and I can provide further guidance or direct you to the appropriate resources.wavy
11/21/2024, 11:13 AMwavy
11/21/2024, 11:14 AMVapi
11/21/2024, 11:15 AMVapi
11/21/2024, 11:15 AMinput event.
When you receive an input event, it will contain the DTMF digits that the caller pressed. You can then use this information to trigger different actions or responses within your application logic.
Here's a simplified example of how you might handle this in your server code:
json
{
"eventUrl": ["https://yourserver.com/webhooks/dtmf"],
"actions": [
{
"action": "talk",
"text": "Please press 1 or 2 on your keypad."
},
{
"action": "input",
"maxDigits": 1,
"timeOut": 5,
"submitOnHash": false
}
]
}
And then on your server, you would have an endpoint /webhooks/dtmf that might look something like this:
json
{
"dtmf": "1 or 2"
}
Based on the dtmf value, you can then decide what action to take. If you need more specific guidance on setting up your server to handle these events or have any other questions, please let me know!Vapi
11/21/2024, 11:15 AMShubham Bajaj
11/22/2024, 8:50 AMwavy
11/22/2024, 7:56 PMwavy
11/22/2024, 7:57 PMShubham Bajaj
11/25/2024, 2:55 PMwavy
11/25/2024, 2:59 PMwavy
11/25/2024, 3:00 PMShubham Bajaj
11/25/2024, 3:22 PMwavy
11/25/2024, 3:50 PM