Understand AI availability and human review
Welcome to Resgrid Academy. In this lesson, we will understand ai availability and human review. AI product descriptions and code can move ahead of deployment availability, so training must distinguish released tools from planned ones. We will explain the features, the setup decisions, and a practical way to check the result.
A department scenario
An administrator asks Admin Assist why a member was not paged and reviews the evidence it links to. Get explanations and drafts for people to review, alongside the tools you already use. The examples in this series use a fictional department and are teaching scenarios, not default settings.
Enhanced AI
Enhanced AI. AI assistance beyond the free Admin Assist allowance. Nothing to set up yet; your free Admin Assist allowance works without it. This feature is marked planned in the source catalog. Verify release availability before recording a configuration walkthrough.
AI dispatch settings and activity
The checkout contains gated AI dispatch settings for enrichment fields, confidence, sender scope, token limits, and activity. Confirm host enablement and department rollout before reviewing the settings. Saving settings alone does not start enrichment. Check the Running state, activity outcomes, and usage. This source-present feature is unverified on the target deployment. Confirm availability in the demo department before recording the live workflow.
Configure one useful workflow
For the training scenario, work in this order. Step 1. Use deterministic Setup Wizard and Setup Report for configuration guidance. Step 2. Check whether Admin AI is enabled for the target department. Step 3. Check release and rollout before teaching Enhanced AI summaries or drafts.
Verify the result
Now verify the result. Record the target deployment version and observed feature availability. Human reviewers remain responsible for any generated explanation or draft. A common problem to watch for: The catalog in this checkout marks Enhanced AI as planned. This lesson explains its scope; it does not demonstrate a released configuration.
Try it with your department
Your practice task is simple. Ask a configuration question through an available tool, inspect its evidence, and identify any unknowns before making a change. Record the result, who owns the follow-up, and when it should be reviewed.