Skip to main content
Transparent pricing from day one

Office & Ops · Front Office

Every Front-Desk Interaction. One Place to Act

Capture enquiries, welcome visitors, log calls, track post, manage complaints and follow every next action from one live command centre.

Book a Demo See How the Desk Works

Follow-ups stay visible until someone closes them

Priorities, visitors, follow-ups, complaints — one screen.

Today at the desk Live priorities

A source, an owner and a next action on every one.

Enquiry with an owner Follow-ups

Preregister, check in, notify the host, check out.

Visitor checked in Visitor check-in

Received, assigned, acknowledged — with the trail kept.

Post with an owner Private records

Priority, status, target date and who it escalates to.

Complaint in progress SLA and escalation

Everything due, filtered to your access.

One action queue Permission-aware

Why front offices lose time

The Front Desk Shouldn’t Run on Memory.

An enquiry is in someone’s inbox. A visitor is waiting at reception. A call needs a follow-up. A parcel has no owner. A complaint is ageing. The work is connected — the records are not.

The context that decides the next action lives outside the record of the interaction.

  • Enquiries separated from whoever owns them
  • Visitors arriving ahead of their context
  • Postal items with no owner, no acknowledgement
  • Complaints with no target date, no next step

The follow-up nobody owns

Someone promises to call back. The promise lives in a notebook or a memory, so the only way to know whether it happened is to ask them.

Missed follow-ups
An enquiry noted in a mailbox, a notebook and a sticky note, with the promised call-back date written in only one of the three and no owner recorded anywhere

A visitor with no context

A name and nothing else — no host, no purpose, no last visit. The host finds out when the visitor is already at the counter.

Visitors without context
A visitor at a reception counter with only a name on the sign-in sheet, no host, no purpose and no record of a previous visit

Post handed over, not handed off

A parcel is signed for and shelved. Nobody can say whether it was collected, because nothing was written down when it changed hands.

Postal handoffs without ownership
Parcels and envelopes stacked on a shelf behind reception with no recipient assigned, no date recorded and nothing to show whether any of them were collected

A complaint that just ages

Two weeks on, nobody is sure what was agreed or who is handling it. The case is not closed and it is not moving.

Complaints drifting without a next action
A complaint logged three weeks earlier with no current owner, no target date and no next step, beside an email thread that stopped halfway

Meet Academyship Front Office

One Operating Workspace for Every First-Line Interaction.

Academyship Front Office brings enquiries, visitors, calls, postal items and complaints into one permission-aware workspace, so reception can capture what happened, route it to the right person and keep the next action visible.

Incoming work

  • Enquiries
  • Visitors
  • Calls
  • Incoming and outgoing post
  • Complaints

Academyship Front Office

  • Identity and context
  • Owner
  • Priority
  • Next action
  • Files
  • Activity

Kept under control

  • Follow-up scheduled
  • Host notified
  • Visit checked out
  • Postal item acknowledged
  • Complaint progressed
  • Searchable history

How it works

Capture It. Route It. Close the Loop.

Four steps from the moment someone walks in, calls or writes, to the moment the work is finished.

  1. A quick-add panel offering enquiry, visitor, call, postal item and complaint, with the enquiry form open and its source, reference and custom fields shown

    Capture it once

    Log the interaction where it happens — an enquiry, an arrival, a call, a parcel, a complaint — against the right record type, using your own reference data. Custom fields carry whatever else the desk needs to note.

  2. An assignment panel setting the owner, the host or team and the priority on a record, with the record’s source and history visible beside it

    Route it to an owner

    Assign the owner, host or team, and set a priority. The record carries its context, so whoever picks it up sees the source, the history and the attachments without asking reception to repeat the story.

  3. Front-desk actions in progress: a visitor being checked in, a call being dispositioned, a postal item being acknowledged and a complaint status being moved on, each writing to the activity history

    Act on it

    Check the visitor in and notify the host. Record what a call was about and how it ended. Acknowledge a postal item. Move a complaint on. Each action updates the record and its activity history together.

  4. The action queue with a reminder raised before a follow-up is due, an overdue item held in the list and a complaint flagged as approaching its target date

    Follow it through

    Due work stays visible until it is completed, rescheduled or closed. Reminders surface follow-ups before they are late, overdue items stay in the queue, and a complaint approaching its target is flagged while there is still time to act.

