The short answer
Give each advertising inquiry an office owner, preserve its source and original request, and check for earlier contact before responding. Keep the advertising record separate from qualification, appointment confirmation, and completed work. Reconcile the two records so an inquiry does not disappear between the agency, lead provider, and service office.
Where does the inquiry actually arrive?
Write down the specific source, destination, and owner. An ad might lead to your own website form, while another source may deliver a call or a platform message. Inspect the configured path rather than assuming every paid inquiry reaches the same inbox with the same information.
For Google Local Services Ads, follow the account's actual call or message workflow. Google documents those channels in its lead-management guidance. The separate LSA follow-up guide covers that platform context. This guide focuses on your office handoff across sources, not advertising setup or bidding.
Did the same person already call or submit a form?
Before starting another sequence, compare the contact details and requested work with the existing record. A homeowner might inquire through an ad and later call your main number. Treating those as unrelated requests can produce conflicting replies or competing appointment offers.
Preserve the original source reference and the relationship between records. Do not collapse two different jobs just because the customer email matches. If the connection is unclear, flag it for review rather than inventing attribution or silently discarding an inquiry.
Agree what the agency or provider hands to the office.
- Keep the original request, arrival time, source reference, and appropriate contact route.
- Identify the person who checks service area and requested work.
- Show any response already made, including a decline or opt-out.
- Name the office owner and the specific next action.
- Record whether the customer is waiting for an answer or the office is waiting for a detail.
A roofing estimate inquiry arrives through a campaign form. The agency notification and the form record refer to one request. The office assigns one owner, checks for a previous call, and asks only for the missing property detail. An afternoon preference remains a request until availability is confirmed.
This is an operating example, not evidence of ad performance or a claim that every platform exposes these fields. Agencies considering a referral relationship can review the CallBack Engine partner program.
A lead, an appointment, and a job are different outcomes.
Use distinct office definitions for inquiry received, qualified opportunity, appointment requested, appointment confirmed, and work completed. Keep unreachable, declined, and out-of-area inquiries visible under the appropriate outcome. A response attempt alone should not count as a booking.
Reconcile a defined set of source records against office records. Investigate missing entries and explain duplicates or internal tests. Do not change advertising conversion settings or upload customer data as a shortcut for this review. Attribution and account changes need their own authorized process.
What should you review before adding another source?
Check whether current inquiries have owners, useful first responses, and clear scheduling handoffs. Compare like-for-like periods and retain unanswered inquiries. This guide sets no cost, conversion, or response-time benchmark and does not establish whether a particular campaign is profitable.
CallBack Engine supports configured advertising or external leads within its managed lead-response scope. It does not manage ad spend, sell leads, or claim universal advertising integrations. Manual Scheduling is complete, and Google Calendar is optional when authorized and configured. See the roofing service workflow or discuss your actual source-to-office path.
The process recommendations here are CallBack Engine's operational guidance. Platform facts are limited to the linked Google documentation, reviewed October 8, 2026.