Modular by design

Four modules. One clear workflow.

Guest registration, verification, service cases, and partner services can be activated individually. All four modules share the same role, status, evidence, and governance logic.

Connected Oprivia modules for roles, tasks, communication and evidence
Impact before feature volume

One bottleneck, one module, one measurable effect

Not every module needs to be activated at once. The starting point is the area where questions, delays, rework or missing evidence currently create the greatest operational effort.

Guest registration

Bring required information to the correct stay in full and on time.

Identity verification

Distinguish missing, confirmed and unresolved information.

Guest cases

Prioritize, assign and move reports through to an outcome.

Housekeeping and partner tasks

Connect assignment, execution, evidence, rework and acceptance.

Module 01

Guest registration without repeated follow-up

The module guides guests through the required registration steps, requests the necessary information and connects it to the correct stay.

Missing or inconsistent information becomes visible before it delays arrival, handover or internal preparation. Identity and specific compliance checks remain within the dedicated verification module.

  • Benefit: Complete required information before arrival or the start of the stay.
  • Typical cases: Invitation, data entry, question, correction and confirmation.
  • Completed state: A clear registration status showing open, resolved and completed steps.
Abstract registration workflow showing required guest details, open steps and completion status before arrival.
Abstract review model showing identity, contact and reporting details assigned to a stay with visible review status.
Module 02

Identity verification and required data

Identity, contact, reporting and business data are connected to the correct stay or user profile and maintained with a visible verification status.

Email, phone, KYC, Advanced KYC and KYB checks are used only where technically enabled, contractually agreed and legally permitted. Unclear or critical results remain assigned to an authorized person for review.

  • Benefit: Capture required information for a defined purpose and clearly identify its verification status.
  • Typical cases: Email and phone confirmation, document verification, identity checks, registry or business checks and manual review.
  • Verification state: Information is user-provided, verified, open, rejected or marked for manual review.
Module 03

Guest requests become cases, not chat messages

Questions, incidents, damage reports and additional requests are captured as specific cases, prioritized and assigned to a responsible party.

The status remains visible until a resolution, referral or documented decision has been recorded.

  • Benefit: Assign, track and complete service cases clearly.
  • Typical cases: Technical issue, damage, additional requirement, question, handover and escalation.
  • Documentation: Intake, ownership, history, response and outcome remain traceable.
Abstract service case workflow showing questions, incidents and additional needs assigned with priority and traceable status.
Abstract partner-service workflow showing cleaning, facility work, photo evidence, rework and acceptance linked to one case.
Module 04

Housekeeping through documented approval

Cleaning, facility work, repairs and other partner services are managed from assignment through to documented acceptance in one shared order.

Time windows, checklists, questions, photo evidence, exceptions and rework remain visible until the assignment can be fully completed.

  • Benefit: Manage recurring and event-driven services reliably and complete them with evidence.
  • Typical cases: Cleaning, laundry, facility assignment, repair, photo documentation, rework and acceptance.
  • Assignment status: Allocation, acceptance, execution, exception, rework and approval remain connected to the assignment.
Shared operating logic

Four modules, one shared record

Each module addresses a different bottleneck. The operating logic remains consistent: outcomes, records, and approvals stay linked to the relevant case, making completion traceable.

Capture

Information is recorded where it arises.

Connect

Each item is linked to a stay, property or assignment.

Process

Open points move through defined handling steps.

Approve

Authorized roles review the required records, document approvals or exceptions, and confirm closure.

Which module addresses your bottleneck?

The right starting point depends on the operating model, property structure, involved roles and current points of friction. A pilot can begin with one limited workflow and expand once the logic has been tested.