Assistant settings

Each application’s Setup → Assistant section holds six company defaults for how record sessions work a table. A tenant admin can lock any one of them, so every table under that application follows the same rule unless the admin leaves it open to override.

Every setting on this page is live

As of the wake-rules release, every setting below changes what actually happens on a record: Wake on create (including “when conditions match”), Wake on the requester’s answer, Wake on other comments before pickup, and After a person is assigned are all read by the comment wake gate, the create-admission door, or the new assignment handler. Nothing here is sent to a model provider or any outside service; these are configuration values stored on the table’s note.

The six settings

Setting	Choices	Default	Locks?
Mode	Assist, Autonomous	Assist	Yes
Wake on create	Never, Always, When conditions match	Never	Yes
Wake on the requester’s answer	On, Off	On	Yes
Wake on other comments before pickup (Autonomous only)	On, Off	No default declared	Yes
After a person is assigned	Hold, Keep working	Hold	Yes
Changes without approval	Opens the auto-approval policy page	—	n/a (existing setting, not owned here)

Mode. Assist is the conservative choice: every message to a requester, including a question the assistant wants answered, is left as an editable draft instead of being posted. A person reviews it, edits it if needed, and sends it themselves; the assistant never wakes on a public comment by itself before a person picks the record up. Autonomous lets the assistant ask the requester directly and wake on a public comment before pickup, under the “Wake on other comments before pickup” setting below. Once a person is assigned, Autonomous drafts too: after pickup, a message to the requester is always a draft, in either mode. In either mode, an internal note never wakes the assistant unless it names @agent directly, and @agent always works.

A question addressed to the desk (most of what the assistant asks) is never a draft: it posts as an internal note the moment the assistant asks it, in either mode, and says “Answer here and mention @agent so the assistant can continue.” A question addressed to the requester says “Reply here with the answer” once it posts (directly in Autonomous before pickup, or once a person sends the draft).

Wake on create. A record landing on a session-enabled table is not, by itself, worth a run (present but silent is the platform’s default). Set this to Always to start a run on every new record, or to When conditions match to start one only when the record matches a condition you choose (one condition today: a field, an operator and a value, from the same operator set a business rule trigger uses). Choosing a value here does not disturb the other: the platform never reads “Always” where you set “When conditions match”, and the other way round.

Wake on the requester’s answer. When a requester replies to a question the assistant addressed to them, this decides whether that reply wakes the pursuit. It has no effect on a desk-audience question (most of what the assistant asks): that reply is governed by Mode and “Wake on other comments before pickup” instead, the same as any other comment. A requester reply never wakes a pursuit that a person currently holds, however this setting is set. A held pursuit only ever resumes when it is handed back (a manual Take over), or never, when the hold is “a person is assigned” (see below): the reply is recorded and goes to that person’s own notifications, not replayed to the assistant later.

Wake on other comments before pickup (Autonomous only). Any other public comment, before a person has taken the pursuit over, wakes it when this is on. H-D5 states no default for this setting; the page shows it unset rather than guessing one, and it has no effect under Assist.

After a person is assigned. Hold (the default) pauses every open pursuit on the record the moment it gets an assignee, the same way a manual Take over does, and resumes it the moment the person is removed. A pursuit a person holds manually is never released by an assignment change, and the other way round. Assigning a group, with nobody named, holds nothing: only a named person’s assignment counts. Keep working leaves every pursuit untouched when the record is assigned.

Changes without approval is the existing auto-approval policy, not a new setting: the row only opens that page.

Where it is edited

1. Open Admin → Setup, choose the application, and open its table’s AI stage.
2. Each control saves on change, the same door the table’s Wake on every new record switch already saves through (PUT /tables/{table}/session). A locked control shows Locked by the company default: <value> and cannot be changed from the table’s own page.
3. The Studio Session tab’s Wake on every new record checkbox reads the SAME wake_on_create key. When the table is set to When conditions match, that checkbox shows the condition’s row as a third, read-only state rather than a plain on/off, so toggling it there can never erase the condition; change the mode from the Setup Assistant section instead.

Verification

Reopen the Assistant section and check the saved choice. A locked setting shows the company’s value immediately, with no table override possible; unlock it from the tenant’s house rules to let a table choose its own.

Troubleshooting

Symptom	Cause	Fix
A setting will not save, naming an operator	The condition’s operator is not one the dispatcher implements	Choose one of the listed operators; an unlisted one is refused rather than silently never matching
A control is disabled with no explanation	The tenant note locks it	Check the caption under the control for the company’s value, or ask the tenant admin to unlock it
The Studio checkbox shows no change after a save on the Setup page	”When conditions match” was chosen, which the Studio checkbox shows read-only	Change the mode on the Setup Assistant section
A comment on a record wakes nothing, even in Autonomous	A person is already assigned to the record (the pursuit is held), or the comment is an internal note with no @agent	Mention @agent directly, or check who the record is assigned to
A requester’s reply wakes nothing	”Wake on the requester’s answer” is off, the question was addressed to the desk rather than the requester, or a person already holds the pursuit	Check the setting, the question’s audience, and the record’s assignee