Features
Customer requests land straight in the system.
Requests that arrive by phone, email, WhatsApp groups and hallway chats get lost, arrive without photos or an address, and nobody knows who was meant to reply. With the Atus portal your customer submits the request on a page carrying your brand, attaches photos and tracks it by reference number. On your side, the request drops into a single queue, ready to become a work order.
- A page carrying your company's brand
- Access by code or public link, per customer
- Up to five photos per request
- Tracking by reference number
- Approve, reject or convert into a work order
- Kept out of search results
A portal that looks like yours, because it is
The portal shows your company's identity, not Atus's. Each customer gets their own portal address, and the link is how the system knows which provider and which customer the request belongs to — the requester never has to pick either.
Portal pages are not indexed by search engines: they are your customer's service channel, not a public shop window.
Who can submit requests, decided per customer
By default a customer's portal requires an access code, given to that customer's registered contacts. When it makes sense to leave it open — a residential building where any resident can report a problem — the customer's portal can be published to anyone with the link.
One contact can answer for several sites. In that case they pick the site before submitting, and their code never reaches a customer they are not linked to.
Requests arrive with what the technician needs to see
The requester describes the problem and attaches up to five photos taken on the spot. The photo of the leak, the dead panel or the equipment label arrives with the request — and saves the diagnostic visit that would only have seen what the photo already showed.
On submitting, the requester gets a reference number and a tracking page where they see the request's status without calling to ask.
One request queue in the dashboard
Every request from every customer lands on the dashboard's requests screen, with its photos. The team reviews each one and decides where it goes:
- Approve — the request stands and waits to be scheduled.
- Reject — out of scope, duplicated or unfounded.
- Convert into a work order — one click creates the work order, which reaches the technician through the usual flow — app, WhatsApp or web link.
Indicadores · Planta Joinville
Últimos 30 dias
MTBF
212h
MTTR
3,9h
OEE
84,2%
Backlog
11 OS
Evolução do backlog (semanas)
Fewer calls, more records
Every portal request has a date, requester, description and photos, and stays linked to the work order it produced. That record is what answers, at month end, how many requests the customer raised, how many became jobs and how long they took to serve.
Putting a customer on the portal
To open the portal to a customer, you register their contacts — name, role, phone and email — and set each one's access code. A contact can be linked to several sites, and one of them can be marked as the primary contact.
If the customer prefers an open channel, their portal is published to anyone with the link. Either way, you send the portal address to the customer once, and from then on requests arrive on their own on the dashboard's requests screen, with the reference number the requester uses to follow up.
Frequently asked questions
What every maintenance manager asks before buying.
Keep exploring
Create, prioritize and track work orders with checklists, photos, parts, signatures and an audit trail. Four types, seven statuses, branded PDF reports.
Technicians create, run checklists and complete work orders straight from WhatsApp. No app to install, no training — same rules and audit trail as the system.
Per-work-order or fixed-fee contracts with billing periods, validity and auto-renewal, percentage or manual price adjustments and covered assets.
An equipment register with code, serial number, maker, model and location, operating status and the full history of work orders and calibrations.
Ready to put control, audit and AI in one ecosystem?
See Atus running against your own scenario in a 30-minute demo.