Luma · Case studyDemo build · fictional business, simulated data

Every service enquiry gets an owner.

A lead follow-up workflow for service businesses: capture from forms, calls, and WhatsApp into one inbox — with AI reply drafts, owner approval, and an audit trail.

React + TypeScriptAI reply draftsApproval workflowRoles & audit trailFollow-up tasks

Live demos are password-gated — request access via the contact page and the password comes back in minutes.

Team mapping a service workflow on a board
Demo business: Apex Home Services (fictional)
The problem

Service teams lose enquiries across forms, calls, email, WhatsApp, and manual follow-up — nobody owns the next action.

What was built

Luma: lead capture into a shared inbox, AI-drafted replies behind owner approval, user roles, follow-up tasks, and an audit trail the owner can inspect.

The demo shows
  • One inbox for every enquiry source, with owners and statuses
  • AI reply drafts that wait for human approval before anything sends
  • A 60-second walkthrough video of the full flow

The challenge

A service business hears from customers everywhere at once — website forms, phone calls, WhatsApp — and every channel has its own half-followed process. Enquiries stall in personal inboxes, follow-ups depend on memory, and the owner can't see which lead is waiting on whom.

The failure isn't a missing tool; it's missing ownership. Any system had to make the next action and its owner visible at a glance — and keep AI helpful without letting it message customers unsupervised.

The solution — three decisions

01

One inbox, whatever the source

Forms, calls, and WhatsApp all land in the same prioritized queue with source, value, and status — so triage happens in one place instead of three apps.

02

AI drafts, humans send

Replies are drafted by AI but wait behind owner approval. Speed without the risk of an unsupervised message reaching a customer.

03

An audit trail the owner can read

Every action on every lead is logged — who did what, when, and what happens next — which turns 'did anyone follow up?' into a lookup, not an investigation.

Product tour

Luma lead inbox with detail panelLuma lead inbox with detail panel
The lead inbox: search and filters left; the selected lead's contact, source, value, and next action right.

What the demo shows

  • Lead capture from multiple sources into one prioritized inbox
  • AI-drafted replies with owner approval before send
  • Follow-up tasks with due dates and clear ownership
  • Role-based views for owner, admin, and staff
  • An audit trail of every action on every lead

Under the hood

  • React + TypeScript front end with role-based views
  • AI drafting behind an explicit approval gate
  • Typed lead lifecycle with statuses, sources, and estimated values
  • Follow-up tasks and audit log modeled as first-class records
Built as a demonstration — on purpose

Apex Home Services is fictional and labeled as a demo on every screen. Nothing here is presented as client work: no client names, no outcome metrics, no testimonials. The proof is the running product — open the live demo above and check every claim.

Next step

Build something like this.

Fixed scope in writing before any money moves, demos during the build, and full code ownership at handover.

1%