Request inputs

Why

An enterprise customer has a strict process, where every request must contain specific values from end users. The request cannot be raised without these values. For example, a PO request always requires a value for a PO to be raised. This should be as deterministic as possible.

Goal

Enable builders to define what information a request contains so the operation can process, understand, and escalate work clearly.

---

Problem

Currently, requests have no explicit structure defined by the builder. This leads to:

• unclear input for the agent
• inconsistent request data
• weak or confusing previews
• reduced confidence in escalation and outcomes Without a defined request shape, the operation feels like a black box rather than a system.

---

Solution

TBD