Hospitality: Guest Complaint Triage with Codex: API Runtime Pattern
A production playbook for guest complaint triage in hospitality operations using Codex: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Hospitality support and operations teams
The problem
Hospitality support and operations teams need guest complaint triage to run repeatedly against guest messages, booking records, photos, refunds policy, and escalation notes. In hospitality operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the guest complaint triage instructions as a skill, send guest messages, booking records, photos, refunds policy, and escalation notes as run-scoped inputs, execute with Codex, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For guest complaint triage, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=codex
workflow=hospitality-guest-complaint-triage
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo