What problem does it solve?
Service businesses need booking that understands real availability, resources, service areas and downstream execution.
HalNora Booking is being developed as the appointment and availability authority for service businesses, resources and scheduled services—with Marketplace discovery and Dispatch execution kept separate.
Customer self-service cancellation has propagated to the same V22 Work without creating a duplicate; credential issue→rotate→use→revoke and multi-workspace isolation also passed. Direct-URL Viewer denial checks and broader provider acceptance remain open.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
Service businesses need booking that understands real availability, resources, service areas and downstream execution.
Appointments, recurring schedules, resource requirements, service areas, rescheduling and provider workflows.
Marketplace can generate service demand; Booking owns the appointment; Dispatch can own field execution; CRM can own relationship context.
Active development. Cancellation, credential lifecycle and workspace-isolation checks have advanced; direct-URL RBAC and broader provider acceptance remain open.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Create bookable services and appointment records with duration, timing and customer context.
Calculate availability from provider/resource capacity rather than arbitrary time slots.
Match appointments to people, skills, equipment or other capability requirements.
Support provider locations, customer locations and defined service areas.
Model repeat appointments and service schedules without duplicating fragile one-off records.
Treat changes as controlled scheduling actions with availability and notification consequences.
Support customer and provider reminders as part of the booking lifecycle.
Allow service listings to originate in Marketplace while Booking remains authoritative for appointment availability.
Pass scheduled field execution to Dispatch/Field Service without making Booking responsible for live execution.
Expose authenticated provider functions for availability, schedule and service management as publication matures.
Booking owns services, appointments, availability and scheduling rules. Marketplace owns discovery/commercial context; Dispatch owns live field execution after handoff; CRM owns relationship context.
Cross-product workflows use explicit contracts, authenticated events and clear authority so one product does not silently take over another product’s records.
How the HalNora platform works →HalNora prioritizes reliability, security, recoverability and real-world validation over feature count alone.
Search themes: booking software for service businesses, appointment scheduling, field service booking, contractor scheduling, service provider booking, recurring appointment software.
Talk with HalNora about product direction, commercial use cases, partnerships or investment.