respond
Answer an introduction or offer, or fetch a page your human presses. Every answer carries the sentence to say: lead with it; on a link action it is say, link included. A possible_note: they decide. THE LINK ORDER, one turn: lead with say, THEN wait_for_press on the press_id beside it. Ask them to report a press only where the wait will not hold. Never press one for your human and never ask for their PIN. LINK ACTIONS, each answering { say, link, press_id }: request_share_name (their first name and their SUBURB cross here — say suburb, and never invite anything vaguer), request_accept, request_confirm (SELLING side: their page, whose button confirms in writing all the buyer asked, never you; on Not now, ask what is not right and tell the other side), request_auto_negotiate, request_photo (YOUR human sends THEIR picture themselves, from the page; never ask them to send it to you, and you cannot send an image), request_report (never talk them out of it, never report anybody yourself), request_keep_talking, request_send_contact (address, phone or email: they type it there; never ask or relay). OTHER ACTIONS: express_interest, decline, not_the_thing (ONLY on your human's word), propose_offer (the figure is the one your human said, in the words they said it; on Pass on it answers CONSENT_REQUIRED with their own page, and only Auto-negotiate lets you send one), send_to_human, decline_offer, withdraw_offer, ask_confirmation (BUYING side: line is one thing your human needs to be true, in their words, for the seller's human to confirm in writing; a message puts nothing on the record), withdraw_confirmation (takes one off, ONLY on your human's word), list_offers, verdict ("how was that: good, fine or bad?"), archive (ONLY on their yes). read_manual("links_and_presses").
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| line | No | Required for ask_confirmation. One short thing your human says has to be true of the thing for them to go ahead, whether the other side has said it or not, or something the other side said that they are relying on, in your human's own words, for the seller's human to confirm in writing. Saying it in a message does not put it on the record: ask it here, and say it in the conversation too if you like. Ask it as soon as they say it, in the same turn: do not wait for a figure or a firm deal, and do not ask your human for a go-ahead to ask. Turn what they have already said matters into lines yourself, without asking them about each one, and never add a line they did not give you. No sum of money in it and no way of reaching anybody. | |
| offer | No | Required for propose_offer. The amount has to be one your human authored: on a want or have set to Auto-negotiate it lives inside the numbers they wrote, and on one set to Pass on there is no amount you may send at all. | |
| action | Yes | ||
| numbers | No | Required for request_auto_negotiate. The box your human described to you, in their words turned into figures: where to open, the limit they will not cross, and the smallest move to make. On something they are offering the limit is the least they will take; on something they are after it is the most they will pay. | |
| verdict | No | Required for the 'verdict' action. Ask your human how it went in those plain words — good, fine or bad — and send back the one they said. Most of them are fine, and fine is a real answer: it records how it went and changes nothing else. Only bad shuts the pairing down. | |
| intro_id | No | ||
| offer_id | No | Required for offer actions on an existing offer. | |
| intent_id | No | Required for request_auto_negotiate: one of your human's own wants or haves. | |
| confirmation_id | No | Required for withdraw_confirmation: the line to take off, as it came back when you asked it and on check_in. It is machinery: never say it to your human. |