Skip to content
All modules Communication & Family Engagement

Front Office software for Indian schools

Enquiries, calls, dispatch

Feature identity

Front Office

An illustration, not a screenshot. The interactive example below shows what this capability actually does.

Example view

Front Office in a school workflow

Enquiries, calls, dispatch

Communication & Family Engagement
Front Office in a school workflow
Communication & Family Engagement
  1. 01
    Required context

    A plan that includes Front Office must be confirmed before rollout.

  2. 02
    Supported work

    Gate passes mint scannable QR codes and require approval before they're valid.

  3. 03
    Reviewable result

    A reception command view for visitors, gate passes, walk-in enquiries and general complaints needing follow-up.

Example record

Front Office

Authorised view
  • Gate passes mint scannable QR codes and require approval before they're valid
  • Enquiry register with an idempotent one-click convert-to-lead
  • Complaints move open → in-progress → resolved, and resolving requires a recorded resolution
  • Dashboard KPIs across visitors, passes, enquiries and complaints
A reception command view for visitors, gate passes, walk-in enquiries and general complaints needing follow-up.
Code-native illustrative example · not live product UI · no customer dataExample labels and outcomes come from this capability's reviewed catalogue record.

Product scope

What it does

Reception's daily cockpit: the visitor log, QR gate passes with an approval step, a walk-in/phone enquiry register, and a complaints book — with KPIs for on-premises-now, open enquiries and pending passes. One click converts an enquiry into an admissions CRM lead, so a walk-in never leaks out of the funnel.

The school problem

School teams need a dependable way to handle Front Office: Enquiries, calls, dispatch. The required records, assigned roles and review boundary must remain explicit.

Day-to-day work

How your school uses it day to day

Enquiries, calls, dispatch.

  1. Gate passes mint scannable QR codes and require approval before they're valid
  2. Enquiry register with an idempotent one-click convert-to-lead
  3. Complaints move open → in-progress → resolved, and resolving requires a recorded resolution
  4. Dashboard KPIs across visitors, passes, enquiries and complaints

Operational result

What your school gets

A reception command view for visitors, gate passes, walk-in enquiries and general complaints needing follow-up.

Access and ownership

Who typically uses it

  • Receptionist
  • Front-office manager
  • Admissions officer
  • School administrator
  • Principal

What each person can actually see depends on the role you give them and which classes or records you assign.

Availability and setup

What to confirm before rollout

Included from Growth

Front-office visitor and reception operations.

  • A plan that includes Front Office
  • Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Connected operating context

Available workflows

These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.

Explore all modules

Buyer questions

Frequently asked questions

The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.

Does Front Office work on its own?

Visitor Management, Enquiry Management, Complaint Management, Task Management are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.

What should our school prepare before enabling Front Office?

A plan that includes Front Office. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.

Is AI used in Front Office?

No AI capability is asserted for Front Office. Its documented work remains controlled by school records, roles and permissions.

How do we confirm the plan and implementation scope?

Front Office is included from Growth in the current public plan matrix. Final rollout scope, services and external dependencies are confirmed in your written proposal.

See it in your school context

Run front office the connected way.

See how this workflow fits your school's current records, roles, plan and rollout requirements.