Naar de inhoud
vxori
Fire-alarm logbook · NEN 2654

Every fault that comes in lands in the logbook by itself.

A fire-alarm company has to record what happened per installation: fault, false alarm, maintenance, inspection, decommissioning. That logbook (Dutch standard NEN 2654) is often filled in afterwards — from a note, an email, or the engineer's memory.

With this module Voxori pushes a completed call straight into the logbook of the right installation: who reported what, when, at which priority. You see it on the Fire-alarm tab in your portal, under the object it was about.

Bespoke for fire-alarm companies · price agreed separately · not self-service yet

GDPR
real data erasure + audit trail
EU AI Act
transparent AI disclosure to callers
NL hosting
Amsterdam · register per sub-processor →
Human fallback
forwards to your number
Data processing agreement
standard, GDPR art. 28 (Dutch) →
SLA + status page
availability target per plan (Dutch) →

In pilot

In pilot means: built and tested, not live by default. We switch this module on per customer after a guided start — listening in on a few real conversations before anything runs unattended.

Two switches, both off by default. You switch the module on in your portal, and we have to have released it platform-wide. If either one is missing the module does nothing — no half measures, no button that quietly does nothing.

This module is deliberately not on the build-your-own price list: it is bespoke work we set up per customer, and the price is agreed in that process. So there is no switch and no fixed monthly fee — but an honest conversation about what it would be for you. What is actually true today is stated below.

A register, a logbook, and the call that fills it

You record the installations per client: fire-alarm system, evacuation system, extinguishing equipment. Manually in the portal, through a CSV import or through a webhook from your own system. Each installation gets its own logbook and a place for documents — inspection report, maintenance certificate, handover document.

When a building manager phones in a fault, or someone books the annual maintenance, Voxori runs the call the way it always does for fire-alarm companies: take the report, schedule a service visit, forward immediately on fire or immediate danger. What is new is what happens after the call: the outcome is written as a logbook entry under the right installation — type (fault, false alarm, maintenance, inspection), priority, who reported it, and the source “phone”.

The logbook is factual, never judgemental. It records what was reported and planned; what is technically wrong and whether the installation is safe is for your engineer to judge — not the AI.

What it does

Fire-alarm logbook, concretely.

Register of installations per client

Fire-alarm, evacuation and extinguishing systems with address and contact. Manual, via CSV or via a webhook from your own package.

A logbook entry after every completed call

Fault, false alarm, decommissioning, maintenance, inspection or service visit — with priority (urgent, high, normal, low) and the caller's name.

Urgent stays urgent

Fire, smoke, a gas smell, a stuck lift: that is forwarded to your fault desk during the call. The logbook entry comes afterwards and never holds a call up.

Documents with the installation

Inspection reports, maintenance certificates and handover documents live with the object they are about — not in a loose folder.

Status per entry: open, in progress, resolved

A report does not close itself. Your engineer resolves it — and that, too, goes in the logbook, with who and when.

Connectors: CSV and webhook

Import and push via CSV or a webhook (also to Zapier) work today. Connectors to manufacturer platforms are listed as planned — not as available.

Honestly bounded

What the fire-alarm logbook does not do

In fire safety an overpromise is more dangerous than an honest limit. These are the edges:

It makes no technical or safety judgement. The logbook records what was reported and planned. Whether an installation is safe, or a fault serious, is decided by your engineer on site — never by the AI.

It does not replace your fault desk. On fire or immediate danger Voxori forwards; it fixes nothing and never waits for the logbook. The push is best-effort and may never delay a call.

It does not (yet) talk to manufacturer platforms. Connectors to manufacturer platforms are listed as planned. Today CSV import and a webhook work — we promise nothing more.

It is not a switch on the price list. The module is double-gated and only for the fire-alarm template. We set it up per customer; there is no self-service and no fixed monthly fee.

It is not the statutory logbook itself. Voxori fills and keeps a digital logbook. Whether it may replace the formal NEN 2654 logbook for your client is for you to agree with the certifying body — not a statement we can make.

What does it cost?

The fire-alarm logbook is not on the build-your-own price list and not part of Voxori Complete either. It is bespoke work for fire-alarm companies: we set up the register, the connectors and the push per customer, and the price is agreed in that process. Ask us through the contact form — we will tell you honestly what already works today and what does not.

Frequently asked questions

Questions about Fire-alarm logbook.

What exactly goes into the logbook after a call?

The event type (fault, false alarm, decommissioning, maintenance, inspection, service visit or note), the priority, who reported it (name and phone number if the caller gave them), a short summary and the source “phone”. The call itself stays in your portal as a transcript.

How does Voxori know which installation a report belongs to?

Through the register: the caller names an address or client, and Voxori looks up the matching installation. If none is found, the entry appears as unassigned in your portal so you link it yourself — it never guesses.

Can I import my existing list of objects?

Yes, via a CSV file or via a webhook from your own system. Both work today. Connectors to manufacturer platforms are planned, not yet available.

Which companies is this for?

Only customers on the fire-alarm template. The module stays off until we switch it on together with you, after a guided start in which we listen in on the first real reports.

What does it cost?

There is no fixed monthly price: it is bespoke, and the price depends on what we set up for you. We discuss that up front — you are never billed for something that is not running yet.

See also Voxori for fire-alarm companies, Look-up in your own system or Integrations. Question not answered? Check the full FAQ or ask us directly.

WhatsApp