What problem does it solve?
Service businesses need booking that understands real availability, resources, service areas and downstream execution.
Part of HalNora One · Independent product
Standalone scope completeAppointments & scheduling
Booking and scheduling software for service businesses.
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.
Designed around
- Electricians and plumbers
- HVAC and maintenance
- Roofing and trades
- Cleaning and home services
- Professional service providers
- Scheduled field operations
Current status
On October 18 the owner approved HalNora Booking complete under the eight-point completion standard for its current standalone scope. The published app has real provider-flow, tenant/RBAC, capacity-concurrency and recovery evidence. Optional permanent Marketplace mapping, customer email activation and shared HalNora identity remain conditional future work, not part of the completed scope.
Owner-approved completion · 18 October 2026
Current standalone Booking scope is complete and parked.
This completion applies to the approved standalone scope. Permanent Marketplace mapping, customer email activation and shared HalNora identity are optional future/conditional capabilities and do not invalidate the current standalone completion status.
Live development statusStandalone scope complete
Current focusPreserve the completed standalone product; reopen only for approved optional capabilities such as permanent Marketplace mapping, customer email, shared identity or material scope changes.
Last updatedOctober 20, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
Problem, capability, connection and current stage.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
What is it being built to do?
Appointments, recurring schedules, resource requirements, service areas, rescheduling and provider workflows.
How does it connect?
Marketplace can generate service demand; Booking owns the appointment; Dispatch can own field execution; CRM can own relationship context.
Where is it today?
On October 18 the owner approved HalNora Booking complete under the eight-point completion standard for its current standalone scope. The published app has real provider-flow, tenant/RBAC, capacity-concurrency and recovery evidence. Optional permanent Marketplace mapping, customer email activation and shared HalNora identity remain conditional future work, not part of the completed scope.
Current direction
What this product is being built to do.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Appointments & services
Create bookable services and appointment records with duration, timing and customer context.
Real availability
Calculate availability from provider/resource capacity rather than arbitrary time slots.
Resources & requirements
Match appointments to people, skills, equipment or other capability requirements.
Service locations & areas
Support provider locations, customer locations and defined service areas.
Recurring bookings
Model repeat appointments and service schedules without duplicating fragile one-off records.
Rescheduling & cancellation
Treat changes as controlled scheduling actions with availability and notification consequences.
Reminders & notifications
Support customer and provider reminders as part of the booking lifecycle.
Marketplace integration
Allow service listings to originate in Marketplace while Booking remains authoritative for appointment availability.
Dispatch handoff
Pass scheduled field execution to Dispatch/Field Service without making Booking responsible for live execution.
Provider-facing workflows
Expose authenticated provider functions for availability, schedule and service management as publication matures.
Product boundary
Booking owns appointment authority.
Booking owns services, appointments, availability and scheduling rules. Marketplace owns discovery/commercial context; Dispatch owns live field execution after handoff; CRM owns relationship context.
HALNORA ONE ARCHITECTURE
Connected, not coupled.
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 →What comes next
Development priorities.
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.
Product inquiry
Interested in Booking?
Talk with HalNora about product direction, commercial use cases, partnerships or investment.