Bookings should run smoothly. Even when the team is busy.
A call comes in. A LINE message arrives. A colleague checks the calendar while someone else updates a spreadsheet. ARZ AI starts with this daily friction and connects booking entry points, operating rules, review states and existing systems into one workable flow.
Taiwan · Founded February 2026Early booking product implementedMulti-business SaaS in development
This page describes product design and project implementations. The interactive booking on our homepage is a front-end demonstration and does not create real orders. Feature availability and onboarding depend on the deployed product version.
A booking starts a workflow. It does not finish one.
A date picker alone cannot coordinate an operation. Each appointment needs to pass through a reliable sequence of rules, review and follow-up. Here is the process we developed from venue scheduling work.
01 / Customer
Open the booking entry
Customers enter through LINE, choose a service or venue, and explore options without waiting for manual replies.
02 / System
Calculate availability
Use opening hours, closures, session length, buffers and occupied slots to calculate valid choices.
03 / System
Recheck on submission
Check conflicts again when a customer confirms, reducing the risk of simultaneous double bookings.
04 / Staff
Review and coordinate
Operators manage requests, approval states and exceptions from an administration workflow.
05 / System
Notify and connect
Depending on deployment, send reminders and export records for existing business software.
ENGINEERING EVIDENCE / REAL SYSTEM SCREENS
See the rules behind the product.
These screenshots come from the sports venue LINE booking project. They show implemented venue resources, weekly opening hours and exception management. They are engineering project screens; they do not imply that every business already has access to a standard SaaS product.
REAL SYSTEM SCREEN 01Venue resourcesManage venues, ordering and availability.REAL SYSTEM SCREEN 02Weekly schedulesSet recurring booking hours for each venue.REAL SYSTEM SCREEN 03Schedule exceptionsManage closures, maintenance and temporary hours.
INTERACTIVE SIMULATION
Try the journey from booking to staff review
The walkthrough calculates available slots and lets you submit, review and approve a sample request. Data stays in the demo page and creates no real booking.
Source: ARZ AI sports venue LINE booking engineering project. The public gallery uses settings screens without customer names, phone numbers or order records.
02 / SAAS ARCHITECTURE
One working process. A platform for many businesses.
We are turning recurring project rules into configurable modules. The platform direction lets an administrator create business accounts and assign industry templates while each business defines its resources, services, hours and policies.
01Customer entryLINE / mobile web
02Rules and dataSlots, forms, conflicts
03Business workspaceReview, manage, export
04Alerts and integrationExisting workflows
TARGET SAAS BLUEPRINT
Turn repeatable project workflows into configurable platform modules.
Multi-business platform in development
BUSINESS WORKSPACES / planned independent settings and data
Venue operator AVenues, hours, staff
Service team BServices, people, booking rules
Event organizer CEvents, forms, order fields
01 / ENTRY
Customer entry
LINE, mobile web and embedded forms
02 / CONFIG
Business configuration
Resources, opening hours, form fields and exceptions
03 / WORKFLOW ENGINE
Shared workflow engine
Availability, buffers, conflict checks and order states
04 / OPERATIONS
Operations workspace
Calendar, human review, exports and documents
Integration layerLINE notificationsPayment statusExisting systemsReports and PDFs
AI assistance roadmap
Claude may help interpret requests, organize details and draft replies. Explicit rules and authorized staff confirm availability, payments and consequential changes.
This is a product direction diagram. Scheduling and document workflows have engineering project foundations; multi-business accounts, tenant data isolation and self-service onboarding are still being productized and are not presented as a launched multi-tenant SaaS.
Existing engineering base
Built in project implementations
LINE booking entry and slot selection
Opening hours, exceptions and buffer rules
Conflict validation and booking statuses
Administration workflow and data export
Under development
Multi-business SaaS being developed
Business accounts and industry templates
Independent venue, instructor and service setup
Tenant data boundaries and role-based access
Reusable releases and onboarding workflows
03 / INDUSTRY TEMPLATES
A shared engine. Industry-specific ways of working.
Reuse the common logic while configuring what genuinely differs across industries: resources, data fields and operating rules.
01 / Project implementation basis
Sports and venue spaces
Resource = venue
A venue may have multiple spaces, opening hours, buffers and exceptions affecting bookable time.
02 / Industry template planned
Instructors and studios
Resource = person / service
Appointments can be based on consulting services, classes or instructors. Configurable resources are on the platform roadmap.
03 / Project implementation basis
Events and temple workflows
Resource = event / form
Registration can extend into pricing options, orders and generated documents. A separate implementation informs these modules.
04 / FIELD PROOF
Two practical cases. One product direction.
We learn from demanding workflows, validate the rules that matter, and turn the reusable pieces into a platform.
01 / Sports venue LINE booking
Handling competing booking channels
The venue must retain existing workflows while adding LINE. The engineering work covers time slots, buffers, conflict handling, approvals and exports.
Reusable: scheduling / resources / review statesRead full case ↗02 / Temple events and registration
Reducing repeated manual transcription
After people register in LINE, staff still handle payments, orders, event lists and documents. LIFF forms, order states and PDF output provide a repeatable workflow.
We are evaluating Claude API as an assistive layer for interpreting natural language requests, identifying missing details, and drafting answers for staff review.
01 / AI
Understand requests
Turn 'next Tuesday afternoon' into candidate date and time fields without altering bookings.
02 / AI
Structure intake
Extract service, date and contact requirements and ask for any missing information.
03 / AI
Draft responses
Prepare replies and notifications using confirmed business policies, with human review.
AI workflows are being designed and evaluated. Availability, pricing and order status must always be confirmed by business rules and authorized staff.
06 / HOW TO START
Start with one bottleneck. Build from what matters.
STEP 01
Map operations
How are bookings received today? Where does repeated work begin?
STEP 02
Define the rules
Review resources, schedules, approvals, notifications and existing integrations.
STEP 03
Pilot a narrow scope
Run, review and improve one workflow before expanding use.
Pricing is currently discussed per implementation; no standardized public subscription pricing has been announced. Availability depends on the current product stage.
LET'S TALK / ARZ AI
Bring the one task that keeps getting stuck.
Booking, registration, reconciliation or document work — let's talk about what your team repeats every day.
