The passenger-voice
platform for airports.
The engine behind AAI's customer-satisfaction programme. Nine channels, 100+ languages, AI categorisation, regulator-ready by construction.
The terminal today
is a wall of survey tools.
CSAT on one platform, lounge survey on another, website widget on a third, the regulator's quarterly on a fourth. Different taxonomies, no shared record. The feedback officer sees the silos only at month-end — when the reports won't reconcile.
- Channels siloed — separate vendors, separate taxonomies.
- Languages stop at two or three.
- Free text categorised by hand — analyst memory drives the categories.
- Regulator format assembled in Excel, a week before deadline.
- Every channel on one engine — nine intake routes, one taxonomy.
- 100+ languages auto-detected at capture.
- AI categorisation + sentiment; sensitive items queued for review.
- DGCA quarterly in ~2 hours. ACI ASQ feed, same engine.
Nine ways to ask.
One engine.
Different moments, different channels. One engine, one taxonomy, one audit trail — so the CEO's dashboard and the regulator submission are the same data.
From boarding pass
to regulator submission.
Passenger responds.
Any of nine channels, any language. Audit-hashed at intake.
Categorised & scored.
Free text against your taxonomy. Sensitive items queue for review.
Regulator export.
DGCA quarterly · ACI ASQ · ICAO 9184. Signed + audit-logged.
Three roles.
One record, three views.
Airport CEO.
Reads the cause, not just the headline. CSAT trend, cause breakdown, DGCA ready-state.
Feedback officer.
The keyboard at the centre of the workflow. Configures surveys, supervises sensitive-category review, signs off the regulator report.
DGCA inspector.
Quarterly CSS in the format the regulation specifies. Audit log on demand. Network benchmark.
The product airports
actually use.
Production-ready in a single quarter.
Live at two AAI pilot airports — full multi-channel capture, 100+ languages, AI categorisation, DGCA reporting end to end.
- 250,000+ responses processed.
- 98% surveyor adoption in the first cycle.
- ~2-hour DGCA cycle from assembly to submission.
Rolling out to 130+ AAI airports.
Metros, regional hubs, balance of stations — all live Jul–Aug 2026 on the same template.
- Network benchmarking across every AAI airport.
- Per-airport tenancy, strict access controls.
- One feed for DGCA, ICAO, ACI ASQ.
Built to the standards
that govern the report.
Common questions.
Can I buy just the survey engine?
Yes. Core = designer + 9 channels + 100+ languages + analytics. Add the Regulator Pack for DGCA; Complaint Loop for closed-loop; Operational Triggers for ATOMS-fired surveys. Each is independent.
What channels can we activate on day one?
Any subset of the nine. AAI runs QR + kiosk + surveyor app + email. A private hub might start with kiosk + WhatsApp + web. Same engine; channels are switches.
What happens to a complaint that comes through the survey?
If Complaint Loop is on and AeroResolve is deployed, the response routes there with SLA timer, evidence, and passenger contact. Otherwise complaints surface in a queue.
Where is the data hosted?
Your chosen region. For AAI — Indian cloud (DPDP-aligned). Per-airport tenancy, customer-managed keys on Enterprise. Trust Center →
Start with one terminal, scale to the network.
Pilot template production-tested. Scoped in days, configured in a week, live in weeks.
Bring AeroFeedback
to your airport.
A 30-minute walkthrough on your terminals, channels, and regulator deadline.