What Front Office covers

Five Workspaces. One Reception Rhythm.

Each answers a different question at the desk; all of them write to the same permission-aware record.

01
Command Centre

Start with the enquiries, visitors, calls and cases that need attention today. Permission-aware totals, priorities, one action queue and recent activity give reception a practical opening view.

  • Permission-aware KPIs
  • Today’s priorities
  • Unified action queue
  • Recent activity
02
Enquiries & Follow-ups

Record where each enquiry came from, who owns it and what happens next. Priorities, scheduled follow-ups and due reminders stop conversations from quietly disappearing.

  • Enquiry sources
  • Owner and priority
  • Scheduled follow-ups
  • Reminders before due
03
Visitors & Check-in

Know who is expected, who has arrived and who has left the site. Preregistration, QR check-in, badge issue, host notification and checkout keep every visit traceable.

  • Preregistration
  • QR and badge issue
  • Host notification
  • Check-out
04
Calls & Postal

Turn each call into an outcome and next action while tracking incoming and outgoing post to acknowledgement. Ownership and status make unfinished communication easy to find.

  • Call type and disposition
  • Call owner and follow-up
  • Post received and sent
  • Status and acknowledgement
05
Complaints

Manage every complaint as a case with a clear type, priority, owner and target date. Status, service targets and escalation paths show what needs attention before it drifts.

  • Complaint type
  • Priority and status
  • SLA target
  • Escalation path

Scroll sideways, or use the arrow, Home, End and Page keys.

Live command centre

See What Needs Attention Before Someone Has to Ask.

Counts, priorities and the action queue in one place — every number already filtered to your role.

Front Office command centre with tiles for today’s priorities, visitors in the building, follow-ups due, open complaints, postal items pending and calls logged today, module tabs for enquiries, visitors, calls, postal and complaints, a unified action queue listing an overdue enquiry follow-up, a visitor still in-house, a complaint nearing its target date and a postal item awaiting acknowledgement, a recent activity feed and a quick-add control
1 Counts you can act on Priorities, visitors in the building, follow-ups due, open complaints, postal pending and calls logged today.
2 Move between modules Enquiries, visitors, calls, postal and complaints, without losing your filters.
3 One action queue An overdue follow-up, a visitor still in-house, a complaint nearing its target and a postal item awaiting acknowledgement, in one list.
4 What just happened Recent activity shows who did what, so a shift handover is not a verbal briefing.
5 Add without leaving the screen Quick-add starts any of the five record types from the command centre itself.

Fictional institution, people and interactions, used for illustration. Nothing here is live application data.

01
02
An enquiry record for a prospective parent showing the enquiry source, a matched existing contact with previous interactions, the assigned owner, a priority of High, a scheduled follow-up call and the activity history beneath it

From first contact

From First Contact to the Right Owner —

Capture, identify and assign run the same way for every front-desk record

A call, a walk-in, an email enquiry and a delivered parcel are different events, but the first three steps are the same: capture what happened, identify who it concerns, and assign whoever will deal with it.

Identifying an existing person pulls their history in, so the next action is decided with the previous ones visible.

  • Capture: what happened, in its own record type
  • Identify: who it concerns, and what came before
  • Assign: owner, host or team, with a priority
See the Workflow Rules

Capability example

A complaint case showing the complaint type, a priority of High, a status of In progress, an SLA target date one day away, the current owner, an escalation step to the next responsible role and a restricted attachment on the case

Through to finished

Act, Follow Up, Close and Retain —

The loop closes only when the next action is completed, rescheduled or closed

Acting is the visible part: a visitor checked in, a call dispositioned, a postal item acknowledged, a complaint moved on. Following up is the part that goes missing, so due work stays in the queue and surfaces before it is late.

