72%
Requests complete on first submit
Front Door
Make it easy to ask for help the right way.
This migrated page keeps the business-friendly intake story from the demo, but anchors it inside the real web application boundary so it can evolve toward live API-backed request submission.
4.2 hrs
Median intake-to-routing time
38%
Requests improved by AI clarification
12%
Duplicate or related requests
Business-Friendly Request Form
The form asks for the information that actually helps routing, prioritization, and delivery instead of generic ticket noise.
| Field | Why it matters | Expectation |
|---|---|---|
| Business need | What the requester is trying to do and why it matters. | Required |
| Affected users or audience | Who is blocked, impacted, or waiting. | Required |
| Needed by | Business deadline with context, not just a preferred date. | Required |
| Approver | Required for access, exceptions, and some change-related work. | Conditional |
| Attachments or examples | Screenshots, reports, links, or source files when useful. | Optional |
AI Intake Assist
AI improves the request before it becomes work. It does not decide the final request on its own.
What the requester writes
"Our dashboard is wrong again and leadership needs it fixed before next week. It has something to do with the public data update. Please help as soon as possible."
What AI returns
Suggested type:
Data / reporting request
Structured summary:
Leadership dashboard appears incorrect because the public data refresh may have failed or posted incomplete data.
Missing information:
Which dashboard, which data source, what is incorrect, and who is affected.
Related request:
Possible duplicate of `REP-2335 Public Data Refresh Validation`.