Validate call-conversion classification against real booking outcomes

Read the rule used in this account

Do not assume every call action uses only a fixed duration. Google documents newer recording-based AI qualification and fallback signals, while availability and account settings matter. Inspect the exact conversion action, call reporting, and any recording setting before interpreting the count. This guide does not authorize recording or establish its legal requirements; those need the business's appropriate privacy and legal review. The reporting task is to understand the rule already configured.

Source checks: About AI-qualified call leads · About call reporting

Define the business outcome separately

Write what counts as a useful service inquiry, what counts as a booking, and what counts as completed work. A call can be connected but unsuitable, qualified but not booked, or booked but later canceled. Existing-customer support and supplier calls may also be valuable without being acquisition leads. Staff should use a short disposition list that distinguishes these purposes instead of turning every received call into the same success category.

Review a restricted, representative sample

Compare the platform's classification with the available staff outcome records using appropriate access controls. Select a stated period rather than only memorable calls. Include short useful conversations, long unsuitable conversations, missed calls, and repeated attempts where observed. Use aggregate findings in the owner report, keeping personal details and recordings restricted. If recording is unavailable or inappropriate, use the permitted call metadata and staff notes rather than creating a workaround.

Evaluate duration as a proxy where it is used

A duration threshold can help filter interactions, but its business meaning depends on the service and phone process. A long hold queue may inflate time, while a simple booking can be quick. Do not choose a number solely because it produces a larger conversion total. Compare threshold behavior with actual outcomes and document why a selected proxy is reasonable for this operation. Keep proxy conversions labeled as such in the review.

Investigate disagreement instead of changing labels blindly

If the platform classifies a call as useful but staff record a wrong-service request, check whether definitions differ, data arrived late, or the classification lacks the business context. If staff record a booking on a call below a duration fallback, the business record still matters. Use the mismatch to improve goals or reporting appropriately. Do not alter staff outcome notes just to make them agree with a platform label.

Report the funnel without overstating sales

Show attempts or clicks where measured, connected calls, classified conversions, staff-qualified inquiries, bookings, and completed jobs as distinct counts. Explain unavailable stages and any reporting-definition change. At the next review, ask whether the selected signal tracks useful work more closely and whether call handling remains reliable. The result should help the owner choose a meaningful campaign signal while preserving an honest business outcome report.

Worked example: illustrative figures

For example, a duration-based action counts 12 calls as conversions. Staff records show 7 service-qualified inquiries and 4 bookings among those calls; a further short call below the duration threshold also produced a booking. The owner reports 12 proxy conversions, 7 qualified inquiries in that subset, and 5 total observed bookings across the reviewed sample. The counts are not added together. The example explains proxy disagreement and does not imply that this account uses Google's recording-based classification or that recording is appropriate.

Questions about this task