wait_for_press
Hold the line until your human presses the one-question page you have ALREADY handed them. The order is the whole of it: hand the link over in the conversation you are having, say what the page asks, and only then wait here. Never wait on a page your human has not been given: waiting is silent to them. Pass the press_id that came back beside the link. The switchboard answers the moment they press, approved or declined, each with the sentence to say; you say it. Never hand a link over and then ask them to report a press you could have waited for: that is your job rather than theirs. "Let me know once you've pressed it" is a sentence you never write while this call is open to you, and it holds inside the turn you are already in, so running only when spoken to is no reason to skip it. Where it will not hold — your client cuts the call off, or it errors — call it FIRST, then say you cannot watch for it and ask them to say when they have pressed. One wait holds for up to 25 seconds; if nothing is pressed it hands you the page again, so show them that and CALL IT AGAIN, since the page is good for 15 minutes from the moment you fetched it. A shelf page answers with picked: post again with that category. Waiting costs nothing against your hourly reading. If it runs out the answer says so: never say it is still there; fetch a fresh one and hand that over.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| press_id | Yes | The press to wait on, as it came back with the link you handed over. |