### Answer The Press Digit node evaluates whether to press a digit each time the user (in this case, the IVR/screening system) finishes speaking, and this evaluation timing is affected by the detection delay setting [(1) ]() . Transitions on this node occur specifically when "the IVR system finishes speaking" , which for the Press Digit node means the check for a transition is tied to the other party's speech, not to the digit-press event itself. There is no mention in the documentation of a "skip response" style setting for the Press Digit node . Skip Response is documented as a property of the general node transition system, where a node transitions once the agent finishes speaking, without waiting for the user [(2) ]() — but the Press Digit node does not speak at all, since "the agent will not speak" while in this node [(1) ]() . This means the Skip Response edge behavior, which fires after the agent finishes speaking, would not apply here since there's no agent speech to key off of. Regarding evaluation order, transitions are checked as: always edge first, then equation conditions, then prompt conditions (evaluated together by the LLM) , then the else edge, and finally the node stays if nothing matches [(2) ]() . An always edge "transitions unconditionally as soon as the user responds, skipping condition evaluation entirely" — but this is also tied to the user responding, not to the digit-press action completing. Based on the documentation provided, the Press Digit node's transition check is explicitly designed around evaluating "each time the user (IVR system) finishes speaking" [(1) ](http

s://docs.retellai.com/build/conversation-flow/press-digit-node) , and I don't have documentation confirming a way to trigger transition evaluation immediately upon a successful digit press, independent of the other party speaking again. I found a community forum thread describing a similar scenario involving DTMF and the Press Digit node not behaving as expected on forwarded calls, though it centers on the digit press not registering at all (a DTMF delivery issue) rather than the transition timing after a successful press [(3) ]() . In that case, the resolution involved simplifying the transition condition instructions and confirming DTMF signaling method with the telephony provider , but that thread doesn't address a case where the digit is confirmed pressed successfully yet the node fails to transition. Given this, I don't have documented information confirming a mechanism to force immediate transition evaluation right after a digit press for this node type. If you'd like, I can point you toward relevant support channels. Check out these potentially useful sources: [Press Digit Node]() , [Transition conditions]() , [Documentation]()

​ To learn more, see the sources I considered: [[1] Press Digit Node](https://docs.retellai.com/build/conversation-flow/press-digit-node) [[2] Transition conditions](https://docs.retellai.com/build/conversation-flow/transition-condition) [[3] Conversation Flow: forwarded calls not accepting DTMF “1” (Press Digit node)](https://discord.com/channels/1186424376300679209/1449889950781804726) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.