On this page
AI jobs in MSPortal, area by area
| Area | What AI does | Who reviews it |
|---|---|---|
| Ticket intake | Picks the request template from a client's description, fills in fields using company and user defaults, and asks about missing required details | The client checks the form and clicks Create Ticket |
| Ticket summaries | Summarizes a ticket's history as an email, bullet list or paragraph | Technicians; clients never see these summaries |
| Client-facing notes | Drafts clearer client updates from technician notes | Staff check for accuracy and sensitive details before sharing |
| Reports and QBRs | Writes the executive summary, KPIs, risks, recommendations and a 7, 30 and 90 day action plan, with sources cited and data gaps listed | Your team reviews the report before clients see it |
| Report design | Lays out report blocks from a description, and designs reusable charts and tables | Staff check the preview, then save and publish |
| Compliance | Drafts up to 40 checks from a description after you approve a plan, rewrites or translates checks into 15 languages, and drafts client notes with business impact and remediation steps | You choose which checks to save and apply each proposal. A drafted client note saves straight into the check's public notes, so edit it right away |
| Planner | Answers questions such as which items are overdue, and drafts new items from a description | The draft becomes an item only when you apply it |
| Projects | Explains progress and blockers, drafts weekly updates, and proposes milestones, decisions and status changes | Nothing saves until someone selects Apply |
| Meetings | Drafts agendas using Planner, compliance and ticket data, cleans up notes and extracts action items | Staff edit before sending recaps |
| Templates and surveys | Drafts ticket templates, onboarding templates, automation rules and surveys | A diff preview to accept or reject changes |
| Survey responses | Groups responses into themes and sentiment highlights | Staff decide what to act on |
The AI page shows each of these, and the feature pages for tickets, reporting, compliance and projects go into detail.
The MSPortal AI assistant
The assistant sits on the Home page and in a drawer on other pages, and the same assistant is available in the Chrome extension. It answers questions in plain language, finds records, prepares support tickets and proposes changes. A proposed change shows as a Review change card, and only clicking Apply change saves it; typing "yes" in the chat does not. On pages with their own editor, such as the survey designer, it prepares a draft that you save from the page.
For clients, the assistant mainly helps with ticket requests. They describe the problem and the assistant prepares the request for them to review. It can also answer questions from the documents each user is allowed to see. The AI assistant guide and the AI ticket guide show both sides.
To use an outside AI client such as Claude or Cursor with portal data, MSPortal has a separate MCP server. See whether MSPortal has an API or MCP server.
Where human review applies
Review is built into each workflow rather than left to habit:
- Tickets are never submitted by AI. Routing comes from the template's board, type and priority, not from an AI guess.
- Reports are drafts. A generation review flags missing sections or citations it could not verify, and AI edits show current and proposed text side by side. Scheduled and background report generation runs as automation, so review the output before using it for decisions.
- Compliance AI shows each change as a proposal card with before-and-after values, as described in the Compliance AI guide. A drafted check does not show that a requirement is met, and MSPortal does not certify compliance.
- Related guides suggested during ticket entry are shown to clients only after a person marks each AI-written summary reviewed.
What AI in MSPortal does not do
- It does not see more than the signed-in user. AI is scoped to the tenant, and its tools are filtered by the user's role and company access.
- It does not run unless an administrator turns it on, under Settings > Tenant > AI.
- It does not replace your vCIO or technician. It drafts; they decide. For QBRs specifically, see what parts of QBR preparation an MSP can automate.
Keep passwords and API keys out of chat. Credential handling has its own workflows.
Is AI included in the MSPortal price?
Yes. The pricing page lists unlimited AI usage in every plan, alongside the AI assistant, AI-drafted QBRs and the MCP server. Some features, such as Related guides and the AI block builder, are turned on per organization.
Related questions
Does MSPortal's AI submit tickets for clients?
No. The AI assistant chooses a request template and fills in the form from the client's description, but the client reviews it and clicks Create Ticket. Nothing reaches the MSP's ticketing system before that.
Can clients see AI ticket summaries?
No. In MSPortal, AI summaries of a ticket's history are for the MSP's technicians, and clients never see them.
Does AI write QBRs in MSPortal?
AI drafts QBRs and other full reports from the client's data, with sources cited and data gaps listed. The MSP's team reviews and edits the report before publishing it to the client.
Can MSPortal's AI see data from other clients?
No. The assistant only works with data the signed-in user can access, filtered by tenant, role and company. Client users stay limited to their own company's data.
How does AI help clients submit better tickets?
It matches the client's description to the right request form and fills in the details technicians need. See how MSPs get clients to submit better tickets.