A short list of things to find out at a meeting, written before it and checked after it.
A script is what you want to come away from a meeting knowing — «what to ask my doctor», «what to ask my insurer», the questions a support desk asks on every fault call. It is a name and up to ten lines, in your own words and the meeting's language. You write it yourself under Scripts in the menu, or — the usual way — your own assistant writes it for you over Chui's connection.
A script waits for one of three things: a meeting on your calendar, the next call to a number placed through your Chui number, or your next recording for a meeting with no calendar entry. A one-off script is spent when its meeting ends; a saved one can be used again. A script tied to a calendar meeting that has already happened moves in with your other saved scripts, with all its questions kept; one whose meeting was moved to a later time stays with the upcoming ones, and an open list of scripts updates by itself when a meeting starts (since build 274).
A line ticks when someone gives an ordinary, conversational answer to it, unless the line asks for more detail, and a line meant for one particular person ticks only when that person answers it (since build 271).
Assistants can supply optional line_notes in write_script() and prepare_update_script() to say whose words count and what must be said. A line asking for several things needs all of them confirmed.
Picking one inside a meeting (since build 261). You can pick one of your saved scripts from inside a meeting, while it records or after it has finished, and Chui checks the meeting against it without processing the audio again.
On an iPhone in a room, live assistance sends an extra copy of the microphone sound while the meeting records, including with the screen locked. Allow about 115–120 MB of mobile data per meeting hour for this compressed live copy, plus the recording's ordinary upload. Wi-Fi avoids using your mobile allowance. Confirmed answers stay ticked through a pause or a lost connection. Later speech can confirm more answers or correct an earlier one. The complete saved transcript is checked again when the meeting ends. The saved recording continues independently of the live connection.
A script, its ticks and its answers are yours. They are not part of the summary that is emailed, shared by link or posted elsewhere, and colleagues who can open a shared meeting do not see them. In a company, an admin can save a script for every colleague to use — the support desk's intake, say — and only an admin can change or remove it. Scripts live in your account's home, America or Europe, and are deleted with their meeting or with your account.
An assistant connected to Chui writes one with write_script(), naming the meeting from list_upcoming() (which marks meetings that already have one), a number to call, or your next recording. list_scripts() shows what is coming up, what is saved and what is done; get_script() reads one. use_script() puts a saved script on a meeting, a call or your next recording, and stop_using_script() takes it off again; since build 261 it attaches the script to the calendar meeting you name. place_call() takes a script for the call it places. get_script_answers() reads what a recorded meeting found out. Changing a script and removing one are each two steps, so you are asked first: prepare_update_script() then update_script(), and prepare_remove_script() then remove_script().
An assistant can attach a script to a recording or a finished meeting with use_script(recording_id=…). Replacing an existing recording script, including its ticks and answers, asks first: prepare_replace_meeting_script() then replace_meeting_script().