Skip to content
Cross X OS

Implementation story

Installing the automotive flow: two sales, one connected record

A custom shop runs two sales at once. The quick install needs a time slot. The build needs a consultation. Both start as a message about a vehicle, and both stall in the same places.

Find your setupSee pricing
Ferrari photographed for Lusso Auto Design
Lusso Auto Design · website and customer follow-up

The problem

The handoffs where the work goes quiet

Every one of these is a place a request changes hands without a record, an owner, or a next step.

Inquiry to vehicle

A message that says only "how much for tint?" cannot be answered. The year, make, model, and photos arrive later, in pieces, across channels.

Vehicle to path

Quick installs and custom builds get treated identically, so a booking-ready customer waits for a consultation and a build inquiry gets a price with no context.

Quote to decision

Quotes are sent from a phone and never followed. The shop finds out the answer only if the customer comes back on their own.

Build to referral

The car leaves, the photos go to social, and the record ends. No review request, no reactivation on the next stage of the build.

The connected flow

What the installation actually connects

One continuous path, in the order it runs.

  1. Calls, service-page forms, and social-driven visits all create one record with the source attached
  2. The intake captures vehicle details and photos before anyone replies with a number
  3. Quick installs move to a bookable time slot; builds move to a consultation with a named owner
  4. Quotes and deposits sit in a visible stage with reminders on the agreed cadence
  5. Status updates go out during the build so the shop is not answering the same question by DM
  6. Completed work triggers the review request, and past customers re-enter long follow-up

The automotive operating flow

Capture

Website, call, or social

Website, call, or social

One record is created with the channel and page attached.

Your team: Techs keep working. The inquiry is already captured.

View workflow details

  1. Website, call, or social

    Starts when: A call, a service-page form, or a visit driven from social creates the inquiry.

    Cross X OS: One record is created with the channel and page attached.

    Your team: Techs keep working. The inquiry is already captured.

  2. Vehicle, service, photos

    Starts when: The record enters intake.

    Cross X OS: Year, make, model, requested service, and any photos the customer sent land on the same record.

    Your team: Nobody asks for the vehicle three times.

  3. Quick install or custom build

    Starts when: The service type is known.

    Cross X OS: Quick installs route toward open time slots. Custom builds route toward a scoped consultation with a named advisor.

    Your team: The advisor talks scope, not logistics.

  4. Quote and deposit

    Starts when: The shop puts a number on the work.

    Cross X OS: The quote is tracked with a deposit stage, so an inquiry cannot be marked sold before both are recorded.

    Your team: Pricing, parts, and build decisions stay with the shop. Payment is taken where you take payments today.

  5. Scheduled work

    Starts when: The deposit is recorded.

    Cross X OS: The drop-off or install window is booked with confirmations and reminders.

    Your team: The front counter sees the calendar it already trusts.

  6. Status and handoff

    Starts when: The vehicle is in the shop.

    Cross X OS: The record carries the handoff and an agreed progress-update touchpoint.

    Your team: Customers stop calling to ask, and the tech is not the one answering.

  7. Review and reactivation

    Starts when: The build or install is complete.

    Cross X OS: A review request goes out on the agreed delay, past customers re-enter long follow-up, and the source stays on the ticket.

    Your team: The owner handles the relationship calls that matter.

Cross X OS does not replace your DMS, shop-management, parts, production, or accounting software. It owns the pre-sale conversation and the follow-up around them.

The boundary

What the system handles, and where people take over

The system handles

  • Capturing vehicle details and photos at intake
  • Routing the quick install away from the consultation path
  • Assigning a named owner
  • Quote and deposit reminders
  • Build status updates
  • Review requests and long reactivation

Your team takes over

  • Inspecting the vehicle and the panels
  • Specifying materials and finishes
  • Pricing custom fabrication and performance work
  • Deposits, change orders, and exceptions
  • Closing the build

Project work

What was built and connected

The work attached to each client and the part of the customer path it supports.

Lusso Auto Design

Custom automotive

  • Website and customer follow-up
  • CRM installed

Undercover Customz

Custom automotive

  • Website and customer follow-up
  • CRM installed

Named with permission. Scope only. No lead-volume, response-time, or revenue claims are attached.

Where to go next

Related paths

Back to all implementations

Automotive implementation questions

Does it replace shop-management or DMS software?

No. Cross X OS does not replace your DMS, shop-management, parts, production, or accounting software. It owns the pre-sale conversation and the follow-up around them.

Can it quote a wrap or a build?

No. Automation collects vehicle details, routes the inquiry, and keeps the follow-up moving. Pricing and specification stay with your team.

What does the installation cost?

Cross X OS is $497 per month with a 12-month commitment. Standard website implementation is included when scope fits; custom automotive workflows are quoted separately and can start at $7,500.

Plan the automotive setup

Cross X OS is $497 per month. We will confirm whether the standard implementation fits or this workflow needs a separate scope and quote.

Find your setupSee pricing