Practical AI in Hotel Operations
Lesson 7 / 10The review-response workflow

When to override the AI

Most AI workflows in hospitality should keep a human in the loop — not because the AI is wrong most of the time, but because the cost of the cases where it is wrong is asymmetric. The 1% of responses that go badly wrong cause 20× the damage of the 99% that are fine. Knowing when to override the AI is the skill that prevents the asymmetric tail risk.

Always override when

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Often override when

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Rarely override when

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

The override discipline

Track overrides over time. If you are overriding 30% of a workflow's output, the prompt is not yet good enough — go back and iterate. If you are overriding 5%, the prompt is in production-ready shape. If you are overriding 0%, you have probably stopped reviewing — which is when the asymmetric tail risk catches up to you.

Finished this lesson?
Mark complete and move to the next lesson.
When to override the AI · Practical AI in Hotel Operations · OtelCiro Academy