Your campus. Your rules.Get the answers that matter.

FretBox connects residential life, student services and campus teams through processes defined by your university. Students use one app for everyday needs, while administration, wardens, finance, security and service teams work through the views relevant to their responsibilities. FretBox serves 55+ campuses across 16 states/UTs.

The application family includes Resident, Admin, Cafeteria and Security views for their respective users, alongside web access and Smart TV displays where configured. Available capabilities depend on your plan and campus setup.

Yes. Your university can organise hostel and campus operations with access scoped to the teams responsible for each area. Central administration can review information across its authorised scope. Discuss the configuration and student capacity appropriate for your plan.

FretBox focuses on residential life and student services. CampusOS extends the product family into broader campus operations. Our team can help you identify the relevant product and workflows for your institution.

Pratyak addresses AI-powered classroom attendance. It is part of the connected product family shaped by university needs. Visit its website or contact the team to discuss classroom requirements and how it relates to your campus systems.

There are three plans: Starter, Institutional and Large Scale. Starter has a ₹0 licence for up to 2,000 students. Institutional supports up to 10,000 students with an annual per-student subscription. Large Scale offers unlimited student capacity with custom pricing. Request paid pricing through the sales WhatsApp link on the Pricing page.

Starter includes residency records and essential operations: nightly app roll call, occupancy, gate-movement records with approvals, complaints, notices, polls, suggestions and mess menus. It includes basic batch dashboards and overnight reports, with up to 2,000 students and 5 admin logins. Live operations, payments, integrations and customization require a paid plan.

Use Start free on the Pricing page, provide your campus details and verify your phone with a four-digit OTP. Our team reviews the request and may call for verification. Once access is arranged, Starter onboarding is self-guided with AI assistance.

Starter includes 5 admin logins; Institutional includes 50. Additional logins for either plan are ₹499 each. Large Scale provides admin logins as required, with custom pricing for additional logins. Admin and operating users include roles such as wardens, administrators, security and technicians.

Both include live campus operations and payments. Institutional covers up to 10,000 students, read API access, on-demand reporting, three-day structured training and first-week onsite support. Large Scale adds unlimited student capacity, full API access, scheduled reports, archived history, comprehensive emergency escalation, quarterly training and an onsite FretBox coordinator.

Customization is available only with paid plans. This covers workflows, approval chains, fields, roles and branding. Bespoke development is not included in Institutional; it is quoted separately for Large Scale.

Paid quotes include the agreed setup, data migration, integrations, team-led training and priority support. The plan comparison explains differences in API access, reporting and onsite support. Large Scale bespoke development is quoted separately; confirm any optional hardware requirements with the team.

Starter has a capped SMS / WhatsApp allowance for onboarding and emergencies, with AI assistance, email and ticket support. It does not include ongoing WhatsApp alerts, a dedicated WhatsApp support group, relationship manager or team-led onboarding training.

Starter data is deleted after more than 60 days of inactivity. Its raw event history covers 90 days during use; that history window does not override the inactivity deletion policy.

Yes. Your university can control which buildings, floors and rooms are available to each eligible group, and hold selected inventory for a later window. Students see the choices made available under those rules.

Depending on the plan and services enabled by your university, students can manage room booking, payments, KYC uploads, menus, notices, complaints, permissions, visitor invitations, emergency alerts, cafeteria orders and campus bookings in one app.

Where your university requires it, parent consent can be included through WhatsApp before the responsible campus authority makes the decision. Parent approvals are a paid-plan capability and follow the institution’s configured process.

Students can book doctor appointments, gym subscriptions and amenities such as sports grounds, table tennis, student lounges and guest houses where offered by the university. Eligibility, availability and approval rules remain university-controlled. These bookings require a paid plan.

Yes. Students can upload KYC documents through FretBox as part of the campus onboarding and records process. Your university determines the documents it requires and who is authorised to review them.

Email support@fretbox.in with your institution name and a brief description of the issue. Your university remains responsible for hostel permissions, allotment decisions and campus rules. Contact its designated team for those decisions.

Students raise complaints and the responsible team receives the request. The university can define ownership, response expectations and escalation for overdue work. Students follow status updates, while administrators review progress and resolution records.

A student or university staff member fills in visitor details through the app before the visit. Security checks the invitation and follows the university’s entry process. Visitor management is available with paid plans.

Security records the direct visitor’s details and whom they want to meet. The relevant student or staff member receives an app alert to approve or deny entry. Security follows that decision under the university’s rules.

Visitor and parcel workflows bring delivery records and recipient updates into the campus process. Your university defines how parcels are received and handed over. Parcel management requires a paid plan.

Yes. Broadcast to the whole university or combine location and student filters: building, floor, room, gender, programme and year. For example, reach one room or female B.Tech second-year students in a selected hostel. The audience follows your records and the administrator’s authorised scope.

Yes. Urgent broadcasts are designed to ring recipients’ phones, including when silent, for critical campus communication. Confirm the required app permissions and device setup with the team during deployment.

Yes. Administrators can track who has read the message, helping the university follow up on important communications.

Mess teams publish menus and review voluntary meal opt-outs before preparation. The configured QR or face-device process records meal presence. Teams can review separate breakfast, lunch and dinner attendance totals against expected participation.

