Build the booking foundation first. Add automation when it is ready.
Kutwise is being developed in a deliberate order: reliable shop setup and customer booking first, then payments, communication, and voice automation on top of a proven scheduling workflow.
A reliable booking launch.
The current release focuses on the workflow that determines whether a customer can successfully choose a real appointment time from a real shop.
- Owner onboarding with organization and location creation
- Guided launch checklist for service, barber, assignment, and availability readiness
- Customer booking based on active services, public staff, and real availability
- Booking policy controls for lead time, booking horizon, slot intervals, and confirmation behavior
- Owner appointment operations and customer account cancellation or rescheduling
Operational layers that follow a proven booking flow.
These modules are planned after a pilot shop completes setup and the real booking path is validated end to end.
Deposits and payment lifecycle
Connect payment collection to the booking flow, record payment state, and handle refunds or cancellation outcomes responsibly.
Customer notifications
Add transactional confirmations, reminders, cancellation notices, delivery tracking, and consent-aware communication settings.
Production AI receptionist
Connect live telephony, shop knowledge, escalation rules, and logging only after scheduling and customer communication are proven in a pilot.
What a pilot shop needs before sharing its link.
- An active public location with the correct timezone.
- At least one active public service and price.
- A public barber assigned to that service.
- An active availability window at the selected location.
- Booking settings reviewed for lead time, horizon, and confirmations.
Trust before automation.
Customer-facing pages should reflect real shop data rather than sample services, availability, or pricing. The public directory therefore shows only booking-ready tenants.
Scheduling rules are enforced by the booking APIs, not just by the interface. This keeps lead-time, booking-window, staff availability, and overlap rules consistent.
Payments, notifications, and AI voice features will be introduced as production capabilities with their own reliability, consent, and operational controls.
Want a private branded platform instead?
Multi-location operators and private deployments can explore a separate, contract-scoped rollout path.