From booking to the door.

Smart Access connects each stay with the access it actually requires: the right unit, any shared entrances, validity, guest instructions and operational device oversight.

Operational value

Creating a PIN is only one part of the job.

Access must match the right booking and unit, work during the intended time window and cover every door the stay requires. Communication, expiry and the physical state of each lock belong to the same operational problem.

Access must be correct, valid at the right time and available at the right doors.
  • Booking and unit
  • Time window
  • Shared access
  • Guest instructions
  • Expiry or revocation
  • Lock status

Core workflow

The stay becomes the context for access.

Hestix keeps booking context, configured doors, validity and the operational information guests need within one coherent flow.

  1. Booking
  2. Unit
  3. Required access
  4. PIN / access
  5. Validity
  6. Guest instructions
  7. Expiry / revocation

Coordinated access

One booking may need more than one door.

Apartment access may need to work alongside a gate, building entrance or another shared lock configured for the stay.

Hestix can coordinate access associated with the stay, including the same code across configured access points when supported by the provider. Availability depends on both configuration and provider capabilities.

Lifecycle and devices

Access remains an operational process, not an isolated code.

Smart Access follows access in the context of the stay and also exposes the physical condition of the devices that must be ready for guest arrival.

Access lifecycle

  1. Availability

    Access is prepared for the intended configuration.

  2. Association

    The stay, unit and required access remain connected.

  3. Validity

    The configured time window follows the stay period.

  4. Oversight

    Status and operational attention points remain visible.

  5. End of stay

    Expiry and revocation follow the configuration and provider capabilities.

Physical access health

Knowing a code exists is not enough if the lock is not ready when the guest arrives.

  1. Locks
  2. Battery status
  3. LOW / CRITICAL
  4. Alert
  5. Report

Real product proof

Physical attention points become visible.

The report surfaces monitored devices, thresholds, battery state, connectivity and last synchronization. It proves Smart Access observability without reducing the whole domain to battery monitoring.

Smart Access report with monitored devices, battery thresholds and access points requiring attention.

Provider

Smart Access remains the Hestix domain.

Available integration: TTLock

Hestix coordinates the workflow at its own operational layer and keeps Smart Access separate from the provider’s commercial identity. TTLock is the integration currently available for public communication.

Frequently asked questions

Smart Access, in brief.

Does Smart Access replace TTLock?

No. Smart Access is the Hestix capability coordinating the operational workflow; TTLock is the provider currently integrated.

Can one stay use the same code across multiple access points?

Hestix can coordinate the same code across associated, configured access points when supported by the provider. This is not a universal promise for every lock or provider.

What happens at the end of the stay?

Expiry and revocation are part of the access lifecycle; the exact behavior follows the configuration and provider capabilities.

Does Hestix also monitor battery status?

Yes. The Smart Access report shows monitored devices, battery thresholds and access points requiring attention.

Smart Access in practice

Want to connect stays, access and operational oversight?

The demo starts from your units, the entrances each stay requires and the provider you use today.

Request demo access