Using Additional Instructions
Teach Risotto your organization's terms, systems, and places with one set of instructions that the support agent and automations follow
Additional instructions are text that Risotto adds to its AI prompts as instructions from your organization. Use them to teach Risotto what applies across your whole organization: what you call your systems, teams, and places, and what changed after a migration.
Where the instructions are set
The instructions are the Additional instructions field on the Settings > Advanced page. Org Admins and Managers can open the page and change the field. See Permissions.
There is one field for the whole organization. You cannot set different instructions for a department.
You can also change the text with the update_org_setting tool of the Risotto MCP server, with the key org_additional_instructions.
How Risotto uses them
- Support agent: when the agent works on a ticket, its prompt includes your instructions under Company Instructions, as instructions from your organization. This applies to every ticket, wherever the request came from.
- Automations: each automation run gets the same instructions.
The agent reads the field each time it starts work on a message, so a change applies from the next message.
The Assistant in the dashboard does not use additional instructions. To steer the Assistant on escalated tickets, use your department's instructions for each phase.
Change the instructions
Open the Advanced page
Go to Settings > Advanced.
Edit the text
Type your instructions in Additional instructions. The field has no length limit, but shorter instructions work better. See What to write.
Save
Click Save in the top-right corner of the card. The message "Settings saved" appears. To discard your changes instead, click Cancel.
To remove the instructions, clear the field and click Save. For more about the page, see Advanced.
What to write
Write facts and instructions that hold for everyone in your organization:
- Terminology: "Northwind calls its laptops 'field kits'."
- Systems and tools: "'The portal' means our employee self-service site, Northwind Hub."
- Teams and places: "HQ is the Denver office. The warehouse is in Reno."
- Migrations: "We moved from GlobalProtect to NordLayer in October. Help people set up NordLayer."
- Behavior for every request: if a runbook instruction should apply to every request, such as a greeting or a tone, write it here once and remove it from each runbook.
Tips:
- Say what to do. AI models follow "Help people set up NordLayer" better than "Don't mention GlobalProtect".
- Be specific. "Our service desk team is called the Experience Team" works better than "We use different names for teams".
- Keep it short. Long, repeated, or conflicting instructions can make replies worse in ways that are hard to trace. When you add an instruction, read the whole text again and remove what is no longer needed.
- Put department procedures in runbooks. A step-by-step process for one kind of request belongs in a runbook, which Risotto uses only for matching requests.
Don't add:
- Information about individual employees
- Passwords, keys, or other secrets: the text goes into AI prompts
- Information that changes often
Example
Northwind calls its laptops "field kits". "The portal" means our employee
self-service site, Northwind Hub. HQ is the Denver office, and the warehouse
is in Reno. The Security team is also called InfoSec.
We moved from GlobalProtect to NordLayer in October. When someone mentions
"the VPN" or GlobalProtect, help them set up NordLayer. Our old help desk
email is no longer monitored: ask people to make requests in #it-help.
Keep the instructions current
Read the instructions again after a reorganization, a migration, or a new company-wide tool, and update the names and systems that changed.
Something wrong or missing? Report an issue · View as Markdown