AdverDia Group / Nassau, The Bahamas
In virtually every restaurant, the person with the most influence over the guest experience is the server. Their performance is the least measured thing in the building.
A guest presses. The clock starts. The assigned server clears it on arrival, and that elapsed time is the backbone of everything else.
Logged
Ask any GM who their best server is and you get a confident answer in two seconds. Ask them to prove it with a number and the room goes quiet.
That isn't a management failure. Food cost, waste, labour percentage, ticket times, cover counts and average check are all tracked to the decimal, because the tools exist to do it. For the floor, they don't. So it gets assessed through three unreliable channels.
“How is everything?” Guests are polite, the sample is tiny, and it's biased toward whichever tables a manager happens to reach.
Someone has to be unhappy enough to speak up. Most never come back and never say why. You lose the customer and the lesson.
Pooled, lagging, skewed by check size. A weak server on a great table still looks fine on paper, and you find out weeks later.
What gets measured gets managed. The floor is barely measured, so it's coached on feel, rewarded on tenure, and corrected only after the guest is already gone.
Two instruments sit inside the same object. One reads your operation, one reads your guest. They measure different halves of the same dinner, and neither substitutes for the other.
Measures response
The button is fact. It happened or it didn't, and the clock doesn't have an opinion.
Measures satisfaction
The QR is judgment. It's how the guest scored you, in their own words.
Fast service that guests didn't enjoy is a kitchen problem. Slow service that guests forgave is a staffing problem. You cannot tell those apart with one instrument.
The button sits inside an object that belongs on your table. Custom manufactured, finished to match your room. The QR panel is designed into the same piece rather than propped against the salt.
Dinner service, low light.
Brunch, terrace, garden rooms.
Counter service, pool, casual.
Fine dining, cabanas, day beds.
Material, finish and form are specified per outlet. A steakhouse and a beach bar don't get the same object.
Weighted, wipeable, and heavy enough not to walk. Charged on a cycle your team can run alongside candle service.
Etched or printed into the object itself, so it reads as part of the setting rather than as a table tent.
Nothing works until each press is tied to the right server. BUTN takes that link from the check, which means nothing new to maintain during service.
The clock starts and the request routes to the server assigned to that table.
When a server opens a check on a table, your POS already knows who is responsible for it. The press scores against that server automatically. Nobody has to build a section map, update it on cuts, or maintain it through breaks. Where a POS connection isn't available, sections can be assigned by hand instead.
Cleared at the table, which stops the clock and logs the elapsed time against the table and the server.
Your kitchen got faster when ticket times went on a screen. Nobody had to be lectured about it. Measure the floor, show it the same way, and service improves before management has to intervene. Then measure again and prove it moved.
A rating at or below your threshold pushes straight to the manager on duty with the outlet and table number attached. They walk over. They fix it. The guest leaves having been looked after instead of leaving quietly and never coming back.
Every alert and every intervention is logged, so you can see how many were actioned and by whom rather than assuming it happened.
Ember & Tide / Table 14 / Section B
Food was great but we waited a long time for drinks and had to ask twice.
Actioned 8:47pm by D. Rolle
Ratings are a number. What guests write is where the information is, and today it dies in a spreadsheet nobody opens. Every response is sorted into stable categories — food quality, service speed, staff courtesy, cleanliness, atmosphere and value — so the data stays trendable. Emergent detail sits underneath, so a spike about one dish or the music volume is still visible.
141 responses, average 8.6, up from 8.3. Problem incidence 9.2%, down from 11.8%. Six recovery alerts fired, five actioned at the table.
| Dimension | Mentions | Direction | Sentiment |
|---|---|---|---|
| Staff courtesy | 47 | up | Positive |
| Service speed | 31 | up | Negative |
| Atmosphere | 18 | flat | Mixed |
| Food quality | 11 | down | Negative |
Connected issue
Service-speed comments are almost entirely about the first drink, not the food, and cluster on Friday and Saturday second seating. Response times run above this room's own baseline in the same window and problem incidence hits 17%, nearly double the average. Points to bar throughput or floor coverage on those two shifts.
Emergent theme
Food-quality mentions concentrate on two dishes and have fallen since the 3 May menu change.
Reported weekly for a single room and daily across a property, and suppressed below a minimum sample so a summary is never built on a handful of comments. Sample data shown.
One screen in the service area carries the open requests, the state of every position, and the shift's top performers. Servers start racing each other because the metric is visible, individual and fair. The board shows the top and the shift average; anything below that goes to the manager's dashboard, privately.
Open requests — 4
Floor — 34 positions
Section A
Section B
Terrace
Tonight's top
Open requests — 3
Zones — 68 positions
Cabanas 1–12
Pool row A — 28
Beach row B — 28
Today's top
The same layout carries a dining room, a cabana row or two hundred lounge chairs. Sample data shown.
A single-room owner and a resort F&B director ask the identical question at the end of service: who was fast, who wasn't, and what did the guest think about it. The only difference is how many rows are in the report.
Service closed 10:41pm
Presses
147 / 112 coversAvg response
2:38 down 0:03Timed out
2 / 147Recovery alerts
2 / 2 actionedSecond seating, 8:15 to 9:30pm
Response ran 0:36 above this room's own baseline. Nine of the twelve slowest presses of the night fell in that window.| Server | Avg | Under 60s | Repeat | Peak | Score |
|---|---|---|---|---|---|
| Maria | 0:42 | 94% | 3% | +0:08 | 92 |
| Tanya | 1:01 | 81% | 7% | +0:24 | 84 |
| James | 1:28 | 63% | 14% | +1:11 | 68 |
| Shift average | 1:04 | 79% | 8% | +0:34 | 81 |
Read the last two columns together. James isn't just slower on average; he's asked twice more than four times as often as Maria, and he falls apart at peak. That's a coaching conversation with specifics in it. Scores are normalised for section size and table count, so a server working twelve busy tables is never ranked against one working four quiet ones. Sample data shown.
12 rooms live
Avg response
3:12 down 0:14Problem incidence
10.4% down 1.9Recovery alerts
38 / 31 actionedResponses
1,204Both improving — 7
Working. Leave them alone.Fast, not happier — 3
Floor is quick, guests aren't. Look at the kitchen.Both slipping — 2
Staffing or coaching. Start with the leaderboard.| Room | Response | vs own baseline | Repeat | Rating |
|---|---|---|---|---|
| Ember & Tide | 2:41 | down 0:18 | 3.1% | 8.6 |
| Sea Glass | 3:04 | down 0:11 | 4.0% | 8.2 |
| Cabana Grill | 3:55 | down 0:07 | 5.4% | 7.1 |
| Coral Lounge | 3:48 | up 0:09 | 7.2% | 7.0 |
| The Reef Room | 4:10 | up 0:12 | 8.9% | 6.8 |
Every room is measured against its own prior baseline rather than ranked against the others, because a poolside grill and a fine-dining room run different service rhythms. Seven further rooms sit within five seconds of baseline. Sample data shown.
Your property makes real decisions on annual third-party guest satisfaction studies. They're credible, externally comparable and worth the attention they get. They're also slow: a full year of guest stays, published months after that window closes. A dinner that disappointed someone in June can surface the following July.
BUTN is the leading indicator for the same two dimensions your F&B leadership is already accountable for, food and beverage and staff service, reported from your own rooms while the year is still in play. And it tells you something no property-level score can: which room is responsible. A single score for the property is a verdict. A score per room, per shift, per day, is a plan.
We install in a single high-visibility restaurant, train your managers, and run for a full quarter. At the end you get a before-and-after on response times, repeat presses, timeouts, guest ratings, problem incidence and recovery alerts actioned, set alongside your own covers and average check across the same window.
If the numbers move, expand. If they don't, you've spent one quarter finding out.