Manage, reschedule, and cancel appointments
Create and maintain appointment records while preserving accurate customer and operator expectations Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Create and maintain appointment records while preserving accurate customer and operator expectations This guide keeps the work focused on Appointments and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
Contacts brings customer identity and conversation context together. Appointments add schedulable work with availability, timezone, duration, and location settings. Accurate records and clear ownership help a team follow up consistently, while booking rules prevent customers from seeing times that the business cannot honor.
Before you begin
Access: Appointments read access is required. Creating, moving, updating status, or cancelling requires appointment write access.
- Confirm the customer, service, store, and timezone.
- Review current appointment status and existing notes.
- Follow the business notification and cancellation policy.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Open Appointments and use the calendar, agenda, filters, or search to find the exact record before taking action.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Review customer details, service, location, start and end time, timezone, status, and custom fields without changing the record yet.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
Use the available create, move, reschedule, status, or cancel action, confirm the new slot remains available, and save the smallest intended change.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Reload the appointment, verify calendar placement and status, and confirm that the customer-facing expectation or follow-up matches team policy.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in Appointments separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The correct appointment record changed once.
- Date, time, timezone, service, and location are consistent.
- Cancelled slots are not presented as active appointments.
- Operators and the customer have the intended next-step information.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
The desired replacement slot is unavailable
Check service duration, hours, buffers, lead time, store, existing bookings, and timezone. Do not force a time that the availability engine rejects.
The calendar time differs from the appointment detail
Compare display timezone and stored appointment timezone, then reload the view. Correct timezone configuration rather than manually offsetting the appointment.