Hostel and Facility Requests: An Agent Use Case

A deputy chief warden in a central university showed us the real queue. Not the website. The WhatsApp. A broken geyser in Block C, a first-year who had not received a mattress, a parent asking why the mess skipped eggs, a medical certificate that should never have been in a group of forty wardens, and three messages that were ragging complaints dressed as 'room change'. The computer centre wanted a chatbot on the prospectus. The warden wanted the geyser.

This is a case-shaped field guide for registrars, chief wardens, estates officers and student-welfare deans. The use case is unglamorous and that is why it works. A facility agent can intake a request, classify it, route it, quote the published SLA, and write a status the student can read. It should not allocate rooms by a hidden score, close a ragging ticket, or diagnose a medical exemption. Those are human acts with statute and statute-adjacent duties behind them.

We are writing as a B2G vendor that runs on-prem. We will not pretend a consumer chatbot is a hostel office. If your first campus AI purchase is a smiling bubble on the homepage, you have bought a press note. If it is a ticket that the plumber actually sees, you have bought operations.

Why hostel tickets beat a prospectus bot

The work is already structured. There is a requester, a location, a category, a priority, and a closer. Estates, mess, housekeeping, IT in the hostel, and the warden's office already know those lanes even if the lanes live in a register. An agent that writes a ticket into the lane you already have is an assistant. An agent that invents a new front door and emails the registrar is a second queue.

The data is sensitive enough to force architecture conversations you should have anyway. Student mobile numbers, room numbers, medical notes, and complaints about other students are personal data. Some complainants are minors. A public model that sees those messages is the wrong processor. On-prem retrieval over the hostel standing orders and the estates vendor list is the right shape.

Success is visible. A geyser closed in six hours is a metric a syndicate understands. A '95% student satisfaction' chatbot score is a vendor slide. Start where the syndicate can audit the outcome without a glossary.

The job the agent may hold

Intake in the languages you will actually mark. A Hindi–English code-mix message from a first-year is the default, not the edge case. Map it to a category the estates vendor already invoices against: electrical, plumbing, carpentry, housekeeping, mess, LAN, furniture.

Route with a published matrix. Night-time electrical in a women's hostel is not the same desk as a weekday furniture request in a research scholars' block. The matrix is a standing order signed by the chief warden. The agent does not invent a desk because the language model thought 'security' sounded right.

Explain status without leaking the other student's name. 'Your ticket 1842 is with electrical, SLA 24 hours, last update 16:40' is a complete answer. 'We are waiting for the boy in 214 to confirm he broke it' is a disciplinary incident.

Write the verbs into the standing order. Verbs the agent does not have are how you stay out of the syndicate.

Verb	Agent may	Human must	Never
Intake and classify	Yes, against a closed category list	Audit a sample every week	Free-text categories that become slurs or medical diagnoses
Route and SLA	Yes, from the signed matrix	Change the matrix	Skip a women's-hostel night rule because the model is 'helpful'
Room allotment or change	Show vacancy counts the warden already published	Allot, including any reservation, disability or medical claim	Rank students by a hidden 'fit' or 'risk' score
Discipline / ragging / harassment	Offer the official complaint channel and freeze the chat for that thread	The statutory committee and the warden	Mediate, summarise the accused to a group, or close as 'resolved'
Medical exemption from mess or floor	Accept a document into a restricted tray	The medical officer and the warden	Read the certificate into a general ticket or a model prompt

Minors, room-mates and the WhatsApp original sin

Plenty of Indian hostels house seventeen-year-olds. Diploma campuses, integrated programmes, and late-board results make minority ordinary. The DPDP Act treats a child as a person under eighteen. Processing their personal data needs verifiable parental consent unless a prescribed exemption applies. Check the live Rules. Do not assume a hostel WhatsApp is an educational exemption. Build an age flag from admission data and keep children's tickets in a tighter tray.

