How to coordinate appointments across salons or service locations

To coordinate several locations, each appointment needs an unambiguous place, available resources and a person responsible. A shared professional cannot appear free at two locations simultaneously. This guide organises those conflicts and appointment transfers, keeping operations, access and the identity of the entity providing and invoicing the service separate.

By Lyntev. Updated on .
About 5 minutes to read.

A request that stays connectedThe same reference follows the request and prevents duplicates.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Represent availability and travel by location
  • Transfer an appointment without losing conditions and confirmation
  • Distinguish calendar sharing from data and invoicing sharing

Define a location and who provides the service

Create a record for each location with its public name, address, support contacts, hours, services and own resources. Confirm whether all belong to the same entity or different entities exist. An application can show several calendars side by side without resolving multi-entity invoicing, contracts or data responsibilities. That distinction should be understood before centralising service.

Documentation for multi-company systems distinguishes shared and specific records. Use this distinction to formulate supplier questions without automatically importing another product’s configuration. Who can consult the customer at another location? Who can change the appointment? Which context is active when issuing a document? Record answers and limits. An establishment name at the top of the screen is insufficient evidence of isolation.

Reserve travel time as well as service time

In a fictitious scenario, a professional works at location A until 12:00 and needs forty minutes to reach B, including the planned transition. Her next appointment should not start before 12:40. The example is only a planning hypothesis; actual time should be defined with an appropriate margin for local conditions and working hours.

The block must affect every calendar where that person can be selected. If each location sees only its own events, a 12:15 booking at B may appear valid. Test the conflict in internal and public views. Increasing the last service’s duration to simulate travel can distort reports; prefer a block or availability rule identifying the operational reason.

Reserve travel time as well as service time
Fictitious intervalLocationProfessional’s state
11:00–12:00AConfirmed service
12:00–12:40Between A and BTravel and transition, no bookings
From 12:40BAvailability subject to other resources

Repeat the location when customers make decisions

Show the location during time selection, final review and confirmation. Include its address and how to request help without relying on an abbreviation only staff know. Where two locations have similar names, use a stable designation and municipality. Check that the directions link points to the selected location, not the business headquarters.

For customers alternating locations, do not automatically choose the last one without making it visible. A previous appointment at A does not mean the next service is available there. Also confirm price, duration and conditions that may legitimately vary between locations. Communicate differences before confirmation without making transfer an unexpected charge. Reception needs the same information as the customer.

Transfer as a confirmed change without leaving two reservations

Before transferring, check destination availability, the accepted professional, equivalent service and necessary resources. Obtain the customer’s agreement to the new location and any changed conditions. Preserve the link to the original appointment and administrative reason for the change. Do not erase history so staff can no longer understand who requested the transfer.

Define the sequence: provisionally reserve the destination, confirm details, release the source and send one updated communication. If the system has no dedicated operation, write a manual procedure with responsibility and a final check. A midway failure can leave two occupied places or none. The acceptance rule is one active appointment at the agreed location with the earlier one identified as transferred or cancelled according to the process.

Share only records needed for service

Central reception may need several locations’ hours without needing every professional note. Define roles and consultation purposes. A transfer between locations should not trigger informal record exports through personal messages. Extended access should be justified and known to the data controller, especially where locations belong to different entities.

Decide how to identify the same customer without merging different people. A family’s shared contact is not a universal key. Prepare a checking request where uncertain and separate permissions to consult from permissions to change. Minimisation and purpose principles help bound operations, but specific configuration needs the establishment’s assessment. Several locations in one account do not remove those responsibilities.

Test a conflicting transfer before activating sharing

Test an appointment at the wrong location, two simultaneous bookings for the same professional, travel between places and destination unavailability during transfer. Use fictitious customers with similar names and a reception role limited to one location. The test should reveal both time conflicts and inappropriate access without introducing real customer data into the demonstration.

Acceptance criteria: travel blocks incompatible times, the location appears in every confirmation, transfer leaves only one active reservation and the restricted role cannot consult information outside its scope. Check listings by location and professional; transfers must not duplicate counts. Where different entities exist, also request validation of the document and receipt-of-payment process before production use.

Record a common rule and local differences

The worksheet brings together what can be common and what needs selection per location. Review it when opening hours, an address or a shared team changes. The person approving changes should check the public journey and notices, because correcting only the internal calendar may leave customers travelling to the old place.

BeautyFlow IA allows managing several salons with a side-by-side view. Confirm in a demonstration how it represents shared professionals and the transfer process. That capability does not confirm every requirement of a group with several legal entities. For different operations, describe the rules first and request an assessment of what is included or needs adaptation, with clear scope and conditions.

Worksheet for your project

Coordination between locations worksheet
Location, address and public contact:
Service-providing entity and operational lead:
Specific services, resources and conditions:
Shared professionals and availability per location:
Approved travel time and block:
Location information on screens and messages:
Who may consult and change each location:
Transfer steps and customer agreement:
Source identifier and active appointment at the destination:
Handling of documents and receipt of payments:
Conflict cases, expected results and approval:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.