What environment state should a referral simulation contain?

Specify the state below when asking for a generated environment that exercises more than transcript completion.

- Customer contact preferences visible to the frontline role. - Existing referrals discoverable through an account search action. - Queue availability returned by a routing lookup tool. - Required intake fields checked when a referral is submitted. - Specialist notes restricted by the supplied role permissions. - Outstanding dependencies that prevent a referral from advancing. - Customer responses available only after an appropriate question.

These elements let the environment distinguish uncertainty from absence. A model that has not searched for an existing referral should not conclude that no referral exists. Likewise, a queue that is unavailable at submission time creates a different problem from an invalid destination.

The buyer can ask for a state inventory showing what is initially visible, what becomes visible through tools and what remains outside the agent’s access. Hidden state should have a clear task purpose. It can test whether the model gathers necessary evidence, respects access boundaries or explains a pending dependency without claiming that the specialised process has already begun.