docs
/
Courses — Appmint

Appmint Calendar and Appointments

Watch on YouTube ↗

Written guide

Overview

This course covers Appmint CRM Calendar. We will move between calendar views, filter the kind of activity shown and open the actual reservation, meeting or event behind an entry. We will also create a reservation and inspect a reschedule, so the calendar remains connected to the records that own the booking.

01. Choose a view and scope

Why this matters

CRM Calendar shows reservations, meetings and events. Post and reminder schedules belong to Schedule Management’s calendar instead.

Follow these steps

  1. Open CRM → Calendar. The heading is Calendar Management, with Calendars and Appointments beneath it. This is the standalone CRM module; it is separate from the Calendar tab inside Reservations.
  2. In Calendars, read the date heading first. Use Previous Month, Next Month and Today to move through the monthly grid.
  3. Select Month View to open the view menu. It offers Upcoming, Day View, Week View, Month View and Year View. Choose Week View when the time of day matters: days become columns with an hourly scale. The navigation buttons then refer to weeks.
  4. Choose All, Reservations, Meetings or Events to restrict the kinds shown. Select All when investigating an item you cannot find.
  5. Under People, click Anyone. The searchable picker identifies entries as staff or customer. Choose the relevant person rather than treating every result as an employee. Leaving the picker at Anyone avoids narrowing the calendar to one person.

Calendar Management in Month View with its separate Calendars and Appointments tabs

Week View provides day columns and time-of-day positions

The People picker distinguishes staff and customers

For a list of upcoming activity, select Appointments. Set the date range using Next 7 days, Next 30 days or Next year, then check the status selector (initially Any status) and search field. 0 items / Nothing coming up for this filter describes the current view; it does not prove the organization has no records at any other date or under another filter.

Appointments shows its date-range and status controls above the current empty result

Check the result

A calendar filter can hide a valid booking. Inspect selected users and kinds before creating another record.

02. Create through the actual booking flow

Why this matters

The calendar’s creation flow uses the Reservations booking wizard. It should preserve the selected date and enforce the same booking rules.

Follow these steps

  1. Select Add reservation in the Calendar toolbar. The current button is named Add reservation; there is no need to search for a generic “+ Item” menu.
  2. The New reservation drawer opens at Service. Read the available service’s title and duration before selecting it. In our training organization, Course tasting session is a thirty-minute service. The separate meeting section says that meetings are not a bookable service and exposes Book meeting; do not treat that as the same service booking.
  3. Select the intended service, then choose an available date/time in Time. In Details, search for the existing customer or enter the required customer information. Use Review Booking to inspect the complete service, customer and timezone together.
  4. For a real booking, select Confirm Reservation, wait for the save result and return to its date in the calendar. Open the entry and compare its identity and values with the saved reservation. The Reservations course shows the current time-selection and review screens in detail.

Add reservation opens the actual service-selection wizard from Calendar

This Calendar rehearsal opened and closed the wizard without saving a customer booking. It proves the navigation and handoff, not a completed booking or delivered invitation. Selecting a time is not confirmation; a new calendar entry requires the completed save.

Check the result

The current CalendarCreate source opens New reservation with ReservationBookingWizard. Do not invent a separate universal meeting/event creation drawer. Other kinds require their supported owning route.

03. Inspect the underlying record

Why this matters

An item on the calendar is a view of an actual reservation, meeting or event. Open its details before changing it.

Follow these steps

Select the item and inspect its identity, start/end time, location and meeting link where present. Compare the reservation’s detail in Reservations or the meeting’s owning view. Use the provided link to join only for the controlled test.

Check the result

Calendar rendering and successful joining are separate outcomes. A URL in a card does not prove a meeting provider works.

04. Reschedule or cancel

Why this matters

Reservation rescheduling should update the booking and its calendar position while retaining history. Cancellation also needs its relevant customer communication checked.

Follow these steps

Open the reservation detail and Reschedule. Select the intended new available slot, confirm and reopen the item at its new time. Use the cancel action on a disposable booking, then compare its status, old slot availability and controlled recipient notification.

Check the result

Current CalendarItemDetail uses ReservationReschedule. Do not drag a tile and claim a persisted change if that interaction is not exposed.

05. Resolve timezone and visibility questions

Why this matters

A displayed time belongs to a timezone context and a filtered view. Wrong-day appearances need that context checked before editing the booking itself.

Follow these steps

Open the item, compare its saved timezone and start/end with the calendar display and original reservation. Clear user/kind filters and refresh. Check the same record in the intended participant’s view after any correction.

Check the result

The local pass exercised Month and Week views, the People picker, Appointments and the Add reservation handoff. It used an empty training calendar; therefore record positioning, cross-user visibility, DST boundaries and notification delivery are still open checks. Do not use these empty-state captures as proof that a newly created booking appeared.

