CRM and follow-up for customization shops.
A set of wheels and a full build do not belong in the same queue. One should be answered in minutes, the other is a conversation that runs for weeks through parts, deposits, and updates. Most shops run both through one inbox and lose the slow one.
What a useful customization inquiry has to capture.
Enough to tell a fast accessory request apart from a project that needs a real conversation, on the first message.
Vehicle and current modifications
What it is and what has already been done to it. A previously modified car changes what fits, what has to come off, and what is honest to promise.
Services of interest
The work they are asking about, in the terms your shop uses. This is what decides whether the record takes the short path or the consultation path.
Reference images
The look they are chasing, attached to the record. It removes several rounds of describing the same thing in words.
Budget range where it helps
Optional, and only where it genuinely saves both sides time on a larger build. It is never used to filter people out silently.
Timeline and vehicle availability
When they want it and how long the vehicle can be with you. Build scheduling depends on that far more than on the order the inquiry arrived in.
Two paths, one pipeline.
The short path answers accessory and bolt on work quickly. The longer path carries a build through the steps your shop actually runs. Deposits, parts, and updates appear only where your process puts them.
Inquiry
One record with a source and an owner, sorted toward the accessory path or the consultation path from what the intake captured.
Accessory path
Straightforward work quoted and booked quickly, without dragging a simple request through a build process it does not need.
Consultation and scope
For larger projects, the conversation that turns a reference image into a scope, logged on the record with the files attached.
Deposit and parts ordering
Commitment, then parts ordered against the record so the wait is visible to the team and to the customer.
Build updates
Progress notes and the update cadence your shop is willing to keep. Nothing here promises a frequency you have not agreed to.
Delivery
The vehicle goes home, the record closes against its source, and the follow up agreed in scope goes out.
What gets installed.
One installation covering both paths, so a quick request is answered fast and a long project stops going quiet in week three.
The intake points agreed in scope
Website and landing page forms, the phone numbers you want tracked, and the message sources included in scope are connected so a new inquiry creates a record instead of living in whichever app it arrived in. Sources outside that scope are not claimed to be connected.
A pipeline that matches how you sell
Stages named after the real steps your business takes, so a glance tells you what is waiting on you and what is waiting on the customer. Stage names are set from your process, not from a template.
Assignment and routing
Every new record gets an owner. Routing rules are configured from the way your team already splits work, so nothing sits unclaimed while everyone assumes someone else picked it up.
The follow up agreed in scope
A first response, reminders on the records that go quiet, and the internal notifications your team needs. Automations are written to the sequence you approve. Anything requiring judgment stays with a person.
The system carries the path. Your team still runs the business.
What the installed system does
It catches every inquiry from the sources in scope, puts it in one place with an owner, starts the agreed first response, reminds someone when a record goes quiet, moves the work through named stages, and reports which sources turned into real jobs.
What your team still does
Your team handles the conversations and decisions that need judgment, confirms quotes and appointments, and keeps each record current. The system gives everyone the same context and makes the next handoff clear.
Verified automotive systems work.
Named with the client's approval. Both are verified Cross X Agency website and CRM engagements for automotive businesses. Neither is presented as a case study for the specific niche this page describes, and no result is claimed for either.
Lusso Auto Design
Cross X Agency built the website and the CRM behind it, and produces recurring content for the shop. Inquiries from the site reach a pipeline instead of sitting in a shared inbox, and the team works from one place.
Henderson, Nevada. Website and CRM, plus recurring content.
Undercover Customz
Website and CRM built by Cross X Agency. The same pattern as above: a site whose forms and calls are wired into a pipeline with stages, an owner per lead, and the follow up agreed in scope.
Henderson, Nevada. Website and CRM.
What it costs.
Setup is scoped to the work.
What it costs depends on how many lead sources, pipelines, and automations we connect, and how much of your current setup stays. You get the scope and the number in writing before anything starts.
After launch there is a monthly amount for Cross X OS software and lite management of the installed system. If Cross X Agency also runs the wider marketing and growth work around it, that retainer is quoted for the business and is not required to keep the system running.
Before you buy.
Stop losing the long projects.
Bring both kinds of inquiry you get. We will map how each one moves today, then show you where the installation changes the outcome.