On this page
The core features every client portal needs
These are the features clients notice within their first week. Without them, they go back to email.
- Ticket submission with guided forms. Clients should pick the kind of request and answer a few relevant questions, not write an open-ended email that a technician has to follow up on. Forms that change based on earlier answers keep them short.
- Ticket status and history. Clients need to see whether anyone has picked up their request, who is working on it and what was said, and reply in the same place.
- Documentation clients can find. How-to guides, the Wi-Fi details for the guest network, the process for onboarding a new hire. Each item needs its own sharing control, because not everything in the MSP's documentation is meant for clients.
- Per-user permissions. An employee, an office manager and a finance director need different views. Permissions should cover which modules a person sees and which records inside them, such as their own tickets, their location's or the whole company's.
- Your brand. Logo, colours and ideally your own web address, so clients trust that the portal belongs to their IT provider.
Features that make clients come back
Once the basics work, these turn the portal into the place clients check first.
| Feature | What the client gets |
|---|---|
| Reports and business reviews | A current view of their service and security, without waiting for the next meeting |
| Compliance status | Their score, open gaps and evidence, on demand instead of by email |
| Devices and warranties | A list of their equipment, with ages and warranty dates, for budgeting questions |
| Backup and security summaries | Plain confirmation that backups and protection are running |
| Invoices and agreements | Billing records next to the work they pay for, ideally with a way to pay |
| Approvals | Managers approve requests and changes without a separate email chain |
| Security awareness training | Staff take assigned courses where they already go for IT help |
| Project and onboarding progress | A shared plan showing what is done and what needs the client |
Not every client needs all of these. A ten-person office may only care about tickets and documentation; a multi-site firm with an audit coming up will care about compliance and reports. Pick the portal that covers the clients you have and the ones you are trying to win.
Controls the MSP needs behind the scenes
Clients never see these, but they decide whether the portal is safe to roll out.
- Two-way sync with your ticketing system. Tickets created in the portal should land in your PSA with the right board, type and priority, and replies should flow both ways. Check which actions write back and how often data is updated.
- Internal versus client-visible content. Internal notes, worked hours and draft reports must stay hidden unless you choose to share them.
- Integrations with the tools you already use. Device, backup, documentation and security data should come from your existing tools rather than being re-entered.
- Support for complex clients. Clients with several offices or subsidiaries need one login that can switch between locations, with per-location permissions. See How can clients with multiple locations use one portal login?
- Sign-in that clients already have. Microsoft or Google sign-in, or a one-time email link, means one less password to forget.
Where AI is useful in a client portal
AI is worth having where it does a specific, checkable job. Useful examples are choosing the right request form from a client's description and filling it in for them to review, answering questions from documents the user is allowed to see, and drafting reports that a person reviews before the client receives them. Be cautious of portals that describe AI only in general terms; ask what it does, where the data comes from and who reviews the output.
How MSPortal covers these features
MSPortal is a client portal for MSPs, and the features above map to its modules as follows:
- Tickets: clients describe a problem in their own words, AI fills in the matching request form, and they review it before submitting. Tickets sync with ConnectWise Manage, HaloPSA, Autotask and Syncro, and clients see status, the assigned technician and public notes. Internal notes and worked hours stay hidden unless you choose to show hours.
- Documentation: share Hudu or IT Glue documents and passwords, plus pages and files written in MSPortal, by folder, document or password for each company and role.
- Dashboards and reports: share dashboards with specific client roles and publish reviewed reports to the portal or send them on a schedule.
- Compliance: clients see their score, grade, failed and overdue checks, public notes and shared files. Private notes are never shown to client users.
- Access: company roles control what each client user can see and do, and individual records such as Planner items or compliance checks can be hidden from company users. Clients sign in with Microsoft, Google or an email link.
Data from connected tools is automatically updated on a schedule. ConnectWise ticket updates arrive by webhook as they happen, and Autotask and HaloPSA can use webhooks once you set them up; otherwise a scheduled sync brings PSA changes in within 5 to 15 minutes, depending on the PSA. The MSPortal guide to controlling what company users can see explains the visibility rules in detail.
To compare options, see What is the best client portal software for MSPs? or book a demo.
Related questions
What is an MSP client portal?
An MSP client portal is a branded website where a managed service provider's clients sign in to open and follow tickets, find documentation, and see their reports, compliance status, devices and invoices. See What is an MSP client portal?
Do small clients need a full-featured portal?
Not always. Small clients often need only ticket status and a few how-to guides. A portal with role-based access lets an MSP switch modules on per client role, so small clients see a simple portal while larger clients get reports and compliance.
Should a client portal show technicians' internal notes?
No. Internal notes often contain troubleshooting detail, credentials or frank assessments that are not meant for clients. A good portal keeps internal notes hidden by default and shows only the public replies.
How do clients see compliance status in a portal?
The portal shows a compliance score, open gaps and any evidence the MSP shares, so clients can check progress on demand. See How can MSPs show clients their compliance status?