Documinds
NederlandsSign inBook a demo
Documinds
Menu

For organisations that send a lot of letters.

And that have to be able to explain why the letter says what it says, to a recipient, a regulator or a judge.

A man fills in a form at a counter while a clerk looks on.

Municipalities

A decision has to hold legally and be understood by every resident. Legal and communications approve in one route, and the version that was sent is on record.

Letters we see often
Decisions, assessments, permits, reminders and demands
An older couple on a sofa reading a letter together.

Pension funds

Texts a regulator can ask for. For every version it is on record who approved it and when, and which letters were made with it.

Letters we see often
Value transfers, changes to the scheme, statements and covering letters
A man reading a letter at the kitchen table.

Insurers

Hundreds of variants of the same policy letter. Change one component, and every letter that names it follows, once approved.

Letters we see often
Policy letters, claims handling, premium changes, cancellation
The reception desk of a hospital, with a sign listing its wards.

Healthcare

Letters with data nobody else may see. Test post never goes to a patient, and support looks in only if you allow it.

Letters we see often
Appointment confirmations, personal contributions, referrals, results letters
A teacher in front of a class of students.

Education

Peaks around enrolment and payment. Scheduled runs send the pile, and every run says which letters failed and why.

Letters we see often
Admission, enrolment, tuition and course fees, deregistration
An aisle between tall racks in a warehouse.

Logistics

Messages from your own systems, through the API. Your reference is the key: the same one twice is one message, not two.

Letters we see often
Delivery notices, damage claims, payment reminders, rate changes
Demo

Your sector is not listed?

If you send a lot of letters, we would like to talk. We reply within one working day.

Book a demo