Loading…
Follow one appointment from choice to recovery.
The strongest local proof is not a feature count. It is one connected, inspectable journey in which salon-authored information remains authoritative from the public page through appointment creation and change management.
Customers pay the salon. ilinara does not process salon-customer appointment payments.
The journey starts with salon context.
The guest arrives at a known salon and location, reads salon-controlled information, and continues into that salon's services. This is not a marketplace-discovery claim.
- Salon
- Location
- Service
- Language
Service choices become a server-authored quote.
Selections that change duration, informational value, capability, or resources are resolved before availability. The browser displays the validated result; it does not invent it.
- Complete recipe
- Current duration
- Informational value
- Signed configuration token
Current availability follows the configuration.
The journey requests times for the resolved service, location time zone, booking window, notice rules, and capable professional. A displayed time can still change before creation.
- Configured duration
- Capable professional
- Location time zone
- Current rules
Creation returns the real appointment state.
The server rechecks current information when the guest submits. The result can be confirmed, requested, or changed; the interface must not turn a click into a false confirmation.
- Recheck
- Confirmed or requested
- No silent policy change
- Pay at the salon
A private link carries allowed appointment actions.
The current build can be evaluated for viewing, rescheduling, and cancelling without a customer account. The full management URL is sensitive and must not enter help, analytics, or public copy.
- View
- Reschedule
- Cancel
- Keep the link private
A changed state has an explicit next action.
Expired quotes, changed slots, changed policies, waitlist offers, and invalid links do not silently resubmit or fabricate success. Valid choices are preserved only where the current contract allows.
- Refresh the quote
- Choose another time
- Review changed policy
- Stop at terminal offer states
What this page does not claim.
These boundaries keep the product's current scope explicit.
- A production deployment
- A held slot before creation
- Guaranteed waitlist recovery
- Production messaging delivery
- Customer-payment collection
Use one real booking journey as the next check.
Start with the salon handoff that creates the most questions. The utility returns one practical action without asking for contact details.
Explore the Aysu demonstration