Configure appointment hours and timezone

Set bookable hours and timezone so customers see slots the team can actually honor Follow a safe workflow, verify the customer-facing result, and isolate common problems.

Set bookable hours and timezone so customers see slots the team can actually honor This guide keeps the work focused on appointment scheduling 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: Appointment configuration write access is required.

  • Confirm the business timezone and staffed hours.
  • Create at least one active store and service when required.
  • List closures or exceptions handled outside normal weekly hours.

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

  1. Confirm the scope and current state

    Open appointment scheduling settings and confirm whether hours are global or associated with a location or service in the current configuration.

    • 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.
  2. Prepare the change

    Choose the authoritative timezone first, then enter non-overlapping availability ranges that match real coverage.

    • 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.
  3. Save and allow required processing to finish

    Save settings and review duration, buffer, lead time, store association, and any active public fields that affect offered slots.

    • 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.
  4. Test the complete customer journey

    Request slots as a customer for several days, including a boundary near opening, closing, and a timezone transition if relevant.

    • 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 appointment scheduling separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

  • Displayed slots fall within staffed local hours.
  • The timezone label and confirmation time are consistent.
  • No overlapping or impossible ranges are accepted.
  • Unavailable periods do not appear to customers.

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

No slots are available

Check active stores, services, weekly hours, duration, lead time, buffers, existing appointments, and the requested date range. Correct the earliest constraint that removes all availability.

Slots appear at the wrong local time

Fix the configured timezone rather than shifting every hour manually. Retest both customer display and operator calendar after saving.

Related guides

Was this article helpful?