Service Robots in Hotels: Where the ROI Is Real and Where It Is Theater

Delivery and cleaning robots are past the novelty phase, and the results are uneven for reasons that have almost nothing to do with the robots. Payback is decided by your elevators, your floor plate, your delivery volume, and whether you actually reallocate the labor you free up. Here is how to tell the two categories apart before you sign.

A delivery robot that can't get into an elevator on a sold-out Saturday ends up parked in a back corridor under a dust sheet. An autonomous scrubber that runs a mapped route through a lobby every night tends to stay, and after a while the housekeeping team stops thinking of it as technology at all.

The difference between those two outcomes is rarely the robot. It's the building, the volume, the integration work that was done or skipped before the unit arrived, and whether anyone wrote down what the freed-up hours were supposed to be spent on. This piece is about telling the two apart before you commit capital.

That's uncomfortable for enthusiasts and skeptics alike. Some categories of hotel robot are boring and do a measurable job. Others are theater, and the fact that they photograph well in a press release is exactly the problem. A GM who can't say which category a proposed unit falls into, and why, shouldn't be signing the lease.

The Market Has Already Sorted Itself, If You Read the Numbers Correctly

The International Federation of Robotics counted more than 42,000 professional hospitality robots sold worldwide in 2024, down 11 percent on 2023. Read in isolation, that looks like the category losing steam. Read against the rest of the same report, it looks like something more useful: a market shaking out its novelty tier. The IFR notes that mobile guidance, information-point, and telepresence units make up the majority of the hospitality count, and those are the categories with the weakest operating case. Across professional service robots as a whole, the IFR says the robot-as-a-service rental fleet grew 31 percent, as more companies choose subscription over an upfront purchase. That fits a buyer who wants to pay per month, measure, and cancel if it doesn't work.

Analyst forecasts for the segment run from $0.9 billion in 2026 (The Business Research Company) to $2.23 billion by 2031 (Mordor Intelligence), with compound growth of about 24 percent a year. Mordor lists post-pandemic labor shortages as the biggest single driver. Hotels can't hire. The American Hotel & Lodging Association found 65 percent of surveyed US hotels reporting shortages in a survey run from December 2024 to January 2025, with housekeeping the most-cited department at 38 percent and front desk second at 26 percent. AHLA's March 2026 follow-up found more than half of respondents still somewhat or severely understaffed, and about 70 percent saying hotels are offering higher wages to recruit and keep staff.

That is the honest case for robots in hotels. It is not that a machine is cheaper than a person who wants the job. It is that in a growing number of departments there is no person who wants the job at a wage the P&L can absorb, and the alternative to automating the task is not doing it. The Skift analysis of why robots have penetrated Chinese hotels far faster than American ones is useful here. It names three reasons robots are unlikely to spread widely in US hotels even as they thrive in markets like China: cultural concerns, cost and labor dynamics.

Four Categories, Four Very Different Investment Cases

The phrase "hotel robot" covers machines with almost nothing in common beyond a chassis and a lithium battery. Before any ROI conversation can be useful, the category has to be named, because the payback math, the failure modes, and the prerequisites are different for each.

Autonomous floor care is the category with the deepest deployment history. These are commercial scrubbers, sweepers, and vacuums that run a mapped route through public space, typically overnight, with a human operator for setup and edge cleaning. The technology is mature, the vendors are established, and the value proposition is simple: hours of floor coverage that no longer need a person standing behind the machine.

Room delivery robots carry amenities, forgotten items, and F&B orders from a dispatch point to a guest room door, ride elevators autonomously, and phone the room on arrival. This is the category most people picture, and it is the one with the widest variance in outcomes.

F&B running and bussing robots operate inside a restaurant or banquet footprint, carrying plates from the kitchen pass to a table station and returning dirty dishes. They do not use elevators, they do not leave the outlet, and they are increasingly common in high-cover-count venues.

Front-of-house concierge and reception robots greet, answer questions, and in some cases process check-in. This is the category that produces the most video and the least measurable return.

