Our work · App & software

Digicars Interceptor

All our work
Digicars Interceptor lead-routing dashboard: entries and failed-delivery screens

One endpoint between every lead source and every dealership

Digicars Group sells several car brands across a network of dealerships, and its leads arrive from everywhere: social lead forms, classifieds portals, brand websites built by several agencies, QR campaigns, paid media and manual capture. Before the Interceptor, each source was wired into the group’s systems on its own terms.

The group needed three things. Separate lead sources from operational systems. Standardise how leads are delivered. And be free to change a system at any dealership without asking every supplier to re-integrate.

The Interceptor is part of the wider Digicars Group solution, alongside the dealership website platform and the Nero Studio accessories site, but it’s built and run as its own system.

The Interceptor in production
100,000+
leads received and routedAcross the group’s dealerships and channels.
30+
authenticated integration partnersAgencies, website builders, lead portals and internal parsers.
800+
incoming field names mappedMapped in a dashboard, without code changes.

What it does with every lead

Each supplier authenticates with its own key pair and sends leads in whatever format it already has: JSON, form posts, query strings, nested objects or formatted emails. The Interceptor stores the untouched request first, so nothing can be lost to a later failure. It then flattens and maps the fields, resolves the source per dealership and channel, normalises South African phone numbers and delivers the lead in real time.

Delivery is configured per dealership: the group’s CRM, a contact centre with mandatory reporting fields, or both. Campaign and vehicle are read from a structured ad naming convention, and anything that can’t be resolved is labelled “Unknown” so reports keep working.

Built so the business can change without us

New field names are discovered automatically and mapped by an operator in the dashboard. A new agency or a new lead-form question goes live without a deploy. Suppliers get published integration guides and a test mode that runs a lead through the whole pipeline without delivering it, so they can onboard themselves.

Because suppliers only ever talk to the Interceptor, a dealership can move to a different downstream system as a configuration and mapping change. Every agency, portal and form keeps sending to the same endpoint.

An operations dashboard, not a black box

  • Search any lead by cell number or email, with formatting ignored and a one-click JSON support bundle.
  • Raw request log, including requests that never became leads, so a supplier’s claim can always be checked.
  • Failed-delivery queue with the HTTP response for every rejection and single, selected or bulk resend.
  • Exports by dealership or partner, a clean contact list and an authenticated CSV endpoint for BI tools.
  • Safe testing with supplier test mode, mirror delivery to a staging CRM and sandboxed contact-centre accounts.

The stack behind it

Deliberately plain technology, chosen so the system is fast to change and easy to support: small single-purpose modules, a document store that needs no database server, and workers that are safe to run as often as needed.

How the Interceptor is built
  1. 01

    Channel connectors

    Pull and push intake from every lead source, each with its own adapter.

    • API pollerspaged, with request budgets
    • Webhook receiversverified, with replay tools
    • OAuth and JWTplatform and DMS auth
    • Email and form adaptersreshape any payload
  2. 02 · Core

    Routing core

    A short chain of single-purpose stages, from authentication to delivery.

    • PHP 8web endpoint and CLI workers
    • Key-pair authper integration partner
    • SleekDBJSON document store, timed queries
    • cURL deliveryCRM and contact centre
  3. 03

    Operations

    What the team uses every day to find, fix and report on leads.

    • Bootstrap 5 + DataTablesfast with 100,000+ records
    • Resend queuesingle, selected or bulk
    • OpenSpout and PhpSpreadsheetstreamed XLSX and CSV
    • Export APIauthenticated CSV for BI
  • Store first then process
  • No deploy to add a field
  • Every payload resendable
  • Safe to run as often as needed

See how we build lead routing for other dealer groups or return to the Digicars Group platform.

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk