Skip to main content
MSPortal.ai and Neo Agent work together automatically through your PSA. There is nothing to connect, no API keys to exchange, and no setup wizard to run.

​
Overview

Neo Agent is an AI teammate platform for MSPs. It connects to your PSA, picks up tickets from your service boards, triages them, and runs its workflows against them. MSPortal.ai is PSA-first by design: every ticket created in MSPortal is written directly into your PSA with full routing and context. Because Neo Agent reads its work from that same PSA, the two products already share a pipeline. Your PSA is the single source of truth, and both tools operate on it. We have met with the Neo Agent team to verify this compatibility. Tickets created by MSPortal carry the structure and context Neo Agent’s workflows expect, so nothing extra is required on either side.
You will not find a Neo Agent card under Settings > Integrations. That is intentional: there is nothing to connect, configure, or maintain. If both MSPortal and Neo Agent are connected to your PSA, they already work together.

​
How Tickets Flow

1

A Ticket Is Created in MSPortal

Tickets can come from anywhere in MSPortal: manual creation, ticket templates, the AI assistant, or forms.
2

MSPortal Writes the Ticket to Your PSA

The ticket lands in your PSA with complete routing: board or queue, type, status, and priority, plus the mapped company and contact.
3

Neo Agent Picks It Up

Neo Agent sees the ticket on the board it watches, exactly like a ticket entered directly in the PSA, and runs the matching workflow.
4

Updates Sync Back to MSPortal

Notes, status changes, and resolutions that Neo Agent writes to the PSA sync back into MSPortal automatically, so both tools stay current.

​
What Neo Agent Sees on Every Ticket

MSPortal tickets are formatted so that Neo Agent can ingest them without custom parsing or middleware. Every ticket MSPortal creates in your PSA includes: This gives Neo Agent all the information it needs to classify each ticket and handle its workflows end to end.

​
Prerequisites

  • An active PSA integration in MSPortal.ai
  • Neo Agent connected to the same PSA (see Neo Agent’s documentation for its supported platforms)
  • Company import and mapping completed in MSPortal, so tickets are created against the correct accounts

ConnectWise PSA

Connect ConnectWise PSA to MSPortal.ai

Autotask

Connect Autotask to MSPortal.ai

Halo PSA

Connect Halo PSA to MSPortal.ai

Import Companies

Map PSA companies into MSPortal.ai

​
Best Practices

  • Route tickets to the boards Neo Agent watches. Review the board, type, status, and priority defaults in your MSPortal PSA settings and ticket templates so new tickets land where Neo Agent expects them.
  • Use ticket templates and the AI assistant. Both produce consistent, well-structured summaries and descriptions, which keeps Neo Agent’s triage accurate.
  • Keep company mapping complete. Tickets for unmapped companies cannot be routed to the right PSA account, which affects any tool working from the PSA.

​
Frequently Asked Questions

No. MSPortal and Neo Agent communicate through your PSA, so there are no credentials to exchange between the two products.
Yes. Notes, status changes, and resolutions that Neo Agent writes to the PSA sync into MSPortal through your existing PSA integration, alongside updates from your human technicians.
Confirm the ticket is landing on a board Neo Agent monitors. Check the board, type, and status defaults in your MSPortal PSA settings, and verify the ticket appears in the PSA with the expected routing.

Ticketing

Learn how tickets are created and managed in MSPortal.ai

Other Integrations

Explore MSPortal.ai’s direct integrations

​
Need Help?

For questions about how MSPortal.ai tickets flow into your PSA, contact support@msportal.ai. For Neo Agent configuration, contact Neo Agent support.