How to measure a hotel reservations team: six metrics and a team scorecard

Ask a reservations team "how many bookings did you take this month" and the team gives a number and the conversation ends. That number measures the month's demand, not the team's performance. In high season everyone takes plenty of bookings; in low season even the best team takes few. Count shows what the market did, not what the team did.

This article covers the six metrics that actually measure a reservations team, a fictional monthly team scorecard, where the data comes from, and the four mistakes I see most often. By "team" I mean the reservations agents answering the phone and the e-mail; front-desk selling after check-in is a separate subject.

Why count is not enough

Booking count hides two problems. First, it presents demand as the team's achievement: thirty bookings from a hundred enquiries and thirty from three hundred are the same count, but the first is a good team and the second is a serious loss. Second, a team given a count target hits it the easiest way: discounting. Count goes up, achieved rate goes down, nobody notices.

Proper measurement starts from the enquiry. How many people asked, how many booked, at what rate, why the others did not, and how many were followed up — the six metrics fall out of those questions.

The six metrics

1. Conversion rate

This is the team's headline metric. It must be kept by channel, because a phone enquiry naturally converts better than an e-mail; mixing them makes you think the team improved or declined whenever the channel mix shifts.

2. Response time

The time to first reply on e-mail and form enquiries. The guest sends the same enquiry to several hotels; the first to answer starts ahead. The target is one hour. On the phone there are two numbers: average answer time and the missed-call rate. A missed call is not counted as an enquiry, so it never shows in conversion — a loss that is ignored unless it is measured.

3. Achieved rate against BAR

A count bonus encourages discounting; this metric makes discounting visible. If the team's average sold rate falls below 85% of BAR for those dates, then even with a high conversion rate the team is not selling, it is cutting price. The two metrics are read side by side.

4. Upsell revenue

Additional revenue per booking: room upgrade, breakfast, late check-out, transfer, package. Revenue from extras offered during the enquiry divided by the number of bookings. When this is zero the cause is usually not the team's reluctance but the absence of a system to offer from — if which guest gets which offer is not written down, nothing is offered.

5. Lost-enquiry reasons

One-word reason for every enquiry that did not book: rate, dates (no availability), room type, late reply, unreachable, other. At month end this breakdown shows the team what to fix. If most losses are logged as "dates", the problem is inventory, not the team; if "late reply", go back to the response-time metric; if "rate", first check whether an alternative was offered.

6. Follow-up rate

What share of guests who enquired and did not book were contacted again? In most hotels the figure is zero, because follow-up is in nobody's job description. A guest who took a quote and did not decide is not lost; a one-line message the next day ("we are holding the room for the dates you asked about") has a measurable effect on conversion. The follow-up rate rises the moment it starts being measured.

Example: Sample Hotel's monthly team scorecard

The figures below are fictional and do not belong to any real property. Sample Hotel has 120 rooms in a city centre; a three-person reservations team handled 640 enquiries in a month.

The scorecard tells one story: e-mail conversion fell, response time tripled, and "late reply" moved to the top of the lost reasons. Three metrics point at the same place. A hotel measuring count would close this month with "bookings dipped a bit, that's the season"; the scorecard instead asks the team what happened that month — most likely someone was on leave and the inbox had no owner.

The scorecard earns its keep the moment the metrics explain each other. One metric gives a finding; six metrics give a cause.

Where the data comes from

The PMS holds bookings, not enquiries. So most of the six metrics need a record outside the PMS. The simplest and most durable method is a shared table in which the team enters every enquiry as a single line:

The table is summarised once a month; the scorecard comes from that summary. If there is a CRM or a call-logging system, the same columns are kept there — the columns matter, not the tool. Filling the table looks like a burden to the team; two weeks later the team clings to it as its own defence, because for the first time it can answer "you took few bookings" with "few enquiries came in", backed by data.

The four most common mistakes

1. A bonus on count

A bonus tied to booking count rewards discounting. Tie it to conversion and achievement against BAR; count can be a component of the target but not the target itself.

2. Training without measuring

Sales training is bought and the result is never measured. The scorecard for the two months before training is the baseline, the two months after are the result; if there is no difference, the problem is not the training content but the absence of follow-up afterwards.

3. Not counting missed calls

A missed call is not counted as an enquiry, so it does not touch the conversion rate; the team looks fine and the hotel loses guests. Without a switchboard log, even having the team count every call by hand one day a week makes this loss visible.

4. Not treating follow-up as a task

If contacting a guest who enquired and did not book is nobody's job, nobody does it. Follow-up starts happening once it is written into the job description and the scorecard; unmeasured behaviour is absent behaviour.

How to set it up in your own hotel

1. 01Open the enquiry table: seven columns, one shared file. On day one agree the five lost reasons with the team; keep the list short.
2. 02Spend the first month only measuring; set no targets. This month's figures become the baseline.
3. 03At the start of month two share the scorecard with the team and pick two metrics — usually response time and follow-up rate, because both change with behaviour immediately.
4. 04If there is a bonus, review its metric: conversion and achievement against BAR instead of count.
5. 05Every quarter add the scorecard to the management report; the team metrics fill the "team decision" row of the KPI map.

Related concepts

• BAR — the reference the achieved rate is compared against.
• Upsell / Cross-sell — the subject of the fourth metric; how to build it as a system is a separate article.
• Hotel KPI list — where team metrics sit in the five-decision map.
• Phone booking conversion — the phone side of the first metric; the subject of a separate article.
• Bonus schemes for reservations teams — which metric to tie them to; the subject of a separate article.

Summary

1. 01Booking count measures demand, not the team; measurement starts from the enquiry.
2. 02Six metrics: conversion, response time, achievement against BAR, upsell revenue, lost reasons, follow-up rate.
3. 03Conversion is kept by channel; phone and e-mail are not mixed.
4. 04Without a rate-discipline metric, high conversion hides discounting.
5. 05Data is collected in a seven-column enquiry table, not in the PMS.
6. 06Bonuses are tied to conversion and achieved rate, not count; follow-up is written into the job description.