Frequently asked questions
FAQ
Transparent and concrete. No marketing fluff.
Why WhatsApp for requests, and dashboard for management?
WhatsApp is the fastest interface on-site (pin/voice/photo). The dashboard is the control room: overview, sharing, roles, and audit logging. Together it's both fast and manageable.
What's the biggest advantage vs. portal + emailing files around?
You remove friction and noise: requests start in WhatsApp, output goes controlled via dashboard links and exports. Fewer attachments, fewer versions, fewer 'who has the right one?'
How does sharing with my team work (without chaos)?
You share one project via the dashboard with the right permissions. Everyone works from the same source (viewer/exports), instead of loose PDFs in group chats.
Can I set permissions/roles (who can request, who can only view)?
Yes. Roles keep responsibility in the right place: field can execute, office can manage. This prevents errors and maintains control over volume and compliance.
How does this help with WIBON/'proof on-site'?
The field has quick access to the right info (viewer/link), and the system logs relevant actions (audit trail). This makes compliance practically feasible.
What does it automate and what not?
Yes: structuring, checks, summarizing, viewer/exports and file management.
No: taking over your duty of care or guaranteeing nothing is there. You keep final control, we make the process tight.
No: taking over your duty of care or guaranteeing nothing is there. You keep final control, we make the process tight.
What if someone provides wrong info in WhatsApp?
That's why there's dashboard control: you see what's been recorded, can validate/correct, and keep a traceable file. WhatsApp is input; the dashboard is the truth.
How quickly does this save time?
From day 1, because you eliminate onboarding hassle (accounts/portals) and standardize the process. Teams notice savings mainly through less handover, less searching, and faster action.
How about security and privacy?
Sensitive data is stored encrypted and access runs via secured tokens/roles. Data deletion is possible (except payment/invoicing records that may need to be retained by law).
What happens during downtime or delays (Kadaster/WhatsApp)?
Then you want transparency and escalation: status, logging, and clear support agreements. This is exactly why you want a dashboard layer alongside WhatsApp: you're not dependent on loose chat messages.
How do you handle security and privacy?
Sensitive data is encrypted at rest and access uses secure tokens and roles. Data can be deleted where permitted (except payment/billing records that may need to be retained by law).
What happens during outages or delays (Kadaster/WhatsApp)?
You need transparency and escalation: status, logging and clear support agreements. That is why you want a dashboard layer next to WhatsApp-you are not dependent on scattered chat messages.
Contact us if you have questions
Don’t see your question? Message us - we reply fast.