Client portal
Give each client a portal that looks like yours, on your domain, where their staff can see their estate, raise requests and get real help from Ask Helio.
Quotes
Price a piece of work on the Quotes page, send it, and the client accepts or declines it signed in to the portal or from the link in the email, with their name on the decision. Monthly lines go onto their contract when you convert the quote; one-off lines appear on that month's invoice. A quote that passes its date expires on its own, and a decided quote can be duplicated but never edited.
Branding and domains
Set your company name and logo once and the portal login and interior carry your brand, not ours. Portals run on a custom domain (for example support.yourmsp.co.uk): point a DNS record and Helios provisions the TLS certificate automatically on first request. Login is email-first and simple enough for non-technical staff.
What clients see
Portal users are viewers scoped to their own company: their devices with health state, their tickets with the public conversation, and a request form. Internal notes, other clients and MSP operations are never visible. Device drill-down shows enough for an office manager to answer "is this machine okay", without exposing your tooling.
You choose the rest in Settings, What clients see. Each item has one switch: the computer list, computer details such as the network address, performance charts, alerts, updates, backups, security threats, security news, your month's work, the service catalogue, quotes, reports and audits, and Microsoft 365. The emails are there too: request received, status changes, the satisfaction rating, and Helio's answers.
Set it once for every client, then change it for one client if they need something different. Anything switched off is hidden in the portal and refused by the server, so a typed link shows nothing either. A switched-off email is not sent, and report sections follow the same switches. Requests and the replies your team writes are always on.
With Alerts off, requests raised by monitoring go too: those opened by an alert, the agent or a failed update. Requests the client raised, and ones your team raised for them, stay. The public status page follows the same switches.
Security news
When a security alert is in the news, clients ask whether they are affected. The portal home can answer that before they email. Turn it on in Security advisories, under Show clients in their portal, or in What clients see, where you can also choose it per client. It is off until you do.
Each client sees recent advisories in plain words: checked and not affected, being checked, being updated, or updated. They never see machine names, versions or other clients. A member of staff limited to their own computer sees the answer for that computer only.
Public status page
Each client can also have a status page: a private link that shows their machines, open alerts, open requests and what was fixed this week, with no sign-in. Turn it on in the client's Setup tab. It shows only what What clients see allows for that client: with computers off it shows requests only. Anyone with the link can see it, so send it only to the people who should. "Make a new link" stops the old one at once. Turning the page on or off and making a new link are all recorded in the audit log.
The page only says what Helios has measured. A machine whose update check failed, or that has not reported updates, shows as not checked, never as fine. Backups are shown only for clients that have backup in place. "Fixed this week" counts each machine and alert once, however often it came back, and never shows Helio's working notes.
Ask Helio for end users
The portal includes the client-facing Helio chat: an end user describes a problem in plain English, Helio checks that company's devices and recent tickets, suggests safe self-serve steps, and if the problem needs a human it opens a ticket that arrives already investigated: findings, steps tried, the affected device and the requester attached. Your techs start from evidence, not "it's broken".
Service catalogue and approvals
Alongside free-text requests, the portal offers a service catalogue: a menu you define of the things clients actually order, such as new starters, leavers, password resets, software installs and hardware. Each item carries your own questions, can be limited to job roles or departments, and can require sign-off from a named approver, who gets an email and approves or declines straight from the ticket, with no console login needed. Helios ships a starter catalogue you can edit freely; it is managed from Service desk → Catalogue in the console.
Approved means done. Items can be set to fulfil themselves the moment they are approved: a leaver is blocked from Microsoft 365 and signed out everywhere, a password is reset (with the temporary password kept in internal notes for the desk to relay securely), an application install queues on the right device group, or a vetted playbook runs. Every action is recorded on the ticket. Offboarding and resets for someone else's account only ever run behind a real sign-off, and anything the platform cannot finish is left honestly open for a technician with a note saying why.
QBRs
Helios drafts a quarterly business review per client from real data: health trends, ticket volumes, patch posture, risks and recommendations. It is fully editable before you present it, and prints cleanly to PDF. The point is to make the QBR you keep postponing into a half-hour job.
Scheduled reports
Recurring email reports keep client stakeholders informed between reviews, using an email-safe design that renders correctly in Outlook and Gmail, in light mode, because inboxes are light even when brands are dark.
