Quick answer: Car dealership website maintenance must cover vehicle information, availability, approved trim and promotion details, test-drive enquiries and sales-lead delivery. A site can load normally while showing a sold car as available or claiming an enquiry was sent when no salesperson received it. Those are business-critical operating failures.
Buyers may arrive directly on a model page from search, an ad or social media. They inspect photographs and specifications, ask where a vehicle is located and enquire from a phone. Maintenance therefore needs to test the journey from that exact vehicle page to the correct sales owner, with evidence the team can verify. It goes beyond uptime, backups and WordPress updates.
Could the dealership site be missing enquiries?
Share a vehicle URL and your current lead-routing flow. IT Systems can identify what to test before defining a maintenance scope.
Why a dealership site needs more than a generic website check
A single model may have different trims, colors, production years, display locations and stock states. Published prices, offers, financing examples and conditions have separate business approvers and effective dates. A website technician should not invent a number or keep an expired banner because it still looks attractive. Content accuracy is part of the customer journey.
Customers commonly call, open Zalo, book a test drive or ask for a quote from mobile. These actions may rely on different components: a theme or Bricks element, form plugin, ad script, CRM, call service or external channel. A content or plugin update can break one connection without visibly breaking the page.
Nine recurring maintenance checks
- Inventory listing and filters: test model, vehicle type, trim, indicative price band and empty results; filters should not lead to the wrong car.
- Vehicle page: compare model name, year, specifications, photos, documents and contact action with business-approved source data.
- Availability: define how available, incoming, sold and pre-order vehicles appear, including branch-specific status.
- Price and campaign copy: record the approver, effective date and terms; remove expired offers on schedule rather than copying prices from another page.
- Test-drive and quote forms: select a model, trim, branch and preferred time on mobile; check validation and the submission response.
- Call and Zalo buttons: open them on a phone, confirm the current business destination and check they are not hidden by floating UI or cookie notices.
- Lead handoff: verify saved form entry, email, CRM and backup recipient; the model and source page should remain attached.
- Measurement: compare call clicks, form submits and thank-you events against the agreed conversion definition to avoid duplicate lead counts.
- Operational safety: check backups, editor access and controlled plugin/theme updates, then retest the commercial flows.
How to test a mobile test-drive request
Choose an active vehicle page and agree on a clearly marked TEST request with the sales team. As a logged-out mobile visitor, open the page, inspect the trim details, select the test-drive action, choose a branch and enter sample details that do not belong to a real customer. Record the time, URL, device, model, screen result and submission reference if available.
A salesperson then confirms that the lead reached the correct team with the model, branch, contact field and source page intact. Also try a missing required field, a double submit and a different branch. If email is the only record, document how to trace a message filtered as spam or lost through SMTP. Mark or remove the TEST lead under the dealership’s process so no one follows up with a fake buyer.
This tests the enquiry flow. It does not confirm that every displayed car is in stock or that a test-drive time has been booked. Sales staff must verify availability and scheduling with the customer.
When online vehicle information differs from reality
Identify the authoritative data source before editing: inventory system, an approved dealer file, CRM or manual content. Compare vehicle ID, trim, branch, status and last synchronization time. If several systems are involved, capture evidence from both sides. Editing a visible page without fixing its source may only last until the next sync overwrites it.
Pause or correct an expired price or offer only after the authorized business owner approves the replacement. Record affected URLs, timing, source and corrective action. If many pages are wrong, inspect the publishing or integration workflow instead of patching banners one by one.
Ownership at the failure point
| Issue | Decision owner | Website team checks |
|---|---|---|
| Available or sold vehicle | Inventory/sales manager | Source, rendered page and cache |
| Price or promotion | Authorized sales/marketing owner | Approved version, effective date, publication |
| Test-drive form misses sales | Sales sets fallback channel | Form, SMTP, logs, CRM handoff |
| Lead routed to wrong branch | Branch manager and CRM owner | Field values, routing rule and send evidence |
Customer data and CRM: define the boundary
Quote and test-drive requests contain contact details and purchase interests. Collect only the information needed, use the company’s approved data notice and restrict who can see enquiries. When a salesperson leaves, update routing and revoke access so forms do not keep delivering to a personal account.
The maintenance team can verify form submission, notification and the CRM handoff point. Lead scoring, regional assignment, two-way stock synchronization and a new sales dashboard are separate integration work unless included in the agreement. The website handover checklist helps document ownership of forms, SMTP, CRM, hosting and ad accounts.
What should a dealership maintenance report show?
A useful report lists vehicle pages compared with approved source data, forms tested, receiving branch, mobile call/Zalo actions, image or filter faults, backup state and items awaiting sales approval. Each issue should include the URL, screenshot, time, business impact, owner and outcome after repair. That gives management more than an unsupported statement that the website is “working normally.”
When ads are running, also check the destination page and conversion events. The landing page and tracking guide covers that workflow, but a tracked event does not replace confirmation that a real enquiry reached sales. Check frequency should follow inventory turnover, promotion cadence and agreed support scope. The website maintenance SLA guide explains how business impact affects incident priority.
When is an upgrade a separate project?
Maintenance of an existing handed-over setup covers controlled updates, backup, tests and agreed fixes. Building real-time stock, a new DMS/CRM integration, region-specific drive-away pricing, staff-calendar booking or personalized offers changes the product. It needs requirements, data rules, access, acceptance tests and a separate estimate. Calling that work “a small form tweak” hides important dependencies.
Frequently asked questions
Why test leads if the website loads?
Email, CRM, form and mobile-button failures can lose enquiries while the page remains accessible.
Should availability update automatically?
It can, when the stock source and sync rules are reliable. Test incorrect data, delays and behavior when the connection fails.
Can the maintenance team change vehicle prices?
Not independently. Prices, offers and conditions require an approved source and an authorized business owner.
Is a missing CRM lead a website or CRM fault?
Trace evidence at the send and receive boundary. The website team checks its form and handoff; the CRM owner checks receipt and routing inside that system.
Review the site before the next sales campaign
Tell IT Systems which vehicle pages matter, how stock and prices are updated, and where enquiries arrive. We can propose a focused maintenance checklist.
