The three-tier prompt system
Base prompt (managed by Rallied)
Base prompt (managed by Rallied)
The base prompt defines the agent’s core IT helpdesk behavior: how to reason about requests, when to ask for clarification, how to use tools, approval flow logic, and safety rules. Rallied manages this prompt and updates it as the product changes.You cannot edit the base prompt.
MSP prompt (your organization's standards)
MSP prompt (your organization's standards)
The MSP prompt is where you document your organization’s IT policies and tool preferences. Every agent you run, across all your clients, receives this prompt in addition to the base prompt.Use it for things like:
- “Use Microsoft 365 for user lookups, password resets, and group changes. For clients with a separate identity provider, prefer that provider for app-access decisions.”
- “Escalate any request to create or modify admin-level accounts.”
- “When a user reports a software issue, check if they’ve restarted within the last 24 hours first.”
- “Our SLA for access requests is 4 business hours.”
Client custom instructions (per-client context)
Client custom instructions (per-client context)
A client’s custom instructions add context specific to one company. The agent receives them in addition to the base and MSP prompts.Use them for things like:
- “This company uses Zendesk for customer support, Slack for communication, and Microsoft 365 for email and files.”
- “Users are in the
clinic-staffMicrosoft 365 group. Contractors are inclinic-contractors.” - “The IT contact for escalations is helpdesk@clinic.example.com.”
- “This client is a medical clinic: treat any patient data references with extra caution and do not store them in notes.”
Editing the MSP prompt
Go to Settings → Prompt. Write your instructions in the editor and click Save.
Editing a client’s custom instructions
Open a client’s detail page and click the Custom instructions tab. The editor shows only this client’s instructions. Rallied applies the base and MSP tiers automatically, so they don’t appear here. Write your client-specific instructions and click Save. The change takes effect on the agent’s next request. For a client that’s in a workspace but isn’t its primary, the agent uses the primary’s custom instructions. The agent ignores the client’s own instructions for its tickets, so edit the primary’s instead.
Tips for writing effective prompts
Be specific about tool preferences. Don’t just say “use Microsoft 365”. Say “use Microsoft 365 to look up users and manage group memberships. Use themsgraph-get-user tool to find a user before attempting any access changes.”
Write down your escalation rules. The agent follows written rules more reliably than implied ones. If admin account creation should always go to a human, write: “Never create admin accounts autonomously. Always escalate to the on-call technician.”
Include company-specific context the agent can’t discover on its own. For example, org chart conventions, Microsoft 365 group naming patterns, your PSA board routing rules (which boards or queues take which request types), or the names of key applications employees commonly request access to.
Keep MSP and client instructions focused. Add what the base prompt can’t know: your policies, your tools and your clients’ environments.