# Students and faculty ask the same twenty questions every term.

> Enrolment is a spike: the same questions, from everyone, all at once. Peeve answers and shows them in-product, so the seasonal surge doesn't need a seasonal support team.

Canonical: https://peeve.ai/industries/edtech/

**The pain**

- Seasonal spikes at enrolment
- The same twenty questions, from everyone
- Non-technical users on a deadline

- **Path emphasis:** Answer + Show
- **Judged on:** Deflection at peak, accessibility

## How does Peeve handle an enrolment spike?

By resolving the repeat questions in-product without adding headcount. The twenty questions everyone asks at the start of term are exactly the navigational, how-do-I kind Peeve answers and shows, so a spike in demand doesn't become a spike in support tickets or a scramble to staff up for a season.

## Is Peeve accessible for all students?

Peeve works from the accessibility tree (roles and accessible names), which is the same structure assistive technology relies on, and it pairs motion with optional voice narration. Guidance that respects the accessibility layer is guidance that reaches every student, not only the ones using a mouse.


## More questions

### Does AI customer support make sense for an edtech or education product?

Education products see enrolment spikes and non-technical users, so showing beats describing. Peeve walks a learner or an administrator through the real interface on screen rather than sending a help article, and hands off to a human with context when a question needs one, which reduces the support load during peaks.
