Skip to content
EN
Open app

On Key Pressed

2 min read
Copy as Markdown
View as MarkdownOpen the raw .md file.md

On Key Pressed fires when the caller finishes a keypad run (Runs when: When caller presses a key) - usually after the end key on Call handling - Advanced or when the wait expires. Digits are available to later nodes as the key-pressed / DTMF input variable.

The agent’s Phone keypad input settings decide when a run is complete. The trigger panel itself is light:

Enable Message Creation
When enabled, the AI speaks a message to the caller before executing this workflow.
On Key Pressed trigger on the canvas
wf-dtmfExpand
On Key Pressed Enable Message Creation
keyword-pressed-formExpand

Order ids, account numbers, menu digits. Speech is sloppy for long numbers - Skip Turn plus this trigger is the usual pair.

  1. On the agent, Call handling - Advanced - Phone keypad input - wait long enough for the id, end key # unless your IVR already uses another key.
  2. + Add Trigger - On Key Pressed.
  3. Connect To External Service - pass the DTMF input into the URL or body.
  4. AI Response to Caller on success (and a failure path if useful).
  5. Save & go live, attach. Prompt the agent to ask them to type the id then #. Call, type, listen.
The API gets three digits of a ten-digit id

Raise the keypad wait on Advanced, and tell callers to press #. Confirm Skip Turn is on.

Why not During Call?

During Call makes the model hear the number. Key Pressed reads the pad. Use During only if they will say the id, not type it.