Open an incident properly
With their description, the affected equipment and a photo. You stop having to interpret "the hallway AC isn't working" at eight in the morning.
Client app
Let your client check instead of calling
Half the calls a maintenance company gets aren't requests: they're just asking how things are going. With their own access, the client sees it themselves and the call never happens.
The cost of being the only one who knows
When the information only exists inside your system, you are your client's search engine.
- Calls asking about the status of a breakdown that's already fixed.
- Reports that come in over WhatsApp, with no photos and no idea which equipment they mean.
- The client asks again for the report from three months ago, and someone has to dig it up.
- No one remembers when the next inspection is due, so they ask.
- A pending quote falls asleep in an email inbox.
What your client can do on their own
Their own access, scoped to their sites, their assets and their work orders.
Follow their work orders
What state each job is in, who's handling it, and what's been done. The information that today gets asked over the phone.
See what's coming
Upcoming preventive visits on a calendar or timeline. They know when it's their turn without asking, and can arrange site access.
Download their reports
The PDF of every job, whenever they need it, without asking you. And they can upload any documents they want to attach.
Sign off the work
If you give them that permission, the client signs the report from their own access. Useful when the site manager wasn't there the day of the visit.
Check their assets
What equipment they have, at which site, with what history and documentation. Often the first time a client sees it laid out clearly.
A complete application, not an incident form
For when your client expects a real platform: what they see and can do is a lot more than it looks.
A dashboard with what matters
Indicators, status and trend of their incidents, activity by site, what needs their attention and their upcoming visits, on a single screen.
Incidents with their conversation
Each incident carries its history of communications, so what was said is not lost in an email or a WhatsApp.
Quotes they approve themselves
They receive the proposal, read it and approve or reject it from their own access, with a record of who did it and when.
Assets with their record
Each piece of equipment with its history and documentation. And, if you grant the permission, creating, editing or moving assets.
Organised documentation
A document tree by site and by asset, which they can browse and add their own files to.
Expenses (depends on module)
If you enable the expenses module, the client checks them by period.
Warehouse (depends on module)
With the warehouse module active, they check the stock and materials of their sites.
Satisfaction surveys
They answer, with their rating, the surveys you send them, and you collect their opinion without asking for it elsewhere.
On mobile and on a computer
The same information in two interfaces. On mobile, an installable app designed for one-handed use: report with a photo, check how a job is going, approve a quote. On a computer, views designed for a large screen —lists, tables, board and calendar of work orders, a dashboard with indicators and detail sheets— for the manager who works with many sites. It is the one best appreciated by whoever has to follow many sites at once, and the information is the same their team sees on mobile.
The data no one else shows them
Of everything the client access offers, the most surprising is that they can see their future preventive visits, with dates, sites and assets, on a calendar or timeline. A client who knows the chiller inspection is due next month doesn't call to ask, arranges site access, and, above all, understands what they're paying for. It's the difference between a contract perceived as a recurring bill and one perceived as a service.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
Everyone sees only their own
That scoping is what makes this safe to open up.
Scoped by client
Their sites, their assets, their work orders. One client never reaches another's, not even by direct link.
Permissions per person
Within the same client, a store manager and the head office contact don't have to see the same thing.
And a separate portal for suppliers
Subcontractors log in through their own access, scoped to the jobs assigned to them.
In their own language
The client app is available in eleven languages, which matters when a chain has sites abroad.
Where the line is, and why
Your client can check, contribute and request, but does not run the job: they cannot change a work order's state. That's a product decision, not an unresolved limitation. The lifecycle of a job — what's assigned, what's in progress, what's closed — is owned by whoever is providing the service, because they're the one accountable for it. Opening it up to the client would turn the state into a negotiation and strip the history of its evidentiary value. What they can do, if you grant the permission, is sign the report: giving their sign-off, which is a different thing.
How to roll out access without it sitting empty
Signing up every client the same day and sending an email with credentials is the surest way to get no one to log in. What works is the opposite: start with two or three clients who call a lot — they're the ones who'll appreciate it most — and open their access in a meeting, showing them the two screens they'll actually use. From there, the best sales pitch for the rest is that their peers in the same industry already have it. And a practical tip: instead of announcing the portal, start answering their questions with a link to the specific work order. Within two weeks they're logging in on their own.
Frequently asked questions
A large client demands its own platform before signing with us: what do I show them?
A complete access limited to their own scope: dashboard with indicators, incidents with their conversation, work orders and reports in PDF, quotes they approve or reject, calendar and upcoming preventive visits, assets with their history and documentation, and satisfaction surveys. On mobile and on a computer, in eleven languages and with per-person permissions. Whether they use it more or less afterwards depends on each client: what counts when they demand it is being able to show that it exists and that it is up to the task. In the demo we set up the access of one of your clients so you can show it to them.
Is there a desktop version?
Yes, with lists, tables, a board and a calendar of work orders and a dashboard with indicators, designed for whoever manages many sites. The information is the same as on mobile: only the way of seeing it changes, adapted to a large screen.
How many users can I give each client?
There's no per-license limit, so the decision is yours and worth thinking through: giving access only to the account manager is easy to manage, but giving it to every site manager too is what actually cuts down the calls, because the person who sees the problem is the one who opens the ticket.
Can the client see the cost before the work is done?
Yes, if you work with quotes: the client receives the proposal in their access and approves or rejects it from there, with a record of who did it and when. It's one of the things that speeds work up most, because a pending quote stops falling asleep in an inbox no one connects to the breakdown.
Can my client see other clients' data?
No. Each access is scoped to that client's own sites, assets and work orders, and that limit is enforced on the server, not just in what's shown on screen.
Can they change a work order's state?
No, and it's deliberate. The lifecycle of the job is owned by whoever provides the service. The client can sign the report if you grant that permission, which is giving their sign-off, not managing the state.
Does it work offline, like the technician app?
No. The client app installs on the device, but it's built for checking and requesting with a connection. Working without coverage is the technician's scenario, and it's the technician app that's built for that.
Do clients need training to use it?
In practice, no. The two things a client does — open an incident and check how it's going — are designed for someone who logs in three times a month and doesn't remember anything from the last time.
What about subcontractors?
They have their own portal, separate from the client one, with access limited to the jobs assigned to them and to handing back what they did inside the system.
Show it to one of your clients
In the demo we'll set up access for one of your clients with their sites, to see what they'd see and what they'd stop asking you.