Repair website-call inquiry cohort
Follow distinct qualifying inquiries through recorded conversations, bookings and completed outcomes.
Use the interactive tool without signing up. It runs in your browser: enter your numbers, save a comparison, download results or print a working copy. Your numbers are not sent to BlueFinch.
Illustrative example inputs
These starting values show how the math works. They are not industry averages, customer results or a quote.
| Input | Example value |
|---|---|
Qualifying website-attributable inquiries One source rule, intake period and distinct inquiry definition. | 36 |
Inquiries with the defined conversation Not phone-button clicks or every repeated call. | 24 |
Inquiries with a recorded scheduled visit An actual scheduling record from this same group. | 15 |
Inquiries with the defined completed outcome Completed repair records by the selected observation date. | 12 |
Example results
| Measure | Result |
|---|---|
Recorded conversation share Conversations divided by qualifying inquiries. | 66.67% |
Scheduled share of conversations Recorded visits divided by the defined conversations. | 62.5% |
Completed share of scheduled inquiries Completed outcomes divided by recorded scheduled inquiries. | 80% |
Calculation detail
| Measure | Result |
|---|---|
| Inquiries without a recorded conversation | 12 |
| Conversations without a scheduled visit | 9 |
| Scheduled inquiries without a completed outcome | 3 |
Model assumptions
- Distinct inquiries stay in one nested group.
- Source linkage comes from actual approved records, not a click count.
- The observation date and completion definition are fixed.
- Pending visits are not assumed lost or completed.
Read alongside these results
- No call system, scheduler or repair-order integration is created.
- Observed associations establish neither profit nor website causality.
Download this worked example (CSV). Use the interactive version to export your own inputs and results.
Your website’s phone-button clicks and your advisor’s new appointments are two different numbers. They might describe different people. Define a group of website-attributable inquiries, then check the connection against your call records and scheduling reports. Without those links, the owner is comparing unrelated activity.
The tool above follows one call-origin inquiry cohort through an actual conversation, scheduled visit and completed work. Starting numbers are illustrative. Count each qualifying inquiry once, even when the person calls again. Keep spam, duplicate contacts and unverified sources outside the defined group rather than counting every phone event as a customer.
Use with this guide
Review website analysis scope
Separate technical findings from observed customer results.
Review estimate stage definitions
Keep each step tied to its actual source record.
Prepare the intake answer
Address a verified service question before adding sales copy.
Browse the complete auto repair guides and worksheets.
Write down what qualifies as a website call
Choose the attribution rule before reviewing results. A documented source reference in your authorized call system differs from an advisor’s unconfirmed guess. Define the observation period and how repeat calls connect to the original inquiry. Where source evidence is absent, label the source unknown. Do not move every unknown record into the website category to make the page look productive.
Google Analytics documents campaign parameters for links you control, including source, medium and campaign. Those labels describe referral activity. They do not independently verify a caller or repair order. Keep customer names, phone numbers and vehicle details out of public URL parameters. Connect operational outcomes only through the approved business records supporting the report.
Sources for this section: Google Analytics: Campaign source URL parameters
Define a conversation and a scheduled visit
A button click confirms no conversation. An answered call might be someone asking for directions or an update on work already in progress. Define the conversations included in this report and record the exclusions. Follow the inquiry identifier, not each attempt to dial, so a callback does not become another lead.
Count a scheduled visit when the appointment exists in your actual scheduling process. A request for a preferred date is not the same status. Count completed work under the stated repair-order rule and observation date. Preserve appointments waiting to occur outside the completed total. None of these counts establishes customer authorization for an unapproved repair.
Read the example as one nested inquiry group
The illustrative report has 36 qualifying website-attributable inquiries, 24 recorded conversations, 15 scheduled visits and 12 completed outcomes. Conversation coverage is about 66.67 percent of the original group. Scheduled visits are 62.5 percent of conversations. Completed outcomes are 80 percent of scheduled visits. Each percentage uses the stage named in its label.
The unresolved counts also matter: 12 inquiries without the defined conversation, nine conversations without a scheduled visit and three scheduled visits without a completed outcome. Those categories are recorded statuses, not assumed lost customers. The next action depends on the actual reason. A future appointment needs different handling from a wrong number or a declined service.
Review the missing step with the advisor
Look at the conversation-to-schedule records before reducing every advertised price. Did the shop offer the requested service? Was the vehicle eligible? Was an appropriate slot available? Record confirmed reasons separately from staff assumptions. Make one change supported by the records, then compare a later cohort using the same definitions and a fair observation period.
Assign unresolved inquiries using the owners, notes and record associations described in HubSpot’s task guidance, or equivalent fields in your existing system. The marketing report should let the advisor look up the correct business record. Keep the actual repair order and sensitive caller details in approved storage. Use internal codes in this public tool.
Sources for this section: HubSpot: Task owners, due dates and record associations
Investigate the page without claiming causality
BlueFinch’s website audit requires analysis setup and reports supported technical or content findings. An audit score is not a count of booked jobs. Compare the page’s visible service answer and contact route with the actual inquiry reasons. Test a working phone link on mobile, but do not report a successful link test as customer acquisition.
Download the cohort for your operational review and keep its attribution rule with the source records. With no qualifying calls, the relevant rates are unavailable. A later increase might accompany staffing, seasonality or source changes. Report the observed results and those limitations before crediting the website alone with the repair-shop outcome.
Sources for this section: BlueFinch: Website audit scope
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- Google Analytics: Campaign source URL parameters
- HubSpot: Task owners, due dates and record associations
- BlueFinch: Website audit scope
Use this page for general business information. It is not legal, tax, or accounting advice.