Services and rules
Set duration, staff, rooms, buffers, eligibility, and preparation.
Let customers book an eligible time, complete the right preparation, and manage changes while staff sees the full appointment context.
Service, customer, practitioner, room, availability, intake, payment state, communication, attendance, and outcome stay connected.
Set duration, staff, rooms, buffers, eligibility, and preparation.
Calculate slots from staff, resources, opening hours, and bookings.
Collect relevant details, documents, consent, and preparation.
Coordinate reminders, rescheduling, cancellation, and waitlists.
Keep visits, notes, preferences, outcomes, and next steps together.
See arrivals, pending forms, open slots, no-shows, and workload.
Who it's for
Coordinate practitioner, room, intake, consent, arrival, and follow-up around each visit.
Manage services, staff, equipment, packages, reminders, and repeat bookings.
Schedule lessons or consultations with participant details, preparation, and notes.
Customers need a simple booking path; staff needs reliable availability, complete intake, and an actionable daily schedule.
A slot appears only when the service duration, eligible practitioner, required room or equipment, buffers, opening hours, and existing commitments fit together.
The appointment record shows required forms, documents, consent, preparation, and exceptions beside the customer and service. Staff can request missing details before the visit begins.
Confirmation, reminders, reschedules, cancellations, check-in, notes, outcome, and follow-up remain attached to the appointment instead of becoming disconnected messages.
Front desk, customers, and managers see the same appointment through views built for their part of the visit.
See arrivals, pending intake, open slots, practitioner changes, and no-show risk in time order.
Book, complete intake, view preparation, reschedule, cancel, and follow approved next steps.
Compare demand, lead time, utilisation, cancellations, no-shows, and follow-up by service or practitioner.
Standard schedulers offer fixed services and time slots. Component.app can adapt eligibility, resource combinations, intake, pricing, approval, and follow-up.
Availability, questions, preparation, deposit, package credit, price, and approval can vary by customer type, service history, age, location, membership, or configured criteria.
A proposed appointment can require an eligible practitioner, room, equipment, capacity, and preparation time together. Unusual combinations remain held for operations review.
Confirmation can prepare a payment request, message, or calendar event through supported providers. Exact payment, reminder, and calendar behaviour depends on the selected integration and setup.
Availability, intake, exception review, confirmation, attendance, and next steps stay attached to the appointment.
The customer selects the service, location, and eligible slot.
The system checks resources, eligibility, intake, and payment state.
Staff confirms unusual resources, intake, or approval conditions.
Publish the booking, update attendance, and create follow-up.
It lets customers and staff book services against available practitioners and resources, then manage intake, confirmation, changes, attendance, notes, and follow-up.
Availability can combine service duration, practitioner eligibility, staff and room schedules, equipment, capacity, buffers, opening hours, lead time, and existing bookings.
Yes. Questions, documents, consent, and preparation can vary by service, customer type, location, prior answer, or other configured criteria.
Yes. Selected services, customers, resource combinations, intake answers, or payment exceptions can require staff review before the appointment is confirmed.
Yes. Self-service changes can follow the applicable notice period, fee, refund, package-credit, waitlist, and resource-release rules.
It can connect to selected third-party providers where their APIs and the agreed setup support the required workflow. The exact data exchanged, actions available, and ongoing provider fees depend on that integration.
The system can support PDPA obligations through role-based access, purpose and consent records, correction workflows, retention rules, and appropriate security controls. Compliance also depends on your policies, hosting, integrations, and day-to-day data handling.
Show us your services, availability, intake, change policies, and daily operations. We will connect them in one appointment journey.