← BACK TO ALL WORK{ KAIZEN LABS } CASE STUDY
Manufacturing● PAID PILOT

An AI front desk that runs the gate

CLIENT: Manufacturing client, Pune. Named on request

A multilingual workplace entry system handling visitors, deliveries, pre-approved entries and host approvals from a kiosk, with a separate admin portal behind it.

Aagman admin portal showing the visitor book: filters for scenario and date range, and a table of visits with scenario, status, language, kiosk and time. Visitor names are blurred.
// overview

The gate register is the last paper system in an otherwise digitised plant. A visitor arrives, writes a name nobody can read, and waits while somebody walks the floor looking for their host. Deliveries and contractors go in the same book. Nothing is searchable afterwards, and when an auditor asks who was on site on a given morning, the answer is a photograph of a page.

Aagman puts a kiosk at the entry point and an authenticated portal behind it. The visitor checks in by voice, touch or QR; the host is asked to approve on WhatsApp, by email or in the portal, and the visitor waits only for that. Deliveries, vendors and pre-approved guests each follow their own path rather than being squeezed through the visitor flow. Everything lands in a searchable, exportable record with sites, users and roles around it. It runs live at a manufacturing plant today.

// specs
Kiosk speaks
English, Hindi, Marathi
Kiosk understands
20+ spoken languages as input, accent-tolerant, low latency
Check-in modes
Voice, touch, QR, pre-approved entry
Workflows
Visitor, delivery, vendor, pre-approved
Host approval
WhatsApp, email, or in-portal
Deployment
Cloud application; the kiosk is a thin client
// what it does
01

Kiosk check-in by voice or touch, plus QR check-in for returning and expected visitors

02

Understands 20+ spoken languages at the kiosk, accent-tolerant, with low-latency response

03

Host approval before entry: approve or deny from WhatsApp, email or the portal

04

Pre-approved entries for expected visitors, so they skip the approval wait entirely

05

Deliveries and vendors run as their own flows, separate from the visitor path

06

Searchable visitor log with CSV export, inside a portal with sites, users and roles

// how it runs
ARRIVAL → APPROVAL → RECORD
  1. Kiosk
  2. Cloud application
  3. Host notified
  4. Approval
  5. Visitor record
  6. Admin portal
// how we worked
01 / Diagnose

Watched a full day at the gate: who arrives, who they are looking for, and how long each of them stands there waiting for someone to be found.

02 / Ship

One kiosk at one gate, running the visitor, delivery and vendor flows end to end, with the portal live behind it from day one.

03 / Scale

Live at one site, built for the next: further gates and sites follow the same configuration rather than a new build.

Still running your gate on a paper register?

Bring the workflow and the number it affects. A reply within one business day.

Book a pilotSee other work
// end of case study · An AI front desk that runs the gate