Tracking / Repair / Warsaw, Poland / 2024
AutoPrime Service
Everything Worked.
Nothing Was Connected.
How a three-location auto service business rebuilt lead tracking, routing, and CRM discipline
March–October 2024 · 8 months · 3 locations
This is the project owner’s supplied record. Supporting exports and screenshots are not reproduced here and have not been independently audited for this publication.
Project facts
- Client
- AutoPrime Service
- Industry
- Automotive service and repair
- Location
- Warsaw, Poland
- Engagement
- March–October 2024
- Duration
- 8 months
- Locations
- 3
- Scope
- Lead-path audit, call tracking, CRM routing, conversion tracking, paid-media restructuring, response process, reporting
01 / Operating record
The business already had the tools
AutoPrime Service was not starting from zero.
The three-location automotive service business already had:
- a WordPress website;
- Google Ads;
- Bitrix24;
- two phone numbers;
- website forms;
- WhatsApp;
- Instagram;
- an established flow of customers.
On paper, the basic digital infrastructure existed.
Operationally, the pieces barely communicated with each other.
The owner could see that customers were arriving.
He could not reliably answer a much more useful question:
Where did they come from — and what happened to the ones we failed to reach?
The project started there.
02 / Operating record
The problem was not simply lost leads
Some leads were genuinely being lost.
Others were reaching the business but disappearing from measurement.
Both problems looked the same from the owner’s perspective: missing information.
Two website forms sent inquiries into a shared info@ mailbox that was checked inconsistently.
Managers sometimes discovered an inquiry only when the customer called again.
Phone calls were not tracked.
Calls arriving after 7 PM had no defined callback process and could disappear completely.
WhatsApp lived on the owner’s personal phone.
Two locations still used paper booking records at the front desk, creating recurring conflicts with appointments taken by phone.
Bitrix24 was technically installed, but only two of five managers used it consistently.
Paid campaigns were generating traffic, but conversion tracking was not configured. Campaigns were being evaluated primarily on clicks.
The business was therefore dealing with two different failures at once:
it was losing some inquiries, and it had no reliable way to measure the scale of the loss.
03 / Operating record
We mapped every path before changing the system
The first step was not a redesign.
It was a lead-path audit.
We mapped four primary entry channels across all three locations and documented what happened from the first customer action to the point where an appointment should appear in the operating system.
The audit covered:
- website forms;
- phone calls;
- WhatsApp;
- paid traffic;
- CRM entry;
- branch routing;
- response ownership.
The objective was to identify every point where an inquiry could:
- fail to reach the right person;
- reach the business but never reach the CRM;
- reach the CRM without a source;
- remain unhandled long enough to become commercially irrelevant.
That map became the basis for the rest of the project.
04 / Operating record
First, we gave the business visibility
Call tracking was added to both primary phone numbers.
UTM conventions were standardized across paid campaigns.
Website conversions were defined around actual actions rather than traffic alone:
- phone calls;
- form submissions;
- WhatsApp clicks.
This changed the advertising conversation.
Before, the business could see that people clicked.
Afterward, it could begin seeing which campaigns created observable customer actions.
That distinction made it possible to stop treating traffic volume as performance.
05 / Operating record
Then we removed email from the lead path
Website inquiries had been routed through a shared mailbox.
That was replaced.
Forms began creating records directly inside Bitrix24.
At the same time, the duty administrator received a Telegram notification.
The service category and source information could now travel with the inquiry rather than being reconstructed later.
Email stopped being the operational handoff point.
The new path became:
- website inquiry
- CRM record
- administrator notification
- response
instead of:
- website inquiry
- shared inbox
- somebody eventually notices
06 / Operating record
The CRM problem turned out to be a workflow problem
The first attempt to improve CRM discipline failed.
Managers were instructed to manually log every inquiry.
For roughly three weeks, compliance deteriorated until CRM entry was close to collapsing again.
The reason was straightforward.
The employees were running service desks and handling customers. The workflow had added administrative work without removing anything else.
The system was asking people to behave like data-entry staff during an operational shift.
That assumption was wrong.
We changed the process instead of blaming the users.
Required CRM fields were reduced from 11 to 4.
Website inquiries were created automatically.
Telegram became the immediate notification layer.
Two short CRM training sessions — approximately 40 minutes each — focused only on the fields and statuses the business actually needed.
CRM became the record of the work rather than an additional task competing with the work.
Within approximately a month, usage recovered.
That failure became one of the most useful lessons of the engagement:
A process that depends on perfect manual discipline is usually a process waiting to break.
07 / Operating record
Paid campaigns were rebuilt around services
Before restructuring, campaigns largely sent users to the homepage.
That forced someone searching for a specific service to:
- click an advertisement;
- land on a general page;
- find the relevant service independently;
- decide how to contact the correct location.
Campaign structure was rebuilt around actual service intent.
The seasonal tire-service campaign received its own landing page.
Three campaigns with no tracked conversions were turned off.
The advertising freelancer continued managing the campaigns after the restructuring; the project lead’s role was the measurement architecture, campaign structure, conversion framework, and operating logic rather than ongoing day-to-day media buying.
This distinction matters because the resulting media performance was shared work, not a claim that one person independently ran the entire advertising program.
08 / Operating record
Response expectations became explicit
The new operating target for website inquiries was:
15 minutes or less during business hours.
Outside business hours:
response by 10:00 AM the following day.
The target and the measured result should not be confused.
By month seven, measured response time for website inquiries had improved from approximately:
26 hours → under 1 hour
The system did not prove that every inquiry received a response within 15 minutes.
The 15-minute number was the operating SLA.
The under-one-hour figure was the observed result.
09 / Operating record
The numbers changed — but they need to be interpreted correctly
Monthly inquiries, all tracked channels
~140
~210
Leads with a known source
~25%
~85%
Website inquiry response time
~26 hours
<1 hour
Tire-service campaign CPL
Not reliably tracked; reconstructed estimate ~€18
€11 tracked
Advertising-origin appointments
Unknown
61/month tracked
The increase from approximately 140 to 210 monthly inquiries should not be interpreted as 50% demand growth created by the project.
Part of that increase came from better capture.
Inquiries that previously disappeared between phone calls, forms, personal devices, and manual processes began appearing in the system.
That is an important distinction.
The project improved both:
- visibility into existing demand;
- the operating system used to process that demand.
It did not isolate how much of the higher recorded volume represented genuinely new demand.
10 / Operating record
What is strongly supported
Three changes are directly supported by operational data.
Source visibility
Known-source leads increased from approximately:
25% → 85%
Source data came from CRM exports and call-tracking logs.
Response speed
Measured website-inquiry response improved from approximately:
26 hours → under one hour
Paid campaign measurement
The tire-service campaign reached a tracked CPL of:
€11
and the paid system recorded:
61 advertising-origin appointments per month
in the measured period.
These figures come from the advertising platform and the connected tracking setup.
11 / Operating record
What we do not claim
There are three important limits.
Historical CPL was reconstructed
The pre-project tire-service CPL of approximately €18 is an estimate reconstructed from historical click and spend data.
It was not measured under the same conversion-tracking system.
It should therefore remain clearly labeled as an estimate.
Higher recorded inquiry volume is partly a measurement effect
The move from approximately 140 to 210 monthly inquiries includes better capture of contacts that previously went unrecorded.
It should not be presented as pure acquisition growth.
Revenue growth is not an agency result
The owner reported approximately 20% year-over-year revenue growth during the broader period.
We did not have access to the underlying financial reporting and cannot isolate the project’s contribution.
For that reason, the figure is not used as a project outcome.
12 / Operating record
What changed structurally
Before the project, the business had several tools.
After the project, it had a lead-handling system.
The difference was not another software subscription.
It was the connection between the existing pieces:
- traffic
- tracked action
- CRM
- branch ownership
- response
- status
- reporting
Weekly reporting then showed:
- inquiries by source;
- response time;
- CRM capture rate;
- tracked paid performance.
That gave management something it did not have before:
a repeatable way to see where inquiries came from and where the process was failing.
13 / Operating record
The most important change was not more advertising
No large increase in media budget was required to solve the original problem.
The business first needed to stop wasting demand it was already receiving.
That meant:
- measuring calls;
- routing forms correctly;
- reducing unnecessary CRM friction;
- clarifying response ownership;
- connecting paid media to actual conversion events.
Only after those pieces were visible could acquisition performance be evaluated honestly.
14 / Operating record
Evidence available
The project can be supported with:
- paid-media screenshots before and after restructuring;
- monthly CRM exports;
- call-tracking dashboard data;
- historical website captures;
- the tire-service landing page;
- 24 weekly reporting sheets;
- written communication documenting response expectations.
Any customer-identifying information must be removed from screenshots before publication.
The existing video testimonial should not be published unless separate permission is confirmed.
15 / Operating record
The takeaway
AutoPrime did not need another disconnected marketing tool.
It needed the tools it already had to behave like one system.
The central lesson was simple:
Before buying more demand, make sure the demand you already have can be seen, routed, answered, and measured.
For this business, better tracking did more than improve reporting.
It exposed where customers were being lost — and made those losses operationally fixable.