Part of HalNora One · Independent product
In development
Appointments & 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

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.

Live development statusActive development
Current focusProvider QA, direct-URL RBAC acceptance, publication/live-email controls and broader authenticated modify/cancel workflows.
Last updatedOctober 12, 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.

01 · PROBLEM

What problem does it solve?

Service businesses need booking that understands real availability, resources, service areas and downstream execution.

02 · CAPABILITY

What is it being built to do?

Appointments, recurring schedules, resource requirements, service areas, rescheduling and provider workflows.

03 · HALNORA ONE

How does it connect?

Marketplace can generate service demand; Booking owns the appointment; Dispatch can own field execution; CRM can own relationship context.

04 · STAGE

Where is it today?

Active development. Cancellation, credential lifecycle and workspace-isolation checks have advanced; direct-URL RBAC and broader provider acceptance remain open.

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.

01

Appointments & services

Create bookable services and appointment records with duration, timing and customer context.

02

Real availability

Calculate availability from provider/resource capacity rather than arbitrary time slots.

03

Resources & requirements

Match appointments to people, skills, equipment or other capability requirements.

04

Service locations & areas

Support provider locations, customer locations and defined service areas.

05

Recurring bookings

Model repeat appointments and service schedules without duplicating fragile one-off records.

06

Rescheduling & cancellation

Treat changes as controlled scheduling actions with availability and notification consequences.

07

Reminders & notifications

Support customer and provider reminders as part of the booking lifecycle.

08

Marketplace integration

Allow service listings to originate in Marketplace while Booking remains authoritative for appointment availability.

09

Dispatch handoff

Pass scheduled field execution to Dispatch/Field Service without making Booking responsible for live execution.

10

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.

01

Publish the current Booking application through the approved production path.

02

Connect a real email sender and validate reminder delivery/retry behaviour.

03

Complete provider-facing functions and authenticated device/provider QA.

04

Finish Marketplace service publication and explicit appointment-creation contracts.

05

Validate Booking → Dispatch execution handoff for field-service scenarios.

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.

Contact HalNora