Autoankauf Zürich — Laravel Lead Management Dashboard

Autoankauf Zürich Admin is a Laravel and Filament dashboard for reviewing vehicle enquiries, tracking offers, and maintaining the content behind a Swiss car-buying website. I built the administration interface to bring lead follow-up and website editing into one workspace.

This case study focuses on the operational backend. The public website case study covers the customer-facing experience. The gallery here shows the local development interface; figures in those screenshots are not evidence of revenue, customer volume, or conversion improvements.

From vehicle enquiry to recorded outcome

A car-buying enquiry needs more context than a name and email address. The lead record brings together vehicle make, model, year, mileage, condition, contact details, postcode, preferred contact method, and acquisition-source fields. Offer and completed-sale amounts are recorded in Swiss francs.

Operators can search the lead table and filter by status, district, vehicle condition, source, and received date. Website, WhatsApp, and phone are supported source labels. These fields help separate enquiries that need a first response from those already being evaluated; they do not imply automatic WhatsApp messaging or automatic district assignment.

The implemented pipeline distinguishes new, contacted, offer sent, offer accepted, and won leads, alongside lost, rejected, and spam outcomes. A bulk action records first contact, while a CSV export provides selected records with German column headings for reporting outside the dashboard.

A dashboard built around follow-up

The overview surfaces today's enquiries, the open queue, average first-response time, and a recorded-outcome conversion rate. A lead-volume chart, status chart, recent-leads table, and quick-action shortcuts support daily triage.

The response-time widget uses contacted leads received within the last 30 days. The conversion widget calculates won leads as a share of won, lost, and rejected records received within 90 days. These definitions matter: the dashboard percentage is a pipeline measure, not the percentage of website visitors who submit a form.

The KPI and status widgets poll every 60 seconds. They provide a periodically refreshed operational view; this implementation does not establish continuously streamed analytics or a measured improvement in response times.

Content management alongside lead operations

The panel includes editors for service and location pages, FAQs, testimonials, blog posts and categories, static pages, hero slides, trust signals, and website settings. The gallery illustrates the blog editor, slide content and call-to-action controls, and settings interface.

Keeping these resources in the same panel gives operators a practical way to maintain the public site while handling enquiries. Review text, business promises, and statistics still need factual approval before publication; editable fields alone do not verify those claims.

AI chat and access boundaries

The chat service uses Prism to call OpenAI, with a configurable model and a default of gpt-4o-mini. It builds context from administrator-managed knowledge items and settings, stores conversation history, records escalation state, and provides fallback replies when the service is disabled or an upstream call fails.

This is a customer-support component, not an autonomous vehicle valuation or purchasing system. Model responses require appropriate oversight. The project includes Spatie permissions and super-admin, agent, and viewer roles; role names alone should not be read as a completed audit of every resource's permissions.

Implementation and evidence

The reviewed project uses PHP 8.4 requirements, Laravel 13, Filament 5, and Livewire 4, with Spatie packages for media and permissions. The dependency lockfile confirms the framework versions. The five screenshots document the dashboard, blog editor, login screen, hero-slide editor, and website settings. They demonstrate the interface without exposing a public admin account.

The available public domain shows the customer-facing website. Admin access is restricted; no public dashboard credentials are supplied here. This case study documents the implementation and its boundaries rather than claiming a security certification or audited commercial results.

Discuss a lead-management dashboard

If your team needs a Laravel admin panel, outline how enquiries arrive, who follows up, which status changes matter, and what reporting you need. Contact me to discuss that workflow, or compare other portfolio projects.