The vendor literature is more optimistic. RobotLAB, which bills itself as America's largest robotics integrator, puts payback "on the order of one to two years," depending on wage rates, hours of use, and whether you buy or subscribe. Its floor-care material quotes an hourly operating cost as low as $0.41 for a cleaning robot against more than $7 for manual labor. Those numbers describe the property where everything went right. Most of what follows is about why plenty of properties aren't that one.

What Actually Determines Payback

Strip out the marketing and the ROI of a hotel robot reduces to four variables. Two of them are about the building, one is about demand, and one is about management discipline. The robot itself barely appears.

Elevators and Floor Plate

A delivery robot that cannot call, enter, and exit an elevator reliably on its own is a very expensive cart. Modern integrations solve this in software: Otis Integrated Dispatch and the KONE Service Robot API connect service robots to the elevator through an API (Otis offers it cloud-based or on-premise), and Relay Robotics says its own cloud-based integration works with elevators from Otis, Schindler, TK, Mitsubishi and KONE. That's the good news.

The bad news is that an older elevator, or one whose controller was never modernized, may need a hardware retrofit before any of that software has something to talk to. Retrofit cost varies enormously and is often not in the robot vendor's quote, because it is not the robot vendor's scope. A property with two elevators serving 200 rooms across twelve floors also has a capacity problem the robot does not solve: at peak checkout, the robot is competing with guests for cars, and every minute it spends waiting is a minute of delivery latency that guests will notice and staff will complain about. Low-rise, wide-footprint properties with one or two floors of rooms and generous corridors are the easiest environment for delivery robots. High-rise towers with tight elevator banks are the hardest.

Floor care has its own version of the same constraint. Autonomous scrubbers earn their keep on long, open, hard-surfaced runs: lobbies, pre-function space, casino floors, convention corridors, parking structures. They do not earn it on a floor plate broken up by tight furniture groupings, level changes, and carpet transitions every twenty feet, because the operator ends up doing the edges by hand and the autonomous hours per shift, which is the metric that matters, collapse. Brain Corp, which says its software runs more than 50,000 autonomous robots, puts autonomous cleaning coverage, autonomous usage percentage and autonomous hours per day at the top of its list of cleaning KPIs for exactly this reason.

Delivery Volume

A delivery robot has a fixed cost and a per-delivery value. Below a volume threshold it never pays back regardless of how well it works. The threshold is easy to estimate and rarely estimated. Count the amenity deliveries, forgotten-item runs, and in-room dining drops your property actually makes in a week, then divide by seven. As a rough illustration, a 150-room select-service hotel with no restaurant might run ten a day, and a 400-room full-service property with room service and an active convention book might run eighty. The robot is the same price for both.

This is why F&B runners tend to have the cleanest payback of any category. A restaurant doing 250 covers a night generates hundreds of pass-to-table trips per shift, the route is short and flat, and the robot is fully utilized from the first day. It is also why the concierge humanoid almost never pencils: it has no volume metric at all.

Labor Reallocation

This is the variable nobody models and everybody gets wrong. A robot does not write a check. It frees hours. Those hours turn into money only if one of three things happens: an open position is left unfilled, a scheduled shift is removed, or the freed time is redeployed to work that measurably generates revenue or reduces cost elsewhere. If none of those happens, if the floor attendant who used to run the scrubber now stands next to it, the robot is a pure cost and every ROI slide in the vendor deck is fiction.

The reallocation has to be decided before the robot arrives, written down, and checked quarterly. In practice the strongest outcomes come from properties that already had a vacant position they had failed to fill, because the saving is immediate and requires no difficult conversation. The weakest come from properties that were fully staffed, bought a robot on the promise of efficiency, and discovered that nobody was willing to cut a shift.

Maintenance and Uptime

Robots break. Wheels wear, sensors drift, batteries degrade, and a software update occasionally takes a unit offline for a morning. A robot that's often unavailable can be worse than no robot, because the team stops relying on it and builds a manual workaround that then runs alongside the machine. The payback model below assumes 90 percent uptime, and that only holds for a property that owns the maintenance calendar instead of waiting for something to fail.

