Your client gets one of everything too.
The client’s side of The One Stack is one portal and one app under the MSP’s own brand, on the platform MSPs run their whole business on. Your clients ask for help, see their devices, take their training and pay their invoice in one place. They see your name on all of it. Never ours.
Before and after
What a client deals with when an MSP runs a stack of tools, and what they deal with on One.
| What your client notices | With a stack of tools | On One |
|---|---|---|
| One portal, under your name | A ticket page from one vendor, a payment page from another, a training site from a third. | Tickets, devices, training and invoices in one portal on your domain, with your logo and colors. |
| One place to ask | A phone tree, a support inbox and a web form that do not know about each other. | They call, email or ask THEO in the portal. Whichever they choose, it lands on the same record. |
| Fixed without the wait | A stuck print queue or a full disk becomes a ticket, and the ticket waits its turn. | When the fix is in THEO’s runbooks, THEO checks who is asking and fixes it. Anything else reaches a technician with the details already on it. |
| One conversation | Updates arrive as emails from a ticketing system, and replies go back into it. | A reply on a ticket lands in the thread your technicians are reading, and their answer comes back in it. |
| One invoice | A bill for the contract, another for the hours, another for the software. | One invoice from you, with the contract, the hours and what they bought on it, paid in the same portal by card or autopay. |
| One sign-in for what you sell | A separate account for every service you resell to them. | The apps and services you provide open from the same portal, with the same sign-in. |
The portal
One portal on your domain. What each person sees follows the role you give them.
They move their own ticket
On a ticket, a client asks for a phone call, asks for an update, flags it as urgent or confirms it is fixed. Each request lands on the ticket for your team, and a resolved ticket can be reopened from the same page.
Starters and leavers
A client’s admin tells you from the portal that someone is starting or leaving. A new starter arrives as a ticket. A departure becomes a request with its own steps, each owned by your team or by the client, and both sides see which are done.
Approvals
Change and purchase requests wait in one place. They approve or decline with a note, and the decision is recorded.
Security
They see status and summaries. Findings and remediation come to you as tickets, not to them as raw alerts.
Contracts
Signed statements of work, amendments and change orders are listed, with a download when a copy is on file. Quotes and agreements you send are signed there too.
One place to ask
They call, email or ask THEO in the portal. Whichever they choose, it lands on the same record.
Phone
The caller is matched to a person and a client before anyone picks up. THEO or your team answers.
THEO in the portal
They ask a how-to question, open a ticket or check on one. THEO answers from their own company’s record and no one else’s.
Fixed without the wait
A routine request does not have to wait its turn in the queue.
- 01
They ask
A person reports a routine problem, such as a stuck print queue or a full disk, on the phone or in the portal.
- 02
THEO checks who is asking
THEO confirms the person and their company before it does anything.
- 03
THEO runs the runbook
When the fix is in a runbook you have switched on for that client, THEO runs it and tells the person it is done.
- 04
Or a technician gets it
Anything else reaches a technician as a ticket, with the person, the device and the details already on it.
One invoice
Your client gets one invoice from you. The contract, the hours and what they bought are on it, and they pay it in the portal by card or autopay.
That covers your own services and the apps on the client’s contract. Phone service is the exception: it is invoiced in your brand, with The One Stack as the carrier of record.
Invoices and payments post to QuickBooks Online, so your books match what the client saw.
Client apps
The apps you provide open from the same portal, with the same sign-in. A client sees only what they have.
Apps you sell
Workspace, Files, CRM, Projects, E-Sign and Fleet open from the portal, each under your name and at your price. Phone service is sold the same way and runs on softphones.
Services you provide
Security training, dark web monitoring and compliance, switched on by you for each client.
Your brand everywhere
They see your name on all of it. Never ours.
Your domain
The portal runs on your own domain, so the address your clients type is yours.
Notifications reach your clients as email in your brand.
Mobile app
Your clients get a mobile app with your logo and colors, for tickets, approvals, devices, training and invoices.
Access rules
Access is per person, and there is a plain answer when someone cannot see something.
Roles
Each person has a role, such as basic access, tickets only, billing only, office manager, IT contact, authorized signer or full access.
Per-person rules
You add or take away one thing for one named person. When two rules disagree, the refusal wins.
Your limits, their admin
The client’s admin manages their own people inside the limits you set.
Why can’t this person see it
For any person and any app, your team sees what they can open and which step decided it.
See what they see
Your staff open the portal as a named client person to check it. That view is recorded.
See inside.
What it looks like, screen by screen.
An approval, on their phone
A change or a purchase that needs a yes goes to the person who can give it. They read what is asked and what it costs, approve or decline with a note, and the answer lands on the ticket.
Questions
Questions MSPs ask
Do my clients see The One Stack name?
No. The portal, the mobile app and the email carry your logo, your colors and your domain. The one exception is phone service, which is invoiced in your brand with The One Stack as the carrier of record.
What can a client do in the portal?
A client opens and follows tickets, approves requests, sees their devices, takes security training, signs agreements and pays invoices. What each person sees follows the role you give them.
Can THEO fix a client’s problem without a ticket wait?
Yes, when the fix is in a runbook you have switched on for that client. THEO checks who is asking, runs the runbook and tells the person it is done. Anything else reaches a technician with the details on it.
Does my client get one invoice?
Yes, for your own services: the contract, the hours and what they bought are on one invoice from you, paid in the portal. Phone service is invoiced in your brand, with The One Stack as the carrier of record.
Why can’t one of my client’s people see something in the portal?
Access follows the person’s role and any per-person rule, and a refusal wins. Your team sees, for any person and any app, which step decided it.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.