Voti for private clinics
The protocol, where it is needed and without hunting
Protocols, rotas and what was agreed with each insurer stop living in a shared folder. Potens, the intelligence inside Voti, answers with the clinic’s own document in front of it and cites which one and which page.
The documentation the clinic already keeps
It goes up exactly as it is: PDF, Word, Excel or plain text. It is indexed in seconds, with the status visible, and from that moment its contents can be asked about.
- Staff induction manual· p.7
- Sterilisation protocol· p.4
- On-call rota· p.1
- Booking and cancellation policy· p.3
- Insurer agreement· p.5
- Equipment maintenance plan· p.2
- Consent form (template)· p.2
- Training record· p.6
Nothing is rewritten or summarised: it is indexed and cited. And deleting a document deletes what was indexed from it.
Three questions asked at the front desk
The answers come from the clinic’s document, not from the model. When no document supports one, Potens says so, and the question is logged without an author on the list of what still needs writing down.
What paperwork do we need from someone joining the team?
The list from the induction manual, in order and with who checks it.
Staff induction manual· p.7What exactly does the agreement with this insurer cover?
What the signed agreement says, with its terms and how long it runs.
Insurer agreement· p.5What do we do when a booking is cancelled inside a day?
The written policy, and who can make an exception to it.
Booking and cancellation policy· p.3
What runs out in a clinic
A deadline is not an appointment. It is an entity with a type, a due date, an owner and a severity, and the severity is computed on the server: seven days out it becomes a warning, two days out it becomes critical. Each morning it goes to whoever owns it, in the app and by email, in their language.
- An insurer agreement up for renewalWith an owner and a severity, in the morning notice.
- A mandatory equipment inspectionLogged as a deadline, with its type and its owner.
- An accreditation or a licence expiringType expiry, with its date and its assigned owner.
Who sees the rota and who sees the contract
Voti has five roles, from owner to guest, and the role sets the starting point. The detail does not come from it: it comes from per-document, per-person permissions, granted and withdrawn one at a time. Denial always wins, and they protect against Potens too — a document outside someone’s reach never enters their answer, whole or in fragments.
- Someone who joined this week
- The induction manual and the protocols opened to them. Nothing else.
- Whoever coordinates a service
- The protocols and rotas for their service.
- A visiting practitioner
- Only the protocols for the service they work in.
- Admin
- The whole archive, and the record of every access and every denial.
What adapts to your clinic, and what does not
There is no clinic edition of Voti. There is a description of the clinic — written at sign-up, changed whenever it needs to be — that Potens carries into every answer.
- It does not integrate with your practice management system or any clinical software: Voti neither reads from nor writes to them.
- It is not a patient booking system and it does not bill insurers. It holds the clinic’s documentation and the deadlines around it.
- It ships with no protocols or clinical corpus. The archive is the clinic’s own, and suggested questions come from its own documents.
The protocol is already written down. It just does not answer yet.
Upload one protocol and an insurer agreement, ask what gets asked at the front desk, and see in seven days whether it fits.