Appointments and services

Appointments that stay connected to the person and the sale.

A service visit has a customer, a staff member, a duration, and an operational state before it ever reaches checkout. LiftedPOS keeps that visit inside the same tenant and location context as the team, customer record, services, and transaction.

Work from a weekly calendar or a focused list

Review appointments on a weekly calendar or switch to a searchable, filterable list. Staff can create, edit, and remove appointments while preserving the service type, assigned employee, date, start time, duration, customer contact details, and working notes.

Make the state of the visit explicit

Appointments can move through pending, confirmed, in progress, completed, cancelled, and no-show states. That shared vocabulary helps the desk and the service team understand whether a visit still needs confirmation, is actively underway, or should no longer consume attention.

Protect a staff member from active overlap

The server checks active appointments for the same employee and rejects conflicting time windows. The protection applies to visits that still occupy the schedule rather than treating cancelled or completed history as live work. Operators can address the conflict instead of discovering two customers assigned to one person.

Carry the visit toward checkout

The appointment holds the customer and service context required by the operation, and the checkout workflow can optionally retain the appointment relationship. LiftedPOS does not advertise unverified reminder automation here; messaging and rollout behavior should be confirmed for the merchant configuration.

What to verify in a demo

Use the actual workflow, inspect the resulting record, and ask how the behavior is configured for your locations. Availability can depend on enabled modules, hardware, and payment setup.

Move from the feature to the operation

LiftedPOS is designed so this capability does not sit alone. It shares customer, employee, product, location, transaction, and reporting context with the rest of the system. That is the difference between checking a feature box and removing a handoff from the day.

See the whole operation move.

Open a real demo store, ring a sale, and follow what changes.

Run the live demo