Preserve the inquiry’s origin, assign a location that can serve it and require the receiving team to accept ownership. Forwarding a message does not complete the handoff.
A person requests a service in Medellín through a Bogotá page. The inquiry reaches headquarters, gets forwarded and then sits unanswered because each team thinks the other owns it.
This hypothetical example illustrates a process that multi-location businesses can define before buying complex automation: who receives, accepts and closes each opportunity.
Separate origin from service destination
Record the originating page or channel, the city where the service is needed and the assigned branch as three distinct fields. Reassignment should not overwrite any of them.
Ask “In which city do you need the service?” when location determines coverage. Billing address or residence may differ from the work destination. Use accessible field labels and collect only information that helps route the case.
Define assignment rules before automation
The closest branch may lack the requested service, capacity or operating hours. Agree on decision rules and an exception owner.
- Which branch covers the requested area?
- Does it offer the requested service?
- Can a responsible team accept the inquiry?
- Who handles cases outside normal coverage?
- Who retains ownership until a reassignment is accepted?
Use a short, shared handoff record
A CRM or access-controlled register can hold the record. Use one inquiry ID and a history of status changes. Include receipt time, originating page, service city, need, assigned branch, owner, acceptance status and next action with an internal due time.
Keep contact details in the authorized customer-handling system. General reports do not need complete conversations or personal details. Record reassignment reasons and closure outcomes against the same ID.
Require explicit acceptance
“I sent it to the branch” describes the sender’s action, not the recipient’s ownership. A previous or central owner keeps following the case until the recipient confirms that it has enough context and accepts the next step.
For hypothetical inquiry C-104, Medellín accepts a request that arrived through Bogotá’s page. Its acceptance includes an owner and next action. Bogotá remains the origin, while Medellín becomes the servicing branch. Explain the handoff to the customer without making them repeat everything. Define an after-hours queue and realistic expectations.
Measure one opportunity through its stages
An inquiry transferred between branches remains one case. Keep origin and servicing branch separate so reporting can diagnose both acquisition and handling.
GA4’s recommended lead events require a verified implementation; renaming CRM columns does not create Analytics events. User-based lead reports need not equal inquiry counts because one person can submit multiple requests.
Do not send names, emails, phone numbers or free-text form contents in Analytics event parameters or URLs. Keep that information in the authorized commercial system.
Sources: Google: Recommended Google Analytics events · Google: Lead acquisition report · Google: Avoid sending personally identifiable information to Analytics
Test the exceptions as well as the happy path
Coordinate clearly labeled tests with the team or use a test environment. Verify the entire journey beyond the website confirmation. Start the operational review with unassigned inquiries and unaccepted handoffs.
- A branch-specific request reaches the right owner and retains its origin.
- An out-of-coverage request reaches an exception owner.
- After-hours requests remain visible to the next shift.
- Reassignment preserves context and one inquiry ID.
- Overdue acceptance triggers an internal review.
- A quote is not recorded as a completed sale.
REFERENCES
Sources and review
Source documentation consulted on October 5, 2026. Platforms and features may change; check the official source before implementation. The English adaptation retains the source review date of the original article.
- Labeling Controls: accessible form labels W3C WAI
- Recommended Google Analytics events Google
- Lead acquisition report Google
- Avoid sending personally identifiable information to Analytics Google
This guide provides general guidance. It does not guarantee search rankings or replace a review of your business, locations and data.