Multi-Branch Operations
Multi-Branch Customer Service: Who Owns the Enquiry?
Stop customer enquiries getting passed between branches. Explore five decisions that clarify ownership, transfers and follow-up for growing service businesses.
Reply.my Editorial Team
Practical guidance reviewed for clear implementation steps, responsible AI boundaries and honest claims. How we prepare our guides.
Three branches can see the message. None is sure who should answer.
The customer has asked whether an existing package can be used at another outlet. The original branch knows the purchase. The requested branch knows its availability. Head office may need to confirm the package terms.
Forwarding the message to all three does not settle the question. It can simply create three copies of unfinished work.
Multi-branch customer service needs a clear owner for each enquiry, even when several teams contribute to the answer. The owner keeps the customer informed and sees the request through; other employees can provide information without taking over the whole conversation.
This article looks at five decisions that help spa, beauty-centre and service-business teams avoid passing customers between outlets. The examples are fictional and illustrate business choices, not measured customer results or promises about a particular platform.
Decision 1: does this need a branch—or simply an answer?
Not every incoming question should immediately move to an outlet. A customer asking where you are located may need a clear list of locations, not a transfer.
First separate shared information from branch-specific work. General package descriptions may be common across the business, while service availability, opening hours and appointment options can differ by location.
For example, “Which branches offer this service?” should be answered using current information. “Can PJ fit me in at 4 pm?” requires an availability check for that branch.
Sending every message to the nearest outlet may be convenient internally but wrong for the customer. The nearest branch may not provide the requested service, and the customer may prefer an outlet near work rather than home.
A practical starting question is: “Which branch would be convenient for you?” Ask it when location affects the next step—not as an obstacle before answering a basic question.
Decision 2: who keeps ownership when another team must check?
Return to the customer asking to use a package at another outlet. The receiving employee may need information from head office, but that does not require the customer to contact head office themselves.
One person can remain responsible for the conversation while another checks the terms. The customer receives one clear update rather than several messages saying, “Please check with them.”
| Role | Responsibility in this example |
|---|---|
| Conversation owner | Explain what is being checked and return with an answer |
| Original branch | Provide the relevant purchase context through the appropriate internal process |
| Receiving branch | Check whether the requested service and timing can be offered |
| Authorised manager | Clarify any package exception or approval needed |
This is an illustrative division of work, not a rule that every chain must use. Your arrangement may differ. What matters is that asking a colleague for help does not leave the customer without an owner.
Avoid forwarding a whole conversation to everyone when a focused question would do. Share only the information the receiving employee needs, especially where messages contain sensitive details.
Decision 3: is the transfer actually accepted?
“Sent to PJ” describes an action by the first employee. It does not prove that the PJ team has picked up the request.
A transfer becomes useful when the receiving team can see what needs doing and accepts responsibility. Until then, decide who checks that the customer is not left waiting.
A concise handover could contain:
- The customer’s actual question.
- Their preferred branch and relevant timing.
- What has already been explained.
- What still needs checking.
- Any update that has been promised.
Consider this fictional note: “Customer wants to use their existing package at PJ on Saturday. Cross-branch terms not yet confirmed. Please check service availability; no appointment has been reserved.”
That is more actionable than “New lead, please follow up.” It also prevents an existing customer from being treated as a fresh sales opportunity.
If AI collects the initial details, staff should be able to review them rather than trust a summary blindly. Our AI lead qualification guide explains how to collect relevant context without making customers repeat a long questionnaire.
Decision 4: what happens when the preferred branch cannot help?
A branch can be the correct destination and still be unable to fulfil the request. The service may be unavailable, the desired appointment may be full or the employee with authority may be absent.
The next step should reflect the customer’s preference. Ask whether another time or outlet would work rather than silently moving the enquiry to whichever team is free.
For example: “PJ cannot offer the time you requested. Would you prefer that we check another day at PJ, or look at KL?” This offers a choice without implying that the alternative is already confirmed.
A different location can mean extra travel or an unsuitable schedule. A customer declining that option is not necessarily an unqualified lead.
If no team is available to respond, explain the actual staffed hours and leave a clear next action. Do not promise an immediate reply merely because a notification was sent. See after-hours customer service for the distinction between an automated acknowledgement and completed assistance.
Decision 5: when is the enquiry finished?
A read message, an internal transfer and a completed enquiry are three different things.
Agree what completion means for the request. A general question may be finished when the answer is provided. An appointment request still needs an availability response. A package exception may remain open until an authorised decision has been communicated.
Keep the customer-facing status accurate. Collecting a date does not confirm a booking, and sending a question to a manager does not approve an exception.
For beauty, wellness and healthcare businesses, treatment suitability and other professional judgements must remain with qualified people. Routing a question to the right person is different from answering it automatically.
Customers should not have to chase the business to discover that everyone considered their own part finished while the original question remained unanswered.
What should a branch manager review?
Start with the enquiries that crossed a team boundary this week, rather than counting all incoming messages.
- Which transfers were accepted, and which are still waiting?
- How often did the customer have to repeat the original question?
- Did two branches send overlapping replies?
- Were requests repeatedly sent to outlets that could not fulfil them?
- Did someone deliver the answer or update promised to the customer?
These observations help distinguish workload problems from routing problems. An employee may be responding quickly but receiving questions they cannot resolve. Another branch may appear quiet because its enquiries are being sent elsewhere.
Avoid treating a high transfer count as proof of poor performance. Some requests genuinely need another team. The useful question is whether the transfer moved the customer closer to an answer.
Where an omnichannel AI chatbot fits into the handover
Consider a new customer messaging through Instagram about a service. In a suitably configured flow, an AI assistant answers appropriate questions using approved information and asks which branch they prefer. The enquiry then reaches the appropriate team with those details, so staff can continue without starting again.
The same approach can be considered for enquiries arriving through other supported channels, such as Messenger or WhatsApp. This is an illustrative customer journey, not a claim that every connection or routing action is included in every plan.
Each part has a different job: AI helps with suitable opening questions; the omnichannel workspace brings supported conversations together; branch handover gives an employee responsibility for the next action. Staff still check availability, handle exceptions and confirm any appointment.
That is the distinction between buying a chatbot that replies and assessing a service that helps your team continue the enquiry. Ask Reply.my to explain how these parts would work for your branches, including what remains manual.
Customers should not have to coordinate your branches
If your team has enough people but customers still get passed around, adding another reply template is unlikely to settle ownership.
Reply.my’s published service packages include sales handover flows and multi-channel enquiry setup, with multiple-team routing and manager visibility listed in its broader offering. Confirm the precise scope, supported channels and access arrangements for your business rather than assuming every plan includes them.
Bring one anonymised example of an enquiry that moved between outlets. Discuss where responsibility became unclear and how the next customer could reach the appropriate team with less repetition.
You can also view plans and pricing before comparing the options.
Discuss My Branch Handover Gaps