SmartRequest
SmartRequest is RabbitQA's project-scoped request intake, evaluation, review, and approval module. It combines a request description and supporting files with provisioned product knowledge, adaptive questions, factor-based scoring, generated summaries, acceptance criteria, approval steps, board workflow, and session history.
Use SmartRequest to turn an unstructured need into a reviewable request. AI-generated content and the evaluation score support a decision; they do not replace evidence review or approval.
SmartRequest areas
| Area | Use it to |
|---|---|
| Dashboard | Review project-level request volume, approvals, status distribution, and recent work. |
| Request Board | Review generated requests, create manual cards, approve or reject, manage workflow, and hand off approved work. |
| SmartRequest Generation | Create a structured, scored request through an evidence-backed adaptive evaluation. |
| Request Sessions | Find, resume, inspect, export, or delete stored AI-evaluation sessions. |
| Settings | Configure company threshold, factor order, custom fields, and default approval flow. |
| Provisioning | Maintain the products, project visibility, modules, documents, fields, and product-specific approval context used by generation. |
Provisioning is shared
Provisioning appears in the platform navigation at /provisioning, not inside the SmartRequest
module navigation. SmartRequest consumes the products and module context maintained there.
Typical workflow
- Configure a product and at least one module in Provisioning.
- Confirm the active RabbitQA project can access that product.
- Enter the request need and attach only relevant supporting evidence.
- Select the product and module, then answer adaptive questions with supported facts.
- Review the generated title, summary, priority, acceptance criteria, custom fields, and Q&A.
- Submit the request to the board for its configured approval sequence.
- After approval, manage delivery workflow or continue the request into CaseWriter or Smart PBI.
Correct use
- Keep stable product rules in Provisioning and request-specific facts in the request description and supporting files.
- Use Not sure yet or Skip with Comment when a question requires a rule the evidence does not define.
- Treat the threshold as score readiness, not automatic approval.
- Use Archive for retained inactive work and Delete only for permanent removal.
- Review downstream inputs after a handoff; preselection does not start generation.
