How to use Cadence /

Before you begin

Explore the public interface with example records first. Its preview interactions stay in the current view; use the workspace link to open the account-backed product described below.

Create an account in Cadence and work in its own private workspace. Accounts and records from another Lumia product are separate. Appointment and facility operators reserving one room, person or service station per resource, with operator confirmation and explicit local working hours.

Follow the workflow below to understand the application. Contact Lumia for a guided walkthrough; account access is private. An exported file reflects the record at the time of export.

Define the actual resource

Create a resource with its recognized timezone, weekly working intervals and hold duration. The current model uses capacity one. Set hours for the resource's local day and review any blocked periods before sharing availability. Separate independently bookable rooms or people into separate resources rather than inflating capacity beyond the supported reservation contract.

Place a temporary hold

Choose a future interval and enter the customer's required details. The server checks the full interval against working hours, blocked periods and other active holds or confirmed bookings. A hold temporarily protects capacity but is not yet a confirmed appointment. If a competing request wins, choose another available time instead of assuming the original request succeeded.

Confirm or release explicitly

An authorized owner confirms an active hold after reviewing its details. Repeating the same confirmation returns the saved booking rather than creating another appointment. Cancel an abandoned hold or confirmed booking through its appropriate action. An expired hold cannot be revived by a late confirmation; create a new hold after rechecking current availability.

Retain the appointment record

Reload the saved booking to verify its status and timestamps. The application provides an ICS calendar export for the booking record; distributing or importing that file is a separate step. Do not describe a temporary hold as paid or confirmed. The tested local confirmation mode records payment as not required and does not collect a charge.

Operating the product

Start with the public interface to explore the design using example records. These interactions stay in the current view. Open the private workspace from the interface to use the existing account, storage and product workflows.

Maintain the resource timezone and opening hours deliberately. Inspect scheduled reservations before changing an operating assumption or blocked period.

On conflict, reload availability and choose a new interval. On expired hold, request a fresh hold; do not repeatedly confirm stale state.

Use cancellation to release a reservation and retain its history. Verify the saved booking status before communicating confirmation outside the app.

Before adding payment or external calendar connectors, define hold expiry versus payment timing, duplicate webhook handling, refunds, permissions and reconciliation as separate acceptance criteria.