Your Brand.
Their Experience.
HaloPSA’s customer portal gives your clients a white-labelled space to raise tickets, browse your service catalogue, view projects, accept quotes, and pay invoices — all under your brand, embedded in their workflow.
What’s included
One portal. Every client interaction.
White-Label Branding
Custom URL, logo, colours, font, and CSS — per client if needed. The portal looks and feels like theirs. Multiple portals for multiple brands or organisations.
Service Catalogue
Your MSP shop window. Per-client menus, dynamic product dropdowns, and e-commerce-style requests — no coding, drag-and-drop config.
Client Dashboards
Live project progress, open tickets, agreements, quotes, and invoices — all in one view. A QBR killer: share live data instead of static reports.
Teams & Slack Embed
Your branded portal lives inside your clients’ Teams or Slack. They stay in their tool; you get structured, portal-quality submissions every time.
Service Deflection
Stop the phone.
Start the portal.
Reporting through a portal reduces load on your service desk because you control the triage steps. Clients provide the right information first time. The portal surfaces knowledge articles as they type — resolving common issues before a ticket is ever raised.
Knowledge deflection — clients type a keyword, guides surface inline. Many issues never become tickets.
Asset-linked submissions — clients pick the affected device from their contract-supported assets. Your technician knows the exact device before picking up the ticket.
Azure SSO / Entra ID — clients log in once and Halo knows who they are, what they’re entitled to, and which assets they use.
Structured forms per request type — no more “I’ve got a problem, help me” emails. Every submission arrives with the context you need to start working.
What happens when a client raises a ticket
Service Catalogue
Your MSP shop window.
The service catalogue is the most powerful part of the portal. Customise it per client, per client type — turn common requests into structured, pre-approved workflows that stop clients going to Amazon or raising vague emails.
Per-client menus
Different catalogue items for different customers. A marketing client sees Mac + Photoshop bundles; a finance client sees Lenovo + Excel. Each client only sees what they’re entitled to request.
Dynamic dropdowns
Use dynamic SQL lookup to pull live product data per customer. When a client requests a laptop, the dropdown shows their approved models at their contracted price — not a generic list.
No coding, drag-and-drop
Every form is built in Halo’s ticket-type editor. Add text fields, dropdowns, date pickers, and dynamic visibility rules — no developer needed. Clone and adjust per client in minutes.
Microsoft Teams & Slack
Meet clients where they are.
Your portal can live inside Microsoft Teams as a sidebar app. Clients authenticate once — Halo knows who they are, what they’re entitled to, and how to route their request. They never leave Teams. Your brand is the first thing they see.
Also available in Slack. The portal can be co-branded, white-labelled, or fully client-branded. Per-customer or global configuration.
Client Capabilities
Everything in one place.
Give clients everything they need — from reporting a fault to signing a quote — without a single email or phone call to your team.
Works with
Connected across HaloPSA.
Also in HaloPSA
Every module included. One licence.
Frequently asked
Questions about the HaloPSA customer portal
Is the customer portal included in HaloPSA? +
Can we brand the portal differently for each client? +
Can the portal be embedded in Microsoft Teams? +
How does the service catalogue work in HaloPSA? +
Give your clients a portal they’ll actually use.
Allied ESM sets up and configures the HaloPSA customer portal as part of every implementation — including branding, service catalogue, Teams integration, and client onboarding.