Use case
Turn a fault report into a work order and follow it through
With CloudotNet every reported fault becomes a numbered work order: it's assigned to the right technician or group, closed with photos, and the right people are notified according to the rule you set. Who took which step and when stays in the work order's history.
How it's done today, and what's hard
Faults are reported by phone, by message or in passing in the corridor. Urgent ones get handled right away; the rest end up in a notebook or in someone's head.
The hard part comes after the report. It isn't clear who has the fault, when it was fixed, or whether it was really fixed. The person who reported it calls again to ask.
Step by step with CloudotNet
- Open the fault as a work orderEnter the title, description, priority (Low, Medium, High, Critical), category and location. The work order number is assigned for you.
- Assign it to a technician or a groupGive the job to the on-call technician or the technical service group. Everyone in the group sees a job given to the group.
- Set up a priority ruleBuild a rule such as “if the priority is Critical, notify the technical lead right away” by choosing steps. No code involved.
- The technician takes it from their phoneThey accept and start the job, and pause and resume it if needed. Every step goes into the work order's history.
- Close with photosRequire before / after photos. The job can't be completed while a required document is missing.
- Add a sign-off if you wantAdd a step that asks the technical lead for approval when the job is completed. If they reject it, the technician is notified and the job can be reopened.
- Notify peopleWhen the job is closed, the manager and the right people get an email and an in-app notification.
Frequently asked questions
How does a fault become a work order?
The fault is opened as a task in CloudotNet and gets a work order number automatically. Priority, category, location and assignees sit on that record, and every step is logged in its history until it's closed.
Are the right people told straight away about urgent faults?
Yes. You set up a rule that sends email and in-app notifications to different people based on priority or location; the rule is built by choosing steps, without code. You choose who gets the job when you open the task.
Can tenants or customers report faults themselves?
Today faults are opened by the users you invite to CloudotNet, and you decide who can see and open what. A Request and Help Desk that collects tenant, employee and customer requests in one place is on our roadmap.
How do I know a fault was really fixed?
You require before / after photos or a report. If you want, you add a sign-off to the closure; if the approver isn't satisfied, the technician is notified and the job can be reopened.
Can I see faults that keep coming back in the same place?
Yes. You define your location tree and follow jobs by location. Past faults at a location, and how they were closed, show up in the history.
Other use cases: Assign jobs to field staff, Job tracking instead of WhatsApp, Scheduled maintenance without spreadsheets, Multi-level approval, Mobile checklists, Equipment and vehicle records · All use cases →
Got a question? Let's talk directly.
Tell us about your work and we'll walk you through the right setup on screen. Or just give us a call.
Prefer to try it yourself? Create a free account →
