leave_request_infoWorked example — establishes the design template for all 6 intents. Remaining intents (
leave_balance_check,payslip_access,benefits_policy,policy_lookup,handoff_to_human) follow this structure.
| Field | Value |
|---|---|
| Intent ID | leave_request_info |
| Display name (EN) | Leave Request Information |
| Display name (HU) | Szabadság igénylés információ |
| Category | Informational (read-only) |
| Priority | P0 — must-have v1 |
| Estimated query volume | ~25% of total bot traffic |
| Owner | Dmitrii Drugov |
| Status | Design v1 — draft |
| Dependencies | Knowledge base (8 policy docs), SSO user context |
User wants to know how to request leave — the process, eligibility, timing, approver, type-specific rules. This is informational, not transactional. The bot does not submit the request — it explains the policy and directs user to SAP SuccessFactors self-service portal.
| This intent | NOT this intent (other intent) |
|---|---|
| "How do I request vacation?" | "How many days do I have left?" → leave_balance_check |
| "Parental leave eligibility?" | "Submit a leave request for next Tuesday" → out of scope v1 (route to SAP SF) |
| "Sick leave procedure?" | "I'm sick today" → handoff or direct to manager |
Designed to cover the realistic variety employees produce: formal, casual, fragments, typos, specific cases, mixed language.