Customers & vehicles CRM basics
- Pro
- Yes
- Elite
- Yes
- Ultra
- Yes
Phone, email, and visit history on the same record the estimate uses. History stays with the shop, not a sticky note.
On Pro. In-shop service history is this shop’s work — we do not sell a third-party vehicle report here.

Operate
1. Find or create the customer. One record for phone and email — the same one appointments and estimates use.
2. Attach the vehicle. Many vehicles under one customer without a user cap on founding Pro.
3. Open the RO from the same place. Estimates, appointments, and the board point at records that already know who owns the car.
Prior work this shop actually performed lives on the service-history story — pair that page. Do not import a third-party history product here.
Contrast
Customer info on the RO jacket. Vehicle details in a text thread. “Last time we saw them” is tribal knowledge.
Unlimited founding customer and vehicle records on Pro, tied to every RO. This-shop visit history stays this-shop — not a bought vehicle report.
Honest packaging
Unlimited founding customer and vehicle records on Pro means the counter can stop rationing logins or records to fit a tier chart. It does not mean we built a marketing automation cloud with journeys and segments on this URL.
Why it matters
Shop owners are used to being sold “vehicle history” as if a third-party report were the same thing as knowing what your shop did last time. ShopRally separates those ideas on purpose. Customers & vehicles is the CRM record: people, phones, emails, vehicles, and the ROs attached to them. In-shop service history — what you actually performed — is a paired story. A third-party report is not on this page, not on Pro, and not smuggled in as Ultra magic.
That honesty matters for founding shops who already distrust shop software that overclaims. Review campaigns live on the reviews packaging ladder. Two-way SMS lives on its own Elite page. This page stays Operate CRM basics.
When an advisor opens a vehicle, they should see the shop’s relationship — not a purchased dossier with logos we are forbidden to wave around. If you need prior this-shop work detail, follow the service-history pair. If you need to schedule, follow appointments. If you need to quote, follow estimates. Customers is the hub record those tools share.
Founding claim
We match the live founding claim: unlimited customer and vehicle records on Pro tied to ROs. We will not invent per-seat CRM pricing theater on this page. We will not claim a third-party data network. We will not show fake lifetime-value charts. The job is simpler and more valuable: one customer, many vehicles, every RO attached, history the shop owns.
Built by a shop owner means the CRM page should sound like the counter, not like a venture SaaS “lifecycle” deck. Customers call. They own more than one car. They come back. You need their number on the same screen as the RO — not in a different database you export on Fridays.
That is why unlimited founding records matter, and why third-party history does not belong here. Your differentiator is the work you performed, stored as this-shop history, paired honestly. Everything else is noise we refuse to print.
When the phone rings, the record should already know the vehicle. That is the whole customers page: unlimited founding CRM basics on Pro, this-shop history paired honestly, and no third-party report cosplay. Everything else can wait for the pages that own it — reviews for campaigns, two-way SMS for Elite threads, estimates for the ticket. We will not invent per-seat CRM pricing theater or fake lifetime-value charts on this URL.
Packaging
When the phone rings, the record should already know the vehicle. Unlimited founding CRM basics on Pro, this-shop history paired honestly, and no third-party report cosplay.
Launching Q4 2026 · no card · we'll invite you at launch
Built by a shop owner · Launching Q4 2026