The robot is not the investment. The elevator integration, the reallocated shift, and the maintenance calendar are the investment. The robot is just the part that shows up in the photograph.

The Payback Model, Worked

Here is the arithmetic for a delivery robot at three property types, using the same unit at a $1,200 monthly lease, all-in, including software and support. Loaded labor cost is taken at $22 an hour, which is the BLS mean wage for maids and housekeeping cleaners of $16.66 an hour (May 2023) plus a benefits and turnover load. The robot is assumed to run 90 percent uptime after a ninety-day stabilization period.

Three observations fall out of that table. First, the select-service property should not buy the robot, and no amount of vendor enthusiasm changes that: at ten deliveries a day the labor it displaces doesn't cover the lease. Second, the mid-size full-service property is where the category shines, because volume is meaningful and the vertical stack is manageable. Third, the convention hotel has the best gross case and the highest execution risk, because 22 floors on a shared elevator bank at peak is precisely where robots stall, and "if elevators cooperate" is doing a lot of work in that final cell.

Floor care is simpler. Take a property spending 30 labor hours a week scrubbing hard-surface public areas. If one autonomous unit takes most of those hours, at $22 loaded that's up to about $2,860 a month of labor, so an all-in lease well under that figure leaves room for the operator's setup and edge work. The saving holds up because floor cleaning is one of the few hotel tasks that doesn't need a person present for most of its duration.

Why Some Deployments Are Theater

The Henn na Hotel in Nagasaki opened in 2015 as the world's first robot-staffed hotel and became the most instructive robot failure in the business. As Hotel Management and Forbes reported in 2019, the property cut more than half of its 243 robots after finding they created more work than they saved. The in-room assistant, Churi, couldn't keep up with guests' questions and woke one guest every few hours by mistaking his snoring for a request. The front-desk robot couldn't answer basic questions. Robots broke down often, and staff worked overtime fixing them. The AI Incident Database catalogues the episode, including robots that couldn't make passport copies without a human stepping in.

Henn na said it would keep robots where they had proved effective, and the one Forbes singled out as a success was a mechanical arm that stores and retrieves luggage. A narrow, repetitive, physical job in a controlled space. That's most of the lesson. The test for theater is not whether a robot is impressive. It is whether its job could be written on an index card and whether, if it failed at that job, anyone would notice by the numbers rather than by the complaints.

The academic work points roughly the same way, with caveats. A Cornell Hospitality Quarterly review of service robot applications, built on interviews with managers rather than guests, found robots either support or substitute for employees, and that executives have to balance efficiency against what customers expect. UCF Rosen College research across 11 countries found that both utilitarian value, the sense that the robot did something useful, and hedonic value, the enjoyment of it, predicted whether guests intended to use service robots.

The right-hand column is not a list of bad people making bad decisions. It is what happens when a purchase is driven by how a hotel wants to be perceived rather than by a task that needs doing. The tell is almost always the last row: if the person most excited about the robot does not run the department it will live in, the department will not adopt it.

Deployment Prerequisites, By Category

The difference between the robot under the dust sheet and the robot the housekeeping director will not give back is almost entirely in the work done before delivery. This is the checklist, and it should be complete before a lease is signed, not after.

Two rows deserve emphasis. The Wi-Fi survey sounds trivial, so it gets skipped. Elevator cars are metal boxes, plenty of hotel networks were never designed to hand a moving device cleanly between floors, and a robot that loses its connection mid-route just stops. And the integration row is where the ROI compounds or leaks: a delivery robot that has to be dispatched by a front-desk agent walking to the back of house and loading it is saving far less than one that receives the amenity request directly from the guest messaging platform, is loaded by a runner on the way past, and logs its own completion to the task system. Properties that treat the robot as a standalone appliance get standalone-appliance returns. Those that wire it into the operating stack, which is usually a modest project relative to the hardware, get the returns in the vendor deck. This is typically the point at which a custom integration and automation build is a smaller line item than the robot itself while deciding whether the robot produces value at all.

