Connect calls, forms and bookings in one customer workflow. Define sources, statuses, branch routing and measurement checks for a local business.
A local customer may call from a Google profile, submit a website form or book directly. When each route is tracked separately, the same person can be counted twice or the request can remain unowned. The purpose of tracking is more than channel reporting. It should show that the enquiry arrived, reached the right person and received an understood outcome.
Map every available entry route
List profile and website telephone numbers, forms, messaging channels, booking tools and records created in the branch. Record the receiving team and storage location for each route. A public channel that nobody regularly checks is an operational issue to solve before measurement.
Google's local-business-link guidance describes supported transaction links and links that may appear through providers. Inspect what customers actually see. An old booking provider or a destination pointing to the wrong branch needs correction before a source report can be useful.
Separate clicks, requests and completed appointments
A contact-button click can indicate intent; a request received by the business is a different record. Requested, confirmed and attended appointments are also separate stages. Combining everything under one conversion total conceals where the journey breaks.
Google profile performance defines the call metric through button clicks, while booking data depends on an applicable provider. Do not assume every business has the same reporting fields. Document what the platform counts and the limits of its relationship to operational records.
Build a sufficient initial record structure
A small business can establish clear tracking before adopting a complex CRM. Whatever tool is used, the following information should remain consistent.
| Field | Purpose | Check |
|---|---|---|
| Enquiry identifier | Follow the same request | A repeat message is not automatically a new prospect |
| Source | Understand the starting route | Separate known information from inference |
| Branch and service | Route to the correct owner | The request does not wait in a general inbox |
| Status | Show progress | Request, confirmation and attendance remain distinct |
| Next action and owner | Maintain follow-up | Every open record has responsibility |
| Outcome reason | Improve the process | Cancellations and unsuitable requests are separate |
Test cancellations and repeated contact
Imagine a customer submitting a form and then calling about the same need. That should not automatically become two new opportunities. Make the matching rule understandable to the team. Automatically combining similar names, however, can create a different error by merging separate people.
Preserve the relationship between the original booking and a rescheduled date. Cancellation, non-attendance and a time change initiated by the business are different outcomes. Distinguishing them reveals where customer communication or operations need attention.
Verify the setup through practical tests
Create a test request from each entry route and confirm the correct branch receives the appropriate notification. Keep test records out of actual performance reporting. Include the mobile form, telephone destination and booking-confirmation screen in the same review.
Report initial enquiries, suitable bookings, attendance and open records separately. Do not fill missing source details with guesses. Establish reliable customer follow-up first, then interpret channel contribution within the limits of the evidence.