APPOINTMENTS CONNECTED TO WORK
From an offered time to a clear customer appointment.
Combine service-duration availability, opening rules, customer context, confirmation and calendar visibility in one supported booking workflow.
Booking should become a workable promise, not another isolated list
A customer chooses a time, but the business must also know the service duration, preparation needs, customer identity and current appointment state. Tsumira booking brings those pieces together. Supported public and staff-assisted creation use the same core booking path, with availability checked again before the promise is stored. The resulting appointment can connect to CRM, confirmation communication and the business calendar.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Booking availability
Calculate bookable starts from service duration, opening windows, occupied time and the configured lead time and booking horizon.
Opening hours and exceptions
Define the normal week, override a specific date and choose whether the business trades on the built-in Japanese public holidays.
Confirmation and self-service
Prepare confirmation communication and an appointment-specific management link, with defined cancellation and replacement limits.
Booking customer context
Carry customer details and a CRM contact association with the booking, so the next visit can start from recognizable customer context.
Appointments in the calendar
Bring active appointments into the supported calendar view with customer, service and start/end context, then open the booking for authorized changes.
Overlapping booking protection
Recheck availability when writing the appointment and enforce non-overlap for active bookings of the same resource.
Offer times from the real operating rules
Service duration, weekly opening windows, date exceptions, occupied time, lead hours and the future horizon determine the slots offered. A particular date can replace the normal week when the business closes for maintenance or deliberately opens a special interval. Built-in automatic public-holiday handling is Japanese. An international operation needs to evaluate and configure its actual local closures rather than assuming every country’s calendar is included.
- Duration-based slot calculation
- Weekly rules and date exceptions
- Explicit holiday and booking limits
Keep the appointment connected to the customer
The booking records customer name, contact details and notes, with a supported CRM contact association. Active bookings contribute timed intervals to the calendar and can show customer and service context. Confirmation communication uses the configured worker and transport; a recorded appointment and a delivered email are separate outcomes. Customer self-service uses an appointment-specific link, currently with a 24-hour change cutoff before the start.
- Appointment and customer association
- Active booking calendar contribution
- Confirmation and private management link
Handle change and competition as part of the promise
Concurrent choices do not all become confirmations simply because visitors saw an earlier free slot. The write path checks current availability, and active intervals for the same resource are protected against overlap. Cancellation records a changed promise instead of erasing the customer. Rescheduling attempts the replacement before cancelling the original, leaving the old promise standing if the new slot is unavailable. Read the actual result before communicating that a change succeeded.
- Current-state booking checks
- Resource-specific interval protection
- Cancellation and replacement lifecycle
A concrete workflow
Prepare the service and hours
Configure duration, public availability and supported booking rules.
Receive the appointment
Let the customer or authorized staff select an offered time and provide the necessary details.
Confirm and connect
Store the valid booking, associate customer context and process the configured communication.
Manage the actual promise
Use the calendar and booking record to prepare, cancel or replace through the appropriate supported action.
An illustrative working example
Illustrative workflow: a service consultation
A business defines a consultation’s duration and opening schedule. A customer selects an offered time and provides contact details. The final path checks the interval and stores the appointment with customer context. Staff see the active booking in the calendar and prepare from its note. If the customer later requests a replacement within the allowed window, the new promise is checked before the old one is cancelled.
Questions about this topic
Does booking work independently of CRM and services?
The current booking module declares CRM and services as dependencies. Availability uses service duration and the creation path carries customer context.
Are confirmations guaranteed to arrive instantly?
No. Delivery depends on configured background processing, mail transport and recipient outcome. Read the actual booking and delivery states.
Can customers change the appointment without a login?
The supported private management link handles that appointment’s cancellation or replacement, currently before the 24-hour cutoff.
What should an international business verify?
Review timezone and service setup, local closures versus the Japanese holiday data, notification configuration and the actual customer-management rules.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Calendly
Workflow concept: Plan migration of services, opening windows and customer booking expectations.
Google Calendar
Workflow concept: Review appointments alongside work planning without promising bidirectional synchronization.
Gmail
Workflow concept: Prepare customer confirmations with checked timing, recipients and follow-up information.