Next steps

Return to the chapter for the action you need. When you change the configuration, check the matching record, customer view or destination again. A saved setting and a successful external outcome are different observations.

Verification notes

BusinessMade Calendar — supporting guide

What this module does

Open Operations → Calendar to inspect appointments and manage a booking without losing its underlying reservation identity.

Locate your existing booking first

You need access to Operations → Calendar and an existing reservation or a configured service with available slots. Before creating a new booking, locate the customer’s current record in Reservations and note its date and identity. This helps distinguish a hidden calendar item from a missing booking.

In the historical Calendar view below, Today and the adjacent arrows change the displayed date, View changes the calendar layout, and Appointments opens the list-style view. An empty month grid does not mean every slot is available. User filters, item kinds and the selected month can all affect visibility.

BusinessMade calendar with date navigation, View, Item and Appointments controls

Personally inspected historical application screen. It shows the entry controls; current saved and downstream outcomes need separate evidence.

BusinessMade navigation and scope

BusinessMade /crm/calendar mounts the shared calendar. Its New reservation entry uses the shared ReservationBookingWizard. Operations → Reservations is a BusinessMade wrapper with its own service-floor context; verify the same reservation ID when moving between them. Timezone and notification outcomes require live verification.

01. Choose a view and scope

Why this matters

CRM Calendar shows reservations, meetings and events. Post and reminder schedules belong to Schedule Management’s calendar instead.

Follow the steps

Open Operations → Calendar. Use Calendars for Day, Week, Month or Year and Appointments for the upcoming list. Choose the relevant user and kind filter, then select the intended date.

Check the result

A calendar filter can hide a valid booking. Inspect selected users and kinds before creating another record.

02. Create through the actual booking flow

Why this matters

The calendar’s creation flow uses the Reservations booking wizard. It should preserve the selected date and enforce the same booking rules.

Follow the steps

Open the calendar’s + Item menu and choose the supported reservation entry. Select the service, slot and customer, review the confirmation and complete once. Return to the calendar and open the new item.

Check the result

The current CalendarCreate source opens New reservation with ReservationBookingWizard. Do not invent a separate universal meeting/event creation drawer. Other kinds require their supported owning route.

03. Inspect the underlying record

Why this matters

An item on the calendar is a view of an actual reservation, meeting or event. Open its details before changing it.

Follow the steps

Select the item and inspect its identity, start/end time, location and meeting link where present. Compare the reservation’s detail in Reservations or the meeting’s owning view. Use the provided link to join only for the controlled test.

Check the result

Calendar rendering and successful joining are separate outcomes. A URL in a card does not prove a meeting provider works.

04. Reschedule or cancel

Why this matters

Reservation rescheduling should update the booking and its calendar position while retaining history. Cancellation also needs its relevant customer communication checked.

Follow the steps

Open the reservation detail and Reschedule. Select the intended new available slot, confirm and reopen the item at its new time. Use the cancel action on a disposable booking, then compare its status, old slot availability and controlled recipient notification.

Check the result

Current CalendarItemDetail uses ReservationReschedule. Do not drag a tile and claim a persisted change if that interaction is not exposed.

05. Resolve timezone and visibility questions

Why this matters

A displayed time belongs to a timezone context and a filtered view. Wrong-day appearances need that context checked before editing the booking itself.

Follow the steps

Open the item, compare its saved timezone and start/end with the calendar display and original reservation. Clear user/kind filters and refresh. Check the same record in the intended participant’s view after any correction.

Check the result

No new calendar operation was executed in this pass. User visibility, DST boundaries and notification delivery remain explicit live checks.

Verification notes

BusinessMade /crm/calendar mounts the shared calendar. Its New reservation entry uses the shared ReservationBookingWizard. Operations → Reservations is a BusinessMade wrapper with its own service-floor context; verify the same reservation ID when moving between them. Timezone and notification outcomes require live verification.

Shared UI procedures are authored from the actual component mounted by the BusinessMade route registry. The changed wrapper/navigation has been source-inspected; new BusinessMade session, customer/provider outcomes and permission tests remain unperformed.

Check the booking after returning from the drawer

After completing the reservation wizard, the calendar reloads its timed data and closes the drawer. Find the new item on the chosen date, open it and compare its customer, service and start/end with the confirmation. If it is absent, inspect the filters and the underlying reservation before repeating creation. The retained empty-grid image is not proof of booking success.

For a changed booking, open its detail and use Reschedule; the shared reschedule flow checks the new slot. Reopen the same reservation after the success notice. Cancel opens a confirmation with Cancel booking; review that identity before confirming. Notifications and reminder delivery are separate external outcomes, not implied by the updated calendar position.