Closed is a state, not a deletion: the record, its attachments and its history stay searchable under the retention policy you set.

  • Act: check in, respond, acknowledge or resolve
  • Follow up: due work stays visible until it is finished
  • Close and retain: history kept, retention applied
See Who Can Do What

Capability example

01
02

What stays organised

Every Interaction Leaves the Right Record Behind.

Not a log of what reception typed, but records the rest of the institution can find and act on later.

A visitor visit record showing a preregistered visitor, the purpose of the visit, the host, a QR check-in at ten seventeen, the badge number issued, the host notification that was sent and an open check-out step
A postal item record showing an inbound parcel logged at reception, the assigned recipient and department, the postal status moving from received to awaiting collection, and a timeline ending in the recipient’s acknowledgement
The unified action queue listing front-desk work that is due, each row showing the record type, the person it concerns, the owner, the due date and whether it is due today, overdue or approaching its target

People & interactions

  • Enquiry profile — Record
  • Visitor visit — Record
  • Call log — Record
  • Badge issued — In app
  • Host notification — In app

Movement & cases

  • Postal chain — Timeline
  • Complaint case — Record
  • Escalation step — Timeline
  • Private evidence — File
  • Linked records — Record

Actions & accountability

  • Owner — Field
  • Next action and due date — Field
  • Reminders — In app
  • Status and activity history — Audit
  • Archive and retention — Policy

Attachments are served privately: a file is reachable through the record and the permissions on it, never from a public link.

Configurability

Set the Front Desk Up Around the Way You Work.

Reference data, workflow rules and the working view are set once and used every day.

Front Office settings showing reception reference data: enquiry sources, reference formats, visitor purposes, complaint types, call types and dispositions, and the custom fields defined for each record type
Front Office settings showing workflow rules: statuses and priorities per record type, default owners, reminder timing before a follow-up is due, complaint SLA targets with an escalation path, postal states and the retention policy
Front Office settings showing experience controls: saved views, notification preferences, quick actions available from the command centre, default filters and the permission-aware options that vary by role

What any one person can change depends on their role and your permission set.

Right access, right responsibility

Give Each Front-Office Role Exactly What It Needs.

Permissions are set per module, so the desk, its managers and its administrators each see a different amount of the same workspace.

Responsibility group

Reception team

The counter captures the interaction and keeps its own assigned work moving.

  • Capture enquiries, visits, calls, post, complaints
  • Check visitors in and out, notify hosts
  • Update work assigned to them
What limits this
Module permissions decide which records reception can open, and restricted attachments stay restricted.

Responsibility group

Managers

Managers watch the queues rather than individual records.

  • Oversee queues across modules
  • Reassign owners, change priority
  • Watch overdue follow-ups and SLA targets
What limits this
Oversight follows the same permission set, and every reassignment is recorded.

Responsibility group

Administrators

Administrators set up what everyone else works inside.

  • Configure reference data and custom fields
  • Set statuses, priorities, reminders, SLA rules
  • Manage retention and per-module permissions
What limits this
Configuration changes are recorded too, so a rule change traces to whoever made it.
Front Office command centre with tiles for today’s priorities, visitors in the building, follow-ups due, open complaints, postal items pending and calls logged today, module tabs for enquiries, visitors, calls, postal and complaints, a unified action queue listing an overdue enquiry follow-up, a visitor still in-house, a complaint nearing its target date and a postal item awaiting acknowledgement, a recent activity feed and a quick-add control

A Monday morning

A visitor still in from Friday, an overdue follow-up and a complaint on its final day — all three on the command centre before anyone opens a module.

Counts are filtered by role, so one desk can show two totals.

A visitor visit record showing a preregistered visitor, the purpose of the visit, the host, a QR check-in at ten seventeen, the badge number issued, the host notification that was sent and an open check-out step

An expected visitor

A preregistered visitor arrives, is checked in against the existing record, gets a badge, and the host is notified — without leaving the screen.

