# 2. Doubt Clearing Sessions

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 2. Doubt Clearing Sessions

### 2.1 1-on-1 Session Booking
**What it does:** Configures and manages 1-on-1 doubt clearing sessions between a student and a teacher: booking availability windows, session duration, teacher capacity, and plan-based entitlement (e.g., 2 per month on the All Subjects plan).

**Sub-features:**
- 1-on-1 booking enable/disable
- Booking availability windows per teacher
- Session duration settings
- Teacher capacity limits (max concurrent/weekly sessions)
- Plan-based entitlement (sessions per month by subscription tier)
- Booking cancellation and rescheduling rules
- Available on web
- Event logging (action performed)
- Audit logging of 1-on-1 session booking

**Super Admin User Journey:**
1. Super Admin enables 1-on-1 booking and sets the session duration.
2. Defines each teacher's availability windows and capacity limits.
3. Sets the plan-based entitlement (e.g., 2 sessions/month on the All Subjects tier).
4. Students book within their entitlement; the platform enforces the limits.
5. For a booking that must change, the student reschedules or cancels per the rules.
6. Reviews the booking list: scheduled, completed, cancelled, entitlement usage.
7. Each booking action is event-logged and audit-logged.

**Rules & Edge Cases:**
- A student cannot book beyond their plan entitlement; the booking is blocked with the reason.
- A booking outside a teacher's availability window is not allowed.
- A teacher cannot exceed their capacity limit; further bookings are queued or blocked.
- Cancellation before the session frees the slot; the entitlement is restored per the rules.
- Booking actions are audit-logged with the student, teacher, session, and timestamp.

### 2.2 Group Doubt Solving Sessions
**What it does:** Manages group doubt solving sessions: multiple students with a teacher to solve common doubts, group size, topic focus, and scheduling.

**Sub-features:**
- Group doubt session enable/disable
- Group size limits
- Topic/doubt focus per session
- Scheduling (one-off or recurring)
- Student enrollment (self or teacher-assigned)
- Available on web
- Event logging (action performed)
- Audit logging of group doubt sessions

**Super Admin User Journey:**
1. Super Admin enables group doubt solving sessions and sets the group size limits.
2. Creates a session with a topic/doubt focus, teacher, and schedule.
3. Students enroll (or the teacher assigns them) within the size limit.
4. The session runs; enrollment and completion are recorded.
5. Reviews the sessions list: enrollment, completion, topics covered.
6. Each action is event-logged and audit-logged.

**Rules & Edge Cases:**
- Enrollment is blocked at the group size limit; late joiners are flagged.
- A session with no enrolled students is flagged (not silently run empty).
- Actions are audit-logged with the session, the actor, and the timestamp.

### 2.3 Drop-In Office Hours
**What it does:** Configures drop-in office hours: open time slots where students can join without a prior booking, teacher availability, and capacity.

**Sub-features:**
- Office hours enable/disable
- Open slot scheduling (recurring time windows)
- Teacher availability per slot
- Capacity per slot (max students)
- First-come-first-served join rules
- Available on web
- Event logging (action performed)
- Audit logging of office hours configuration

**Super Admin User Journey:**
1. Super Admin enables drop-in office hours and defines the recurring open slots.
2. Assigns teachers to slots and sets the capacity per slot.
3. Students join a slot during the window, first-come-first-served, up to capacity.
4. Reviews the office hours: slots, attendance, capacity usage.
5. Each configuration change is event-logged and audit-logged.

**Rules & Edge Cases:**
- A slot at full capacity rejects further joins with a "full" indication.
- Office hours outside the defined windows are not joinable.
- Configuration changes are audit-logged with the slots, the change, and the timestamp.

### 2.4 AI-Assisted Doubt Resolution Escalation
**What it does:** Configures the AI-assisted doubt resolution path before escalating to a human: the AI attempts to resolve the doubt first, and unresolved or low-confidence doubts are escalated to a teacher, with the escalation rules and thresholds defined.

**Sub-features:**
- AI-first resolution enable/disable
- AI confidence threshold for auto-resolution
- Escalation trigger: low confidence, student request, repeated failure
- Escalation routing (to the subject teacher or on-duty teacher)
- Escalation context passed (the doubt, the AI attempt, the student's progress)
- Available on web
- Event logging (action performed)
- Audit logging of doubt resolution escalation

**Super Admin User Journey:**
1. Super Admin enables AI-first doubt resolution and sets the confidence threshold.
2. Defines the escalation triggers (low confidence, student request, repeated failure).
3. Sets the escalation routing (subject teacher or on-duty teacher).
4. A student's doubt is attempted by the AI; if unresolved, it is escalated with full context.
5. Reviews the escalation log: doubts, AI attempts, escalations, resolutions.
6. Each escalation is event-logged and audit-logged.

**Rules & Edge Cases:**
- A doubt resolved by the AI above the confidence threshold is not escalated.
- A student can always request escalation to a human regardless of the AI result.
- The escalation always carries the context (doubt, AI attempt, student progress) so the teacher is not starting from zero.
- Escalations are audit-logged with the doubt, the trigger, the routed teacher, and the timestamp.
