Skip to content
Concept · hotels · Tier 1Platform

Hotel Operations Command Center

A 40-room independent hotel running one property, taking bookings by phone, walk-in and one or two online channels. Front desk keeps a paper book. Housekeeping uses a whiteboard. Payments arrive as cash, transfer and card. Occupancy reporting is manual.

The reality

A 40-room independent hotel is growing past what phone calls and a paper book can coordinate. Reservations arrive by phone, walk-in and one or two online channels. The front desk keeps a paper book. Housekeeping works from a whiteboard. Payments come in as cash, transfer and card, reconciled by hand at the end of the day.

Where it breaks

  • A booking taken by phone doesn't reach the housekeeping whiteboard until someone walks over and says so.
  • Channel bookings arrive on their own schedule, so the desk book and the actual channel availability can disagree for hours at a time.
  • A disputed bill has no record to settle it against beyond a memory of who authorised what.
  • The night audit is built from what the front desk remembers doing that day, not from what actually happened.
  • Occupancy and revenue for last week exist only if someone sits down and adds up the desk book by hand.

The Afivox approach

Afivox doesn't start by proposing a booking system. It starts by mapping how a reservation actually moves through this property — from the moment it's taken to the moment the room is turned, billed and closed out — and builds the system around that path, not around a generic hotel template.

The system

Users

Front desk, housekeeping, management, accounts

Application

Reservations, front desk, housekeeping

Services

Rates and inventory, payments and billing, night audit

Data

Property → RoomType → Room → Reservation → Stay → Folio

Integrations

Booking channels, bank statement import

Security

Roles, permission matrix, audit log

What it looks like

Concept mockups — illustrative interfaces, not a built system.

Executive operations dashboard

82%

Occupancy

14

Arrivals today

11

Departures today

31

Rooms ready

3

Rooms blocked

5

Open maintenance

7

Guest requests

₦38,400

ADR

Live room grid

Housekeeping — mobile

Assigned to you — 3 rooms

Room 108

Checkout clean

Room 214

Checkout clean

Room 302

Stay-over service

Maintenance queue

RoomIssuePriorityTechnicianStatus
Room 118Air conditioner not coolingB. Emeka
Room 214Bathroom tap drippingUnassigned
Room 305TV remote missingC. Ibe

Guest request center

Management analytics

₦31,500

RevPAR

79%

Occupancy (30d)

34%

Channel share

How it flows

Reservation
Room assigned
Housekeeping
Inspected
Ready
Check-in
Guest request
Resolved

Secure by design

  • Roles for owner, manager, front desk, housekeeping, accounts and maintenance, each seeing only what their role needs.
  • A permission matrix controls who can apply a discount, void a charge or override a rate.
  • Every discount, void and rate override is logged with a name and a reason — never anonymous.
  • A full audit log, searchable and exportable, that is never itself editable.
  • Room status and stay status are kept as separate fields at the data level, so a room can't be recorded as occupied and clean at the same time by mistake.

Designed to improve

  • Operational visibility — front desk, housekeeping and every booking channel work from one shared picture of availability.
  • Response time — a room turning clean is visible to the desk the moment it happens, without a phone call.
  • Accountability — every charge, discount and void carries a name and a timestamp, so a disputed bill is settled from the record, not from memory.
  • Reporting speed — occupancy and revenue for any period are on screen, not assembled by hand at month end.

Before

  • The desk keeps its own book. Housekeeping keeps its own whiteboard. The two only agree when someone walks between them.
  • A guest complaint reaches the front desk, who has to call housekeeping, who has to check the room, before anyone can respond.
  • A disputed bill gets settled by whoever remembers the conversation, not by a record.
  • Occupancy and revenue for last month get worked out by hand, days after anyone needed the number.

After

  • The desk, the housekeeping floor and every booking channel see the same availability at the same moment.
  • A guest request enters the system once and reaches the right person directly, with its status visible to the desk throughout.
  • Every charge, discount and void carries a name and a timestamp, so a disputed bill is settled from the record.
  • Occupancy and revenue for any period are on screen the moment someone wants them.

Your operation probably has a workflow like this.

One session. We look at what's breaking, and what we'd build around it — whether or not you hire us afterward.

Tell us where yours breaks