What counts as a service robot?
In hospitality, “service robot” is a broad label for mobile machines that support guest-facing or staff-facing routines. A unit may carry amenities, bring dishes to a pickup point, guide a visitor toward a location, or display routine information. Some systems are designed to interact with guests; others mostly move things while staff manage the service around them.
That distinction matters. A robot that assists a defined task is not the same as a system that replaces an entire workflow. A mobile carrier might take a tray along a familiar route, while a staff member checks the order, handles special requests and completes the handoff. That can be useful without pretending the machine has taken over hospitality.
Where hotels and restaurants may use them
In hotels, a robot might support the movement of selected supplies or provide simple wayfinding prompts in a lobby. Room-service support can mean transporting an item to a designated point—not necessarily entering a guest room or completing every step of delivery. The exact workflow depends on the building, access rules and the robot’s documented capabilities.
In restaurants, a unit may carry dishes between a service area and a table zone, or help staff move items across a busy floor. The staff member still needs to manage table context, guest requests, food presentation and clearing. A well-chosen assistant takes a repetitive trip out of the routine; it does not remove the judgement around the trip.
Information and wayfinding features can be helpful when questions are predictable and the screen is clear. For people who need spoken directions, accessible routes or human assistance, a robot should be one option among several—not the only door into the service.
Navigation in a building full of people
Indoor navigation usually combines a map of the operating area with sensors that help a machine estimate where it is and notice nearby obstacles. The mix varies by system. In a tidy corridor, routes may be straightforward. In a crowded breakfast room, chairs move, bags appear, children change direction and a server quite reasonably has other things on their mind.
Do not assume that every robot can use an elevator, open a fire door, pass every threshold or enter every guest area. Those capabilities require compatible building systems, suitable access arrangements and explicit testing. If the unit cannot complete a route, staff need to know how it asks for help and who takes over.
Comfort, access and privacy
Guests have different expectations. Some enjoy a short interaction; others would rather speak with a person. Clear signage and an easy way to decline an automated interaction help keep the experience welcoming. Consider turning space, passing width, audible alerts, screen height and whether the robot blocks a route when it stops.
Privacy deserves the same practical attention. A robot may use cameras or other sensors for navigation, and a guest-facing screen may handle information. Ask what data is captured, whether it is stored, how long it is retained, who can access it and whether recording can be disabled. A device should collect only what its job genuinely requires.
Make the handoff part of the design
Staff need a simple way to pause, reroute or retrieve a unit. Train them on safe interaction, error messages, charging routines and the point at which they should take over. Guests also benefit from a plain explanation of what the robot can and cannot do. “It will bring the tray to this pickup point” is more helpful than a sweeping promise of autonomous service.
Finally, assess reliability in the real environment, not just a quiet demonstration. Track interruptions, cleaning, maintenance and staff effort alongside guest feedback. In Copenhagen, a compact city hotel and a large resort have very different routes, traffic and service rhythms; the right answer is local. A robot earns its place when its task is useful, the people around it feel comfortable, and the fallback plan works on an ordinary busy day.