You would want to change buttons to Yes=Print Bill,No and remove print bill automation command name.
Then make new rule with event automation command executed, set the constraint to command value equals print bill.
The buttons bit where Yes=Print Bill makes it so pressing yes sends automation command value of Print Bill which is what makes that new rule fire. No button has no value so nothing happens.
You would also obviously need to put the ask question in to a rule.
Simplest example would be a new rule on event payment processed.
Personally I would use a generic ask question action using [: ____ ] to carry the fields into the action settings.
ie;
Question: [:Question]
Buttons: [:Buttons]
Command Name [:Command Name]
Background: [:Background]
Doing this means you have one ask question action you can use many times, then when you add the action to a rule the options/fields from the action are available in the action entry in the rule itself meaning you dont need to have lots of the same actions each having slightly different settings as the options are defined on each individual use of that action.
Like this;
