Hospitality: Guest Complaint Triage with Claude Code: Sandbox Policy
A production playbook for guest complaint triage in hospitality operations using Claude Code: sandbox policy, 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
Run guest complaint triage in an ephemeral sandbox, keep provider credentials in the broker, expose narrow tools, and store logs outside the workspace for review.
Tradeoffs and failure modes
A narrower runtime blocks ambient machine behavior, but it gives security reviewers a concrete boundary. 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.
Runtime boundary
filesystem: /skill and /skill/.argo/inputs only
network: deny by default
artifacts: /skill/output/artifacts
logs: retained outside sandbox
provider: Claude Code
Run this on Argo