End the boomerang on data requests
An IR data request is a question from someone on campus (a dean, a department chair, the provost's office) that the institutional research team answers with a number, a table, or a chart. Clema runs each one end to end: conversational intake, agent-driven SOPs, and a responder AI agent that drafts the answer with the charts attached for an analyst to review and send.
From our research with 50+ IR/IE professionals across 19 states: 91% of teams struggle with how data requests are managed, and ad hoc requests take up 40 to 60% of team capacity. Read the whitepaper
Requester opens a chat. Clema asks the missing questions automatically.
Clema tags it, picks a responder, and pulls the right datasets.
AI agent produces a cited draft response from your warehouse.
Responder reviews, edits, and ships. Audit trail saved.
Why Clema data requests
Conversational intake, responder AI agent, and SOPs written for agents.
Conversational intake
Replace rigid forms. Clema asks the missing questions ("for which cohort?", "by what date?") so requests arrive with the context the responder actually needs.
Responder AI agent
Pulls the data, drafts the response, and packages it with the relevant charts, tables, or report excerpts. The responder reviews, edits, and sends.
Agent-centric SOPs
Resolution plans are written for agents, not for humans. Past tickets become the SOPs that resolve future ones automatically.
Full queue management
Assignment, reassignment, snooze, scheduled replies, and audit trail across every channel, all in one inbox.
"Talk to the IR team" by default
Stakeholders see a friendly call-to-action, not a help-desk ticket. Internally, your team still works the queue as tickets.
History-aware from day one
Past tickets become memory. When the same request comes back, Clema knows what you sent last time, who asked, and what's changed in the data since.
Get started today
Try Clema data requests free, or move to a paid plan as your team grows.
Free plan
Explore Clema data requests with no commitment
No credit card required
- Free forever, no credit card
- 20 AI conversations a month
- Full access to Clema data requests data
- Formatted, cited responses
Paid plans
For growing teams and whole institutions
Monthly or annual, no implementation fee
- Pro300 chats, 3 seats$99/mo
- Max1,000 chats, 10 seats$299/mo
- EnterpriseSSO, integrations, SLACustom
Frequently
asked questions
Instead of a rigid form, requesters chat. Clema asks the right follow-up questions (cohort, timeframe, format) so the request arrives complete. Cuts the back-and-forth that eats most of an IR team's week.
For routine pulls, it queries your warehouse and drafts a response with the charts and tables attached. For nuanced asks, it accelerates the draft instead of replacing the analyst.
SOPs aren't documents for humans to read. They're machine-readable plans that an agent executes. Past tickets become the SOPs that resolve future versions of the same request.
Yes. Requests can come in via web form, email forward, or Slack and land in the same queue. No behavior change required from your stakeholders.
Because stakeholders don't think of themselves as filing IT tickets; they think they're asking a colleague. The friendlier call-to-action gets more, better requests. Your team still sees it as a ticket internally.
Free your team from the request queue
Bring intake, routing, drafting, and audit into one tool.