2 posts tagged with "engineering"

When a case gets stuck — every hotel full, every provider returning 422, a policy mismatch — Nexa's exception agent reads the context, proposes up to three actions, and hands the item back to a human operator. A common question: why doesn't the agent just do the thing it's recommending? We made that choice on purpose, and this post explains how we enforce it.

The flight-disruption predictor is the model that lets Nexa start sourcing hotel inventory before an airline officially declares a disruption. It runs as a Nexa Trained Model on Google — Nexa-built, Nexa-trained, Nexa-served — with no third-party AI service for the customer to provision. This post covers how we approached it.