BOOKING & DAILY PLANNING
See the customer appointment with the time it actually occupies.
Bring active appointments into the supported calendar view with customer, service and start/end context, then open the booking for authorized changes.
Open the source record
The appointment list and the day should tell the same story
A booked service occupies an interval, not an abstract deadline. Tsumira contributes active customer appointments to the business calendar with both their start and end. The entry can show customer and service context and link back to the booking record. Staff can plan the day from that view, while the booking remains the authoritative place to inspect its state and perform the supported changes.
Represent the promised interval
The calendar contribution uses the actual appointment start and end rather than inventing a generic calendar duration. Its label can combine the customer’s name with the service when that information is available. The result answers practical questions: who is expected, for what and during which interval? Read the booking’s own details if the note, location or lifecycle matters to the next decision instead of assuming the short calendar label contains everything.
- Actual start and end
- Customer and service label
- Link to the booking record
Keep current commitments distinct from cancelled ones
Cancelled appointments leave the active calendar contribution because the customer is no longer expected at that time. The appointment itself remains a record of a promise and its later cancellation. A replacement booking creates a new current promise while the old one is cancelled through its proper flow. This avoids treating a historical cancelled record as work the front desk should still prepare for.
- Active appointment contribution
- Cancelled promise retained as history
- Replacement follows its own lifecycle
Retained in appointment history
Retained in appointment history
Plan with other sources without changing the booking
The host calendar can show supported internal events and business dates alongside bookings, according to the selected sources and viewer’s rights. This helps preparation but does not merge all workflows into one editable object. Selecting a calendar category or reading an appointment is not an instruction to reschedule it. Open the source booking and use the permitted appointment action, which checks the current state and availability where relevant.
- Bookings beside supported work sources
- Calendar filters for the planning question
- Authorized changes at the source
A concrete workflow
Confirm the appointment
Create the customer booking through the supported availability and confirmation path.
Inspect the relevant day
Show customer appointments in the appropriate calendar period and read their occupied intervals.
Open the booking context
Review service, customer, note and current state where more detail is needed.
Update through the right action
Use the permitted cancellation or replacement path and then verify the calendar reflects the current promise.
An illustrative working example
Illustrative workflow: prepare an afternoon of consultations
A front-desk colleague opens the day’s calendar and sees active consultations with customer and service labels. The intervals help the team prepare rooms and avoid confusing a longer session with a short call. One old appointment has been cancelled and no longer appears as an active commitment. The colleague opens a booking’s record to check its note before making any authorized adjustment.
Questions about this topic
Does the calendar know how long an appointment lasts?
The booking contribution carries both the actual start and end, representing the promised interval rather than a point-only deadline.
Why does a cancelled booking leave the calendar?
Nobody is expected at that appointment anymore. The cancelled booking record remains, but it is excluded from the active calendar contribution.
Can I treat a calendar filter as a booking change?
No. Filters select the displayed sources. Changes to the appointment require the appropriate action on its source record.
Is this automatic two-way synchronization with every external calendar?
No such integration follows from this function. It describes the internal calendar contribution; external ICS reading is a separate subscription feature.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
