Custom Agents
Custom Agents (also called Custom GPTs) are AI assistants you build and configure for your MSP. Each agent has its own instructions, knowledge base, personality, and scope — so a "Client Onboarding Assistant" agent behaves completely differently from a "Security Incident Helper" agent.
Agents can be used privately by your team, shared with your whole organization, published to the marketplace, or embedded in Studio-built client portals.
What Makes an Agent
Every agent is defined by:
| Field | Description |
|---|---|
| Name and description | How the agent is identified in the library and by Jarvis |
| Instructions | The system prompt — up to 50,000 characters. Defines the agent's purpose, behavior, tone, and constraints. |
| Model | Which AI model the agent uses (inherits from feature routing unless overridden on Enterprise) |
| Temperature | 0–2. Lower = more deterministic. Higher = more creative. |
| Knowledge base | Uploaded files, pasted text, or crawled URLs the agent can reference |
| Capabilities | Web browsing, code interpreter, image generation, file analysis — toggle each on/off |
| Conversation starters | Pre-written prompts shown to users when they open the agent for the first time |
| Product scopes | Which The One products this agent can access data from (psa, crm, defend, etc.) |
| Enabled tools | Which action tools the agent can invoke (create ticket, send email, etc.) |
| Confirmation required | Whether write actions require explicit user confirmation before executing |
| Visibility | Private (only you), Team (your organization), or Organization-wide |
Creating an Agent
- Navigate to Custom GPTs in the left navigation
- Click New agent (top right)
- Choose a starting point:
- From scratch — blank instructions
- From template — choose a system template (see below)
- Clone existing — copy an agent you already own
- Fill in the Name and Short description fields
- Write your Instructions — be specific. Include the agent's role, what it should and should not do, how to handle edge cases, and what tone to use.
- Click Save
Adding a Knowledge Base
Agents can answer questions about your specific documentation, client notes, runbooks, and more. Add knowledge to an agent:
Upload files:
- Open the agent and click Knowledge → Add files
- Upload PDF, DOCX, TXT, or CSV files (up to 50 MB per file)
- The platform extracts and indexes the text automatically
Add URLs to crawl:
- Click Knowledge → Add URLs
- Enter one or more URLs (public websites or documentation portals)
- The platform crawls the content and adds it to the agent's knowledge base
- Click Refresh to recrawl and update changed content
Paste text directly:
- Click Knowledge → Add text
- Paste raw text (runbooks, SOPs, product notes)
- Give the source a name so you can identify it later
Search the knowledge base: The agent uses semantic search to find relevant knowledge chunks before each response. You can test the search from the Knowledge → Search tab.
System Templates
The platform includes built-in system templates to get you started:
| Template | Purpose |
|---|---|
| Customer Support Agent | Handles ticket intake, status updates, and FAQ responses for clients |
| Sales Assistant | Answers pricing questions, qualifies leads, drafts proposals |
| Technical Troubleshooter | Walks users through common IT issues step by step |
| Security Advisor | Explains security alerts, recommends remediation steps |
| QBR Prep Assistant | Pulls data from PSA and Defend to prepare Quarterly Business Review materials |
| Onboarding Concierge | Guides new clients through your onboarding checklist |
To create an agent from a template:
- Click New agent → From template
- Select the template
- Review and edit the pre-populated instructions
- Customize for your MSP (replace placeholder client names, policies, etc.)
- Click Save
Configuring Capabilities
Toggle these capabilities from the agent's Settings tab:
Web browsing — Lets the agent fetch and read live web pages when answering questions. Useful for agents that need current information (e.g., security advisories).
Code interpreter — Lets the agent write and execute code to answer analytical questions or generate reports. Charges apply for compute.
Image generation — Lets the agent generate images from text descriptions. Requires image generation quota.
File analysis — Lets users upload files for the agent to analyze (spreadsheets, logs, PDFs). Files are processed in your tenant and not retained after the session.
Product Scopes
By default, agents can only respond to text input — they cannot read from your PSA, CRM, or other products. Add scopes to give agents data access:
- Open the agent, go to Settings → Product scopes
- Toggle on the products you want the agent to access:
psa— Read tickets, companies, contacts, service timecrm— Read companies, contacts, opportunities, activitiesdefend— Read detections, device status, risk scoresrmm— Read device inventory, patch status, monitoring alertscmdb— Read asset records and relationshipsbooks— Read invoices and subscription billing
- Click Save
psa scope can only read tickets the current user is allowed to see. Agents do not elevate permissions.Require Confirmation for Write Actions
When an agent has tools that can create tickets, send emails, or modify records, enable Require confirmation to prevent accidental writes:
- When enabled, the agent shows the proposed action and asks "Should I proceed?" before executing
- When disabled, the agent executes write actions immediately (useful for automated workflows)
Default: enabled for agents with enabled tools.
Publishing to the Marketplace
Share your agent with other MSPs:
- Open the agent, click Publish to marketplace
- Fill in the marketplace listing:
- Category — Customer Support, Security, Sales, etc.
- Tags — Keywords that help others find it
- Price — Free or paid (USD amount per install)
- Click Publish
Published agents are reviewed by the platform team before going live. The review process takes 1–3 business days.
Agent Analytics
Track how your agents are being used:
- Open the agent
- Click the Analytics tab
You will see:
- Total conversations and unique users
- Average rating (if published)
- Tokens consumed per day
- Cost per day
For published agents, you also see installation count and rating breakdown.
Tips for Writing Effective Instructions
Be role-specific. Start with a clear role statement:
"You are an MSP support agent for Acme IT. You help clients troubleshoot issues with their Microsoft 365 and networking environment."
Define what the agent should not do:
"Do not provide pricing information. Direct pricing questions to [email protected]."
Specify format:
"Always format troubleshooting steps as a numbered list. Keep responses under 300 words unless the user asks for more detail."
Handle edge cases:
"If you do not know the answer, say so clearly and offer to escalate to a human technician."
Use conversation starters to show users what the agent can do — first impressions matter.
Visibility and Sharing
| Visibility | Who can see and use it |
|---|---|
| Private | Only you |
| Team | All members of your organization on the AI Platform |
| Organization | All users across your org and any sub-tenants |
Changing visibility from Team to Organization requires Admin role.
Related Pages
- Jarvis — The system-level AI assistant that can invoke Custom GPTs
- Usage Analytics — Track agent usage and costs
- Studio App Builder — Embed agents in client-facing portals