Appearance
Assistant settings, hours, and Flight Control from Claude or Codex
Most of an assistant's Settings and Toolkit switches can be read and changed from Claude Code, Codex, or any MCP client connected to the MyChatBot plugin or to the Sales-Management MCP (sales_assistants domain). The server checks every change the way the dashboard's forms check it, so a value the dashboard would not save is refused with the reason. Every tool and parameter is in the Sales tools reference.
Read first, then dry-run
Each area has a read: assistant_get_settings, assistant_get_working_hours, assistant_get_flight_control, assistant_list_control_numbers, and assistant_list_live_notes. Every write in the sales_assistants domain, and set_channel_options, takes dry_run: true, which checks the change and shows what would happen without saving. The API Action tools have no dry run and save at once. Changes are live at once on an active assistant.
Behaviour and hand-off settings
assistant_update_settings takes only the keys you change:
json
{
"assistant_id": "909",
"settings": { "switch_stop_word": "#human", "auto_return_from_handoff": true, "auto_return_from_handoff_interval_minutes": 120 },
"dry_run": true
}It answers before and after for every key that changes. Some keys move together, as in the dashboard:
- A stop word and implicit hand-off exclude each other: setting a stop word turns implicit hand-off off, and turning implicit hand-off on clears the stop word.
- The auto-return interval (1–10080 minutes) applies only while auto-return is on; turning auto-return off clears it.
- Choosing a web search model turns web search on.
primary_language takes a language name from the dashboard's list (English, Ukrainian, Persian (Farsi), …). Whether a chat a person switched off by hand also returns to the assistant is changed in the dashboard only (Settings → Handoff Control).
Not available over MCP: self-scheduled follow-ups, hiding calculations, sending Google Docs links as attachments, outreach failure alerts, and automatic manager assignment. Change those in the dashboard.
Work Hours
assistant_set_working_hours changes only the days you name, in whole hours:
json
{
"assistant_id": "909",
"timezone": "Europe/Amsterdam",
"days": {
"Saturday": { "start": "10:00", "end": "16:00" },
"Sunday": null,
"Friday": { "start": "09:00", "end": "22:00", "off": [{ "start": "14:00", "end": "15:00" }] }
},
"dry_run": true
}null closes a day; off is a break and on extra hours. An end that is not after its start runs past midnight. With hours set, the assistant switches itself on inside them and off outside them within a minute, while your plan and balance allow. The timezone must be one the dashboard offers; for another zone the answer lists the dashboard's zones at the same UTC offset.
Flight Control
assistant_get_flight_control says whether a Telegram group gets the assistant's Flight Control updates, and returns connect_link. Connecting the group is done by a person: open the link in Telegram, pick or create the group, and the bot confirms there. See Flight Control.
Control numbers
A control number is a phone whose WhatsApp messages to the assistant are instructions from your business, not a customer's: it can add live notes and, with access you give, ask about orders, bookings, or clients. Add only numbers that belong to you or your team. assistant_add_control_number takes the number in international format, an optional label, and optional access ({"orders": "view"}: clients, orders, bookings, setup, or usage, each view today); without access the number manages live notes only. clients lets the phone read your customers, their chats and messages. Pro plan or higher, at most 5 per assistant. assistant_remove_control_number turns its chat back into a customer chat. See Control numbers.
Live notes
A live note is temporary context every reply sees, such as "the kitchen closes at 20:00 today". Pro plan or higher; at most 50 in force. assistant_add_live_note takes the text (up to 500 characters) and when it ends, in the assistant's timezone for notes: its Work Hours timezone, else its WhatsApp number's country, else UTC (see When a note ends).
until | Ends |
|---|---|
| omitted | When it is removed |
+30m, +2h | After that long (1 minute to 7 days) |
end_of_today, end_of_tomorrow | At midnight in the assistant's timezone |
closing | When today's Work Hours end (refused when none is left today) |
2026-12-24 15:00 | At that local time |
The answer shows the end in UTC and in the assistant's timezone. assistant_remove_live_note ends a note now. See Live notes.
Channel options and API Actions
set_channel_options (sales_channels) sets a channel's reply delay (0–180 seconds) and whether reactions are ignored; its dry_run shows the current values, which list_channels does not. api_action_create, api_action_update, and api_action_attach (sales_integrations) manage API Actions: endpoint, fields, response note, and whether the customer's details are sent. Header values, such as an API key, are set only in the dashboard and never travel over MCP; an action that has them keeps its server (scheme, host, and port), and moving it to another one is done in the dashboard.