Until check-out, the visitor stays counted as in the building.

A complaint case showing the complaint type, a priority of High, a status of In progress, an SLA target date one day away, the current owner, an escalation step to the next responsible role and a restricted attachment on the case

A complaint that escalates

A complaint passes its target date, is flagged, and escalates to the next responsible role — written into the case, not agreed in a corridor.

Escalation follows the configured rule, not whoever is on shift.

Closer in

Six Capabilities That Keep the Desk Ahead of the Queue.

Six controls, and the front-desk failure each one is there to prevent.

  • An enquiry pipeline showing enquiries grouped by status with their source, owner and next follow-up date

    Enquiry pipeline & follow-ups

    Source, owner, priority and next action on every enquiry — with a reminder before the follow-up is late, not a report after it.

  • A visitor check-in panel with a preregistered visitor, a QR scan, the badge about to be issued and the host notification that follows

    Visitor check-in & host notification

    Preregister, check in by QR or at the counter, issue a badge, notify the host, check out. Who is in the building becomes a number you trust.

  • A call log entry with the caller, the call type, the disposition chosen, the owner and a follow-up scheduled from the call

    Call logs & next actions

    What the call was about, its disposition and who owns it. A callback becomes a scheduled follow-up, not a note.

  • A postal tracking row showing an inbound item, its assigned recipient, its current state and the acknowledgement still outstanding

    Postal tracking & acknowledgement

    A recipient, a status and a timeline ending in an acknowledgement — so a shelf is never the only evidence.

  • A complaint row showing its type, a priority of High, the days remaining against the SLA target and the escalation flag that has been raised

    Complaint cases, SLA & escalation

    A type, a priority, a status and a target date. As the target nears, the case is flagged and escalated on your configured path.

  • A global search across front-desk records with results from enquiries, visits, calls, postal items and complaints, and a list of saved views beside them

    Global search, saved views & one action queue

    Search every front-desk record, keep your morning filters as saved views, work everything due from one queue.

Questions

Front Office Questions, Answered Fast.

The practical questions reception teams and their managers ask first.

What is Front Office, and what can it track?

One workspace for first-line interactions: enquiries, visits, call logs, post and complaint cases. Each is a record with an owner, a priority and a next action.

How do enquiry and call follow-ups work?

A follow-up is a next action with an owner and a due date. A reminder surfaces it early, and it leaves the queue only when someone completes, reschedules or closes it.

Can we see who is still in the building?

Yes. A visitor counts as in-house from check-in until check-out, and the command centre shows that count beside the visits behind it.

How are postal items tracked?

An item is recorded when it is received or sent, assigned to a recipient, and moved through your configured postal states until it is acknowledged.

How are complaints managed?

As cases, with a type, a priority, a status, an owner and an SLA target. As the target nears, the case is flagged and escalation follows the configured path.

Can access differ by role?

Yes. Permissions are set per module, so reception, managers and administrators see different amounts of the same workspace — counts included.

Can we customise the lists, and what happens to old records?

Sources, visitor purposes, complaint types, call types and dispositions and postal states are reference data you configure, and custom fields capture the rest.

Archived records are kept: attachments and activity history stay searchable, a soft-deleted record can be restored, and retention follows your policy.

Related Products

Who the caller is, who may see the record, and what is already scheduled.

Who the enquiry is about

Student Management

The student record the rest of the institution already reads from.
Who may see what

Roles & Permissions

The per-module permissions behind every Front Office record and count.
What is already scheduled

Events & Calendar

Events, rooms and bookings — the context behind an expected visitor.

Front Office, without the loose ends

Put the Front Desk on One Live System.

See how Academyship keeps enquiries, visitors, calls, post, complaints and follow-ups moving from first contact to finished action.

Book a Demo See Pricing

Live priorities and follow-ups

Visitor check-in and check-out

Permission-aware, private records

A front-desk record moves through six stages

  1. Capture
  2. Identify
  3. Assign
  4. Act
  5. Follow up
  6. Close & retain