> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the MSPortal integration brings to your Neo Agent setup

MSPortal (MSPortal.ai) is your client success and vCIO portal: Client Health scores, CSAT and NPS, the Traffic Light review, business reviews, budgets, goals, Planner and standards for each client. Connect MSPortal to Neo and your agents find the clients at risk of churn, explain why a client's health fell, and bring health, CSAT and NPS into a business review.

> [!NOTE]
>
> MSPortal uses one API key per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent.

## What Neo can do with MSPortal

> [card] Client Health
>
> Read each client's health score, risk level, score history and the dimensions that cost the most points.

> [card] Satisfaction
>
> Read CSAT per client, NPS per period, and each NPS answer with its comment.

> [card] Traffic Light
>
> Read the weekly Traffic Light review, and log a review or set a status when you allow it.

> [card] vCIO records
>
> Read and update meetings, budgets, goals, Planner items, reports, standards and compliance.

## Find the clients at risk every month

The **At-Risk Client Scan with MSPortal** template is a monthly agent that reads every client in MSPortal and flags those with a churn signal: an At Risk or Critical health score, a score that fell 10 points or more, low CSAT or an NPS detractor, no meeting or contact for months, a Red or Amber Traffic Light, or overdue invoices. It writes a ranked report with the evidence and one next step for each flagged client, and changes nothing in MSPortal. A client MSPortal cannot score yet (Limited data) is listed apart, never flagged for that alone.

Pick it from the template gallery, then set the thresholds, the day and the time to fit your book.

## Your clients are mapped automatically

Neo matches each MSPortal company to a company in your PSA and keeps the mapping on the MSPortal card's **Organization Mapping** tab. It refreshes the mapping when you save the key, and again on each nightly PSA sync.

Matching tries the company's domain or website first, then its name exactly, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest.

**A domain or name match, or one you confirm, is handed straight to your agents**, so they start from the client's MSPortal id without looking it up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent reads and writes only the MSPortal company mapped to the ticket's company.

## Next steps

> [card] [Connect MSPortal](https://docs.neoagent.io/integrations/msportal/connecting-to-neo.md)
>
> Create an API key in MSPortal, save it in Neo with your region, and turn it on per agent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.