Case 02 / 06
LiveAutoPro
Redline
A European-car workshop in Puchong sells a diagnosis, not a generic service. The site had to lower the fear before the customer booked a diagnostic.
The job
Customers arrive with a noise and a worry. They do not know whether it is urgent, expensive or nothing. The site had to lower the fear before they booked a diagnostic.
The public site is in Malay because the customers are Malaysian owners of European cars. That is not a translation exercise; it is the register the customer is already using when the problem starts.
The move
Start with the sound. The customer records the noise, sends the car model and when it happens, and gets an early reply from a master tech on WhatsApp. A short form builds the message. The site explains the diagnostic and the no-find-no-fee promise.
The intake turns a vague noise into a message a master tech can answer. It does not pretend to diagnose the car online; it gets the right information to the person who can.
The public protocol
- 01 Describe the sound.
- 02 Add the car model and when it happens.
- 03 Send it on WhatsApp for an early reply.
The decision
- Keep the public site separate from the internal dashboard.
- Put the dashboard on Twenty CRM behind a Cloudflare Worker.
- Make sure the browser never receives the CRM key.
- Let the public page be a clear intake, not a fake customer portal.
The limit, stated plainly
The dashboard is an internal tool, not a customer portal. Prices are estimates. The workshop supplies the diagnostic expertise. The “500+ cars” and “4.9” rating on the live page are the client’s claims, not verified results.
- No customer portal or live repair tracking.
- No guarantee that a diagnosis is correct.
- No claim of new customers, revenue or rankings.
The evidence
Live site, public intake source, internal dashboard source, Worker proxy and Twenty CRM mapping. The boundary between the public page and the dashboard is the part worth inspecting.
See it live
Built with
A public intake page, a Cloudflare Worker, Twenty CRM and an internal dashboard. The API key stays server-side.
What the source shows
- The public intake form and WhatsApp handoff.
- The Worker proxy and Twenty mapping.
- The internal dashboard structure.
What it does not show
- Client data or dashboard records.
- Diagnosis accuracy or workshop results.
- Source excerpts without permission and redaction.
The rest of the work shows range: communication, learning design, voice and a joint creative direction.