The Guest Question, Answered Honestly

Operators worry that a robot in the corridor signals a cheap hotel. For functional units the evidence doesn't back that up, though most of it is thin. RobotLAB describes guest response as generally positive, which is a vendor talking. In 2014 Starwood's Aloft brand put Savioke's Botlr delivery robot into its Cupertino hotel as a pilot, and the brand's senior vice president told NBC News it could go enterprise-wide if it worked. A 2025 Frontiers in Robotics and AI study of 400 Gen Z guests in China who had used hotel delivery robots found that the robots' service quality (assurance, entertainment value, how humanlike they seemed, and their physical presentation) drove whether guests wanted to keep using them. Reliability, oddly, didn't register.

The practical rule is that a robot bringing extra towels to the door at 11pm is a service upgrade, because the alternative was a fifteen-minute wait for a night porter who was also covering the desk. A robot standing in the lobby trying to make conversation is a downgrade, because the alternative was a human who could actually help. Guests are not confused about which is which, and neither should owners be.

Guests do not resent a machine that brings them a toothbrush in six minutes. They resent a machine that stands between them and a person who could have helped.

Buy, Lease, or Wait

Hospitality unit sales fell 11 percent while the IFR's robot-as-a-service fleet grew 31 percent across professional service robots. Read that as a hint, not proof, but it points the same way as the arithmetic: lease first. A monthly RaaS arrangement converts a capital decision into an operating experiment, keeps the maintenance obligation with the vendor, and allows a property to run the payback test for real rather than on a spreadsheet. RobotLAB's published subscription rates are on 36-month terms. Ask for a shorter one on a first deployment, and expect to pay more for it. It's worth it.

Purchase makes sense once a category has proven itself on property, because the lease premium over three years is substantial and the residual value of a working unit is not zero. Floor care is the natural purchase candidate because its case is the most predictable. Delivery robots are more often leased indefinitely because the vendor's software and elevator-integration layer is a large part of what you are paying for, and it does not stop needing updates when the hardware is paid off.

Waiting is a legitimate answer for the concierge and humanoid category, where the technology is moving quickly and the current generation has not demonstrated operating returns. It is not a legitimate answer for floor care in a property with meaningful hard-surface square footage, or for F&B running in a high-volume outlet, where the case is closed and the only remaining question is which vendor.

A Ninety-Day Sequence for a First Deployment

Properties that get this right follow roughly the same sequence, and it starts well before the robot is on site.

Days 1 to 30: measure and qualify. Log every delivery, or every floor-care hour, for four weeks. Walk the route with the vendor. Get elevator compatibility in writing from both the robot vendor and the elevator maintenance contractor, not just one. Survey Wi-Fi on the actual path, including inside the cars. Decide, on paper, what happens to the freed hours. If the numbers do not clear the payback table above with room to spare, stop here and save yourself the lease.

Days 31 to 60: install and stabilize. Expect the first two weeks to be worse than the manual process. Mapping, elevator calibration, and staff habit all take time. Name the internal owner, load the preventive maintenance calendar, and hold a five-minute stand-up with the department each week to log what went wrong. Do not announce the robot to guests yet.

Days 61 to 90: run the test. Track autonomous hours or completed deliveries daily, uptime weekly, and the schedule change monthly. At day 90 compare the actual schedule to the day-zero baseline. If the hours have not come off the schedule, either the reallocation plan was never executed or the robot is not doing the job, and both are decisions to make explicitly rather than let drift. If the hours have come off, this is the moment to decide on a second unit or a purchase conversion, and to start telling guests.

Done this way, a property ends up with one or two boring machines doing one or two boring jobs, a housekeeping director who talks about them the way she talks about a good vacuum, and a line on the P&L that moved. The technology is the same either way. The difference is whether anyone did the arithmetic first.

Frequently Asked Questions