01
Found too late.
Issues surface after the passenger has already left.
AIRPORT CX · OPERATED BY SPECIALIST AGENTS
Live situations.Clear next steps.
A suite of AI agents for airport customer experience. Sense reviews, kiosks and sensors. Alert the right staff in real time. Design a plan when something happens—and help stop it from happening again. Your team stays in control.
ONE SHARED OPERATIONS CONSOLE
ILLUSTRATIVE UI · DEMO DATA
A NEW LAYER ON TOP OF THE TERMINAL
Example integrations · subject to validation
- Google Reviews
- Tripadvisor
- Kiosk hardware
- Occupancy sensors
- WhatsApp Ops
- Staff radio / SMS
01 / THE WORK BETWEEN THE SIGNALS
Passenger issues arrive late.Staff get them by radio.
Reviews pile up. Kiosk scores drift. Sensors beep. Plans live in binders. The same incident returns on the next shift.
That loop—sense, map, alert, plan, prevent—is where a specialist agent belongs.
02
Alerted by chat.
Staff hear about problems on radio, WhatsApp or word of mouth.
03
Same incident again.
Plans stay in binders; root causes rarely update the SOP.
02 / SPECIALISTS, NOT SILOS
Nine agents.One job each.
Distinct roles. Shared airport context. Every hand-off goes to a person.
REV
Review Monitor
Watches Google and Tripadvisor for new reviews.
EXAMPLE WORKFLOW
Review → flag → case
RPL
Reply Drafter
Drafts EN/ES replies to reviews.
EXAMPLE WORKFLOW
Draft → human approve → publish
TRI
Case Triage
Sets priority and SLA for new cases.
EXAMPLE WORKFLOW
Intake → priority → owner
PLN
Action Plan Builder
Builds step-by-step plans from standard docs.
EXAMPLE WORKFLOW
SOP → plan → case owner
RST
Restroom Dispatcher
Dispatches cleaning crews from sensor alerts.
EXAMPLE WORKFLOW
Sensor → draft → crew
Restroom DispatcherLOG
Compliance Log
Records every action and approval for audit.
EXAMPLE WORKFLOW
Action → log → trail
Proposed agent roles from the Pista product. Workflow examples illustrate direction, not a commitment to every integration.
Explore all agents03 / THE SUITE AT WORK
Different specialists.One continuous loop.
Agents should pass the context forward, not the burden back. Here is how a restroom sensor alert can move from signal to a reviewed dispatch—and into prevention.
SENSOR ALERT → DISPATCH → PREVENTION
01 · DEMO FLOW
Restroom Dispatcher
Sense the threshold
Occupancy and odor sensors cross the limit for Gate B.
Sensor alert received
02 · DEMO FLOW
Case Triage
Map and prioritize
Open a case, set P1/P2 and assign the cleaning supervisor.
Routed to cleaning lead
03 · DEMO FLOW
Human review
Your call, before it goes out
Review the draft dispatch and the sensor evidence before the crew is messaged.
Waiting for approval
04 · DEMO FLOW
Action Plan Builder
Plan the response
Attach the step-by-step plan from the restroom SOP.
Plan linked to case
05 · DEMO FLOW
Compliance Log + Standard Docs
Prevent recurrence
Log the action; flag the SOP for a shift-report update.
Audit trail written
SHARED CONTEXT / SENSOR · TERMINAL ZONE · SOP · OWNER · ACTIVITY HISTORY
One trail of context, from the first sensor ping to the final approval.
Inside the platform04 / HUMAN BY DESIGN
Delegate the work. Not the judgment.
The point isn’t to take people out of the loop. It’s to make the loop clearer: what an agent can see, what it can do, and when it needs you.
- Set the scope before a workflow begins.
- Review consequential actions before they go live.
- Trace the inputs, decisions and handoffs.
APPROVAL BOUNDARY · DEMO
DEMOReady for your judgment.
Send restroom dispatch for Gate B after the cleaning supervisor confirms the draft.
- CAN READ
- Sensor readings · Zone map · Restroom SOP
- CAN PREPARE
- Draft dispatch · Case note · Linked plan
- REQUIRES YOU
- Message the cleaning crew
- NOT IN SCOPE
- Change sensor thresholds without an owner
05 / WHAT BETTER COULD LOOK LIKE
Less radio chase. More calm floors.
A faster find
Catch the signal from reviews, kiosks or sensors before it becomes a complaint queue.
A clearer handoff
Carry the source, the owner and the next action together.
A better next shift
Close the loop into the shift report and the SOP—so the same incident is less likely tomorrow.
Design goals, not measured results. The right outcomes depend on your airport’s workflows, data and review process.
06 / START SMALL. BUILD WITH CARE.
One useful airport workflow is a good beginning.
01
Map the real work
Choose a repeatable loop—reviews, restrooms or kiosk feedback. Name the inputs, the decisions and the people who own them.
02
Define the boundaries
Agree what the agent may access, what it may prepare and where approval is essential.
03
Review before you expand
Walk through demo cases together. Refine the handoffs before considering a broader rollout.
07 / A FEW GOOD QUESTIONS
Clarity, beforecommitment.
A useful conversation starts with knowing what to ask.
Is this one general-purpose assistant?
No. Pista is a coordinated suite of specialists. Each has one job; shared context helps work move between them; every consequential hand-off goes to a person.
Do we need to replace our current tools?
No. The approach is to sit on top of reviews, kiosks, sensors and staff channels you already use. Specific connections need validation.
What stays with our team?
Your team defines scope and approval points. Consequential actions, exceptions and operational judgment stay with the people accountable for them.
What will we cover in a demo?
We’ll map an airport workflow, walk the Pista console (or the live demo at /pista) and discuss the review boundaries that would make sense for your team.
OUR APPROACH / FROM THE FLOOR
Built from real airport work.
The founders’ experience in airports—making action plans, taking passenger surveys, mapping spaces, and alerting staff in real time—shaped Pista. The product automates that loop: sense, map, alert, plan and prevent.
Sense · Map · Alert · Plan · Prevent
A MORE CONSIDERED WAY TO RUN THE FLOOR
Start with one airport workflow. See what opens up.
Bring a process your ops or CX team knows well. We’ll explore where agents could help—and where people should stay in control.