A ticket about a room-mate is two people's data. The agent should not retrieve the room-mate's discipline file to 'give context'. Context is how gossip becomes a system. If the request is a room change for conflict, route to the warden with the requester's words, not a character assessment.

Kill the unofficial group as the system of record. The agent is worthless if the plumber still only works from the supervisor's phone. The standing order must say the ticket is the instruction. That is change management, not a model upgrade.

Architecture that survives a warden transfer

Run the agent where the hostel office already trusts a lock: campus data centre or an isolated rack. Identity from the university IdP, not the vendor's users. Logs in the campus SIEM for the CERT-In 180-day floor, plus whatever longer retention the syndicate wants for discipline-adjacent tickets.

Do not train on ticket text. Ticket text is how students describe illness, caste slurs, and money. A vendor who wants those traces to 'improve the product' is asking to be a second warden. Refuse.

Write an exit. Next year's warden should be able to export open tickets to the estates register without the vendor's console. If the only copy lives in a GPU node's chat store, you have rebuilt WhatsApp with extra steps.

What to tell the contractor in the same week

The estates vendor is part of the system. If their supervisor still only works from a personal phone, the agent is a diary. Put the official inbox in the work order. Say that a ticket not in that inbox is not an instruction. Say that photos of student rooms do not go to a vendor WhatsApp group. Those sentences belong in the next work-order amendment, not in a model card.

Night and Sunday cover is a roster, not a hope. Write who holds the phone after 10 p.m. in the women's hostel and in the research-scholars' block. If the roster is empty, the agent should say the SLA is paused, not invent a plumber. False SLAs are how first-years stop reporting broken locks.

Measure two numbers only in the pilot: time from ticket to first human acknowledgement, and time to close. Do not measure 'student delight'. Delight is how you get a personality. Acknowledgement is how you get a geyser.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Students will not use another portal.

Then put the agent on the channel they already use, with identity, and write into the official ticket store. A WhatsApp unofficial group is not identity. A logged official handle can be.

We should start with a campus-wide concierge.

A concierge that can touch discipline, fees, exams and hostels is a data-governance project pretending to be a weekend pilot. Start with two categories in two buildings. Expand when the plumber closes the ticket.

The warden wants the agent to suggest room-mates.

That is allocation plus profiling. It will import caste, language, food and 'attitude' as features whether you name them or not. Keep matching off the agent. Vacancy lists only.

Our facilities vendor already has an app.

Good. Integrate or replace, do not duplicate. An agent that writes a second ticket the vendor ignores is theatre. The contract with the vendor must name the official inbox.

A six-week hostel-ticket pilot

Pilot two categories, two buildings, one contractor. Everything else is a sequel.

1. Week 1: chief warden signs the category list and the night-routing matrix. Name the medical tray and the ragging freeze.
2. Week 2: connect identity and the estates ticket store. No new database if a register already exists. Hash the standing orders into the retrieval set.
3. Week 3: staff-only dry run. Wardens file fake tickets. Fix the verbs the agent invented.
4. Week 4–5: live in two buildings. Daily sample of ten tickets by the deputy chief warden.
5. Week 6: syndicate one-pager — closure times, leaks found, whether WhatsApp actually died. Decide conversation UI only after this page.

How this shows up in the file

The standing order is the product. Categories, SLAs, night rules, medical tray, ragging freeze, no room-allocation, no training on ticket text, on-prem processing, named contractor inbox. If it is not in the order, the agent does not have the verb.

Attach the DPDP basis: facility administration as a function the university already performs, notice to students, tighter rules for minors. Counsel signs that paragraph, not the vendor.

This article is informational field guidance for Indian public universities and colleges, not legal, regulatory, academic, labour or procurement advice. Confirm against the live AICTE / UGC / NAAC notice, the DPDP Act and Rules as commenced, your Act and statutes, reservation orders, labour counsel and the syndicate before you file it.