Case study · Web platform · Back office

Four lead forms, three messaging apps, one console. Every web enquiry now has a reference.

Bazaar is a platform for buying, selling, sourcing and importing used cars, with a 121-brand catalogue and four lead forms. We built the public site and the staff console behind it: one shared inbox for Instagram, Messenger and WhatsApp, a lead queue on a reply clock, inventory, a viewing diary and an AI assistant that works in three languages.

The Bazaar homepage: a dark showroom photograph behind the headline, a navigation bar with Buy, Sell, Source and Import and a WhatsApp button, and a search panel with make, model and variant fields, popular searches for Corolla, Civic, Prado and Hybrid, and an advanced filters toggle.

The brief

Bazaar offers four services: buy, sell, source and import. The build had to carry all four on one public website, and give the staff somewhere to work what came in.

  • A catalogue a buyer can search Buyers had to be able to search a catalogue of 121 brands for the car they had in mind, or browse it by body type, brand and budget.
  • Every web enquiry on record The website takes four kinds of lead: sell, source, import and enquire. Each had to arrive recorded with a reference. Before, none were.
  • Messages as well as forms Customers also write in on Instagram, Messenger and WhatsApp, and those messages had to be answered alongside the leads from the website.

However a customer got in touch, the staff had to be able to answer from one place.

What we built

A public platform for the four services, and the staff console that every lead and every message lands in.

  1. Catalogue and searchA 121-brand catalogue searchable by make, model and variant, with quick picks for popular searches and advanced filters for body type, price range, mileage, engine capacity, engine type (petrol, hybrid, diesel, electric), colour and registration city.
  2. Four lead forms, one queueSell, source, import and enquire each have their own form. All four feed the same lead queue in the console, and every lead in it sits on a reply clock.
  3. Shared inboxInstagram, Messenger and WhatsApp messages arrive in one shared inbox inside the console, and are answered from there.
  4. Inventory, viewing diary and AI assistantThe console also carries the inventory and a diary for viewings, so stock and appointments sit next to the leads and the messages, and an AI assistant that works in three languages.

What changed

  • A web enquiry arrives as a record Each submission from the site lands in the console under its own reference, in the same queue as every other lead.
  • The form a lead came through doesn't change who picks it up A seller, a sourcing request, an import request and a general enquiry are all worked from one queue, on one reply clock.
  • The app a customer uses doesn't change where they are answered A message on Instagram, Messenger or WhatsApp is answered from the same inbox as the other two, inside the same console as the lead queue.
The results

The numbers, and what they replaced.

None →100%
Web enquiries recorded

Every enquiry from the website is now recorded with a reference; before, none were.

100%
DMs in one inbox

All Instagram, Messenger and WhatsApp messages are answered from one shared inbox.

4 → 1
Lead forms into one queue

Four lead forms (sell, source, import and enquire) feed a single queue with a reply clock.

The stack
Next.jsReactSupabaseCloudflare WorkersChatwoot

Enquiries coming in on your website and on every messaging app, and no one place to answer them from?