Students can voluntarily opt out when they do not plan to eat, giving the mess team better planning information. An opt-out does not automatically imply a refund or credit; any financial treatment follows the university’s policy.

Where your university offers multiple mess vendors, students can choose, book and pay for their preferred mess through FretBox. Vendor choice depends on your campus setup and is not offered at every university.

Yes. Students browse the university cafeteria menu and order through FretBox. The cafeteria prepares the food and campus delivery staff take it to the hostel room. Your university controls service availability, ordering hours and the rooms served. Cafeteria ordering requires a paid plan.

Students can raise emergency alerts, including health emergencies, through FretBox. Alert routing and escalation follow the campus setup and plan. Starter provides in-app alerts with a capped onboarding/emergency messaging allowance; paid plans add escalation, with more comprehensive arrangements in Large Scale.

Authorised leaders can review connected operational information such as occupancy, collections, complaints, permissions and meal participation. The depth of dashboards, report timing and history depends on the plan and the records available to the university.

Yes. Paid plans support hostel fees, mess and other campus charges through the configured payment gateway. Available payment methods depend on that gateway and your university’s setup.

Yes. Authorised teams can record offline or UPI payments and manually update invoices, keeping those collections alongside online payments in the campus record.

Yes. Universities can collect fines and deposits and record partial payments against invoices. Finance teams can follow the amounts collected and the balance remaining.

Yes. The agreed ERP or Tally integration can update central financial records when students pay online. The connection is scoped with your finance and IT teams around identifiers, payment references and reconciliation. A successful payment and a reconciled accounting record are separate states.

Examples include Razorpay, Cashfree and EaseBuzz. These are examples, not an exhaustive list. Discuss your existing payment provider, banking setup and interfaces with the team to assess the connection.

Finance teams can review invoices, payment references, recorded collections and outstanding balances. Where systems are connected, exceptions need review so that payment records and central accounting records remain aligned.

Prepare student and resident records, room inventory, staff responsibilities, fee structures and the university policies that shape your workflows. Identify a campus owner and the IT and finance contacts needed for any integrations.

Both paid plans include onsite visits. Institutional includes dedicated implementation, three-day structured training and first-week onsite support. Large Scale includes personalised implementation, quarterly structured training and an ongoing onsite coordinator. Starter is self-guided.

Yes, you can bring additional systems for assessment. SAP, Oracle PeopleSoft, custom ERPs, payment providers and access devices are examples rather than a complete compatibility list. Our team reviews available interfaces, record mapping, permissions and support ownership with your IT team.

Core app and web workflows do not require new hardware. Biometric and physical gate connections are optional, with compatibility assessed for the devices you use. Confirm any hardware requirements during scoping.

Starter does not include integration access. Institutional includes read API access; Large Scale includes full API access. Agree the required systems, permissions and data flows with the team as part of your integration scope.

Paid plans allow customization of workflows, approvals, fields, roles and branding. The university defines responsibility and access. Bespoke development is a separate commercial item for Large Scale and is not included in Institutional.

You can review the ISO/IEC 27001:2022 information-security and ISO 9001:2015 quality-management certificates on the Security & Compliance page. FretBox also undertakes annual independent vulnerability assessment and penetration testing.

University and student data is hosted on cloud infrastructure in India. Review the hosting, data flows and processing arrangements with the team during your IT evaluation.

Security measures include encryption in transit and at rest, university-controlled access, daily and iterative backups, and an audit trail recording changes. Review the details relevant to your deployment with your IT team.

After contract termination, institutions have a 30-day data export window. Institutional and student data is securely deleted at the end of that window, with a deletion certificate, subject to the legal-hold exceptions described in the Privacy Policy. Starter separately deletes data after more than 60 days of inactivity; its raw event history covers 90 days during use. Paid-plan history and reporting differ by plan.

Yes. Ask the team for the available security and data-processing documentation and the process for reviewing VAPT information. Any document-sharing conditions can be confirmed during your evaluation.

Availability commitments, maintenance arrangements, response times and escalation routes should be reviewed in your service agreement. They depend on the services and plan agreed for your institution.

Starter uses self-guided onboarding with AI assistance. Institutional includes three-day structured training and first-week onsite support. Large Scale includes quarterly structured training and ongoing onsite support. Both paid plans include campus visits.

Use the sales WhatsApp link on the Pricing page, or submit an enquiry through Contact. Select the product and enquiry purpose; for a callback, add a convenient time. Verify your mobile number to send the form, and the team will follow up using your details.

Ask for a relevant peer reference and describe the institution type and topics you want to discuss. Introductions depend on the customer’s availability and consent.

The Noida office is at 1st Floor, B-32, Sector 57, near Sector 59 Metro. Branch offices are in Bhubaneshwar, Indore and Hyderabad. Bengaluru, Ahmedabad and Pune are coming soon. Arrange a visit with the team in advance.

University evaluations, pricing and partnerships go to business@fretbox.in or the sales WhatsApp number +91 78811 10070. Existing users can email support@fretbox.in with their institution and issue. Campus administrators can also use the support channels included in their plan.