STAGING - not the production estate

How replies work

The model never writes what a visitor reads. It picks one of your replies by its code. The words that go out are the ones you typed here.

One reply

Stages

A stage keeps a conversation on one track. Offered in limits a reply to one stage; leave it on "any stage" and it competes on every turn. Then moves to is what advances the conversation. Leave stages out entirely and every reply is always on offer, which is fine for a small set.

You pick both from a menu of the stages your replies already use, so a stage cannot be created by mistyping one. To make a new one, choose + add a new stage. The Setup tab lists every stage and every fact you have, with a warning on any stage nothing moves to - its replies can never fire.

Facts

Needs first is a tick-list of your facts - what the bot must have before it may send the reply. If something is missing it sends the reply whose Asks for matches, waits for the answer, then sends the one it was holding. A fact that nothing asks for is a conversation that stops - the Serving now tab lists every reply that can stop, and says whether you meant it to.

When a person is needed

Some facts cannot come from a visitor - whether a withdrawal actually went through, what a photo says. Tick only a colleague may supply this on the fact, and the bot will never ask a visitor for it and never invent it. It stops instead, and shows the question on its own panel in the chat console.

You answer in the console, where the real transcript and any file the visitor sent already are. Either reply by hand, or hand the fact back to the bot: leave an internal note whose first line is [handback] and put one fact: what you found line under it. The bot picks it up on the visitor's next message and sends your wording.

A reply that stops for a person needs somewhere to go afterwards. If four different questions all move to one stage, and only one of them has a reply that reports a result, the other three sit on "please wait" and nobody is told which fact is actually wanted. Give each one its own stage.

Saving

Nothing you change reaches the bot until you press Save, and the save bar only appears once something has changed. A bot picks up a saved change the next time its console tab connects.

Import and export

Export downloads the setup and every reply as one file - exactly what is on screen, unsaved edits included. Import loads a file back over both, and saves nothing: check it and press Save yourself, or Discard to put the bot back as it was.

The file never contains the API key, so it is safe to keep and to send. Importing one into another bot leaves that bot's own key alone, and leaves auto-send and auto-accept as whoever is at the seat has set them.

Back to bot settings