In-note Command
Last updated: May 14, 2026
Use in-note commands to run AI-assisted workflows from an internal note in your agent platform.
In-note commands work with gateways that have Co-Pilot enabled.
Create an in-note command
Go to Management → In-Note Command to create and manage commands.
Each command has an ID that you can call later from an internal note.
Command types
Choose the command type that fits the workflow.
Analyze
Analyze the conversation, extract key information, and write a summary note.
If configured, it can also update platform attributes.
Use this for structured reporting, case wrap-up, and attribute updates.
When creating an Analyze command, write a clear command instruction for what Aissist should extract.
Examples:
identify the user's contact reason
summarize the user's destination, travel duration, and device make or model
You can also enable schema output and agent platform update.
When platform update is enabled:
make sure each attribute name matches the platform attribute exactly
if an attribute must be one value from a list, include all allowed options in the command instruction
After Aissist analyzes the conversation, it writes a note and updates the platform attributes.
Evaluate
Evaluate the conversation against a linked evaluation setup.
Use this for QA workflows and review scoring.
Rephrase, Translate Then Send
Rephrase the input, translate it into the user's language, and send it to the user.
Use this for agent-assisted follow-up messages.
Summarize
Summarize the conversation and output a note.
Use this for quick handoff notes and internal summaries.
Translate
Translate the input into the user's language.
If sending is enabled, Aissist also sends the translated message to the user.
Link assets and actions
In-note commands can also link to assets and actions.
Use assets when the command needs reference knowledge.
Use actions when the command needs live system data or a workflow step.
Write the command instruction
Each in-note command needs a command instruction.
This instruction tells Aissist what to analyze, summarize, translate, evaluate, or send.
Keep the instruction specific and structured.
For example, tell Aissist exactly which fields to extract, which summary you want, or which allowed values it must choose from.
If the command updates platform attributes, define those attributes clearly in the instruction.
If one attribute must match a predefined list, include the full list in the instruction so Aissist selects a valid value.
Enable Co-Pilot in the gateway
In-note commands work only after Co-Pilot is enabled on the gateway.
In the gateway settings, enable Enable Co-Pilot with this Gateway.
Once enabled, the gateway can process in-note commands for conversations assigned to its team.
Run a command from an internal note
To call a command, send an internal note in this format:
Replace command_id with the command ID you created in Management → In-Note Command.
How command routing works
When Aissist receives the note, it first checks the conversation assignee team.
It uses that team to locate the gateway with Co-Pilot enabled.
Once the gateway is found, Aissist looks for the command by its ID.
Last updated