Your developer or software vendor connects it
Your own developer, or the company behind your system, connects dokus once. From then on, documents make themselves from your data.
Service reports and certificates, made from the work itself.
Technicians record the job once. dokus makes the service report, the certificate and the customer's copy from it, on your templates, with proof of each.
From a visit to a signed report.
What the technician records fills every document the customer receives.
Service reports
Checks, readings and results from the job, one line per check.
- DocumentsAvailable
- FormsPlanned
Certificates
Calibration, inspection and completion certificates from the same results.
- DocumentsAvailable
Customer sign-off
The customer signs the report on site.
- SignaturesPlanned
Schedules
The next visit planned and the customer reminded.
- CalendarPlanned
Records
Every report and certificate kept with proof, ready for audits.
- Proof of every documentAvailable
- FilesPlanned
Inside the software you already use.
Three ways to start, depending on who runs your software.
A pilot with dokus
We connect your system for one set of documents, and your team checks every page before it goes out.
Studio, without a developer
In early access: the people who own the documents upload their own Word templates, mark the blanks and make documents on the dokus website.
The dokus products behind it.
Available today, with the next tools joining as they ship.
- DocumentsAvailable
PDF and Word files from your data and your own Word templates
- FormsPlanned
Collect answers that go straight into your system
- SignaturesPlanned
Several people sign the exact same file, in order
- CalendarPlanned
Schedules, bookings and reminders
- Proof of every documentAvailable
Which template, which data, when, and a fingerprint
- FilesPlanned
Store and share files with the right people
Bring one report your technicians fill in every day.
Thirty minutes on your own template and your own data. You see it made by dokus.