PacoYour team hears from him what is coming, and proves what is done
The third path: something is your team's to fix. A booked visit, a finding to fix, a task to do: Paco tells the right colleague on WhatsApp, reminds them if it sits, and receives the photo that proves it is done. You validate. What is blocked says so, instead of reading as forgotten.
He only reminds about what a human already approved
A message to a colleague always carries a witness: the task a manager created, the visit you approved, the duty whose frequency you confirmed. No witness, no message. With one, a reminder at most every 48 hours, three per task, a week, then it is yours. Every reminder carries the witness that allowed it, so "why did Paco message my technician?" is answered from the register.
- On WhatsApp, over a verified link the person opened themselves
- The colleague can say stop; so can the manager; either is a receipt
- Never to a contractor: that is the other rail, with your approval
A photo says when and where it was taken
A colleague sends a photo over WhatsApp, from the app, or in the chat; all three paths go through the same reading. At receipt, and once only, Paco records what the file says about itself: the shutter time, the position, the camera, and a fingerprint of the bytes. A photo taken three weeks before the work was claimed done, or somewhere else, no longer looks like one taken on the spot that morning. You judge; he gives you what to judge with.
- Read from the file itself, not from the upload time
- A photo without that data says so; it is not rejected
- Validation stays a human act, never a mandate
A blocked task no longer looks like a forgotten one
The technician waiting on a part has somewhere to say so. So does the manager who consciously pushes work out. Each of those states requires a reason, keeps its date, and is never "overdue" on the register. Reminders stop for the person who already said why. The reason lives on the task while the state holds, and on the history forever.
- "Waiting on a part" and "deferred" are states, not excuses
- A reason is required; without one, the state is refused
- A task born from a finding keeps its original evidence
Common questions
Do my staff have to install anything?
No. They link their WhatsApp once, from their own phone, and Paco writes to them there. Without that link, he does not write to them.
What if the photo has no position?
The proof says "no position" and you judge as before. Paco does not reject a photo on that ground; he only refuses to pass off missing data as verified data.
See a brief go out, and a photo come back
With the time and place the phone actually recorded.
Book a demo