# How FCS1 IRGS connects the in-room guest experience with hotel operations

Canonical-URL: https://hoteltech.news/digest/fcs1-irgs-in-room-guest-services-hotel-operations
Text-Version: https://hoteltech.news/digest/fcs1-irgs-in-room-guest-services-hotel-operations.txt
Markdown-Version: https://hoteltech.news/digest/fcs1-irgs-in-room-guest-services-hotel-operations.md
Language: en
Published: 2026-09-17T07:42:02.281Z
Modified: 2026-09-17T08:07:12.981Z
Author: FCS Solutions
Topics: hotel-technology
Summary: A guest asking for something is the easy part. FCS1 IRGS, the new guest-facing module of FCS1, is built for the hard part: getting each request to the team that fulfils it, and tracking it until it closes.

## Article

> **Sponsored content.** This article is part of a paid editorial series commissioned by [FCS Solutions](https://www.fcshub.com/en). Hotel Tech News retained editorial control over the framing and the analysis. Product details attributed to FCS Solutions were supplied by the company.

**Quick Answer:** [FCS1 In-Room Guest Services (IRGS)](https://www.fcshub.com/en/products/fcs1-in-room-guest-services?utm_source=hoteltech.news&utm_medium=referral&utm_campaign=irgs) is the guest-facing module of [FCS1](https://www.fcshub.com/en/products/fcs1), launched on 25 August 2026. A guest scans a QR code and requests hotel services from their own phone, with no app to download, and each request flows into [FCS1 Jobs](https://www.fcshub.com/en/products/jobs?utm_source=hoteltech.news&utm_medium=referral&utm_campaign=irgs) so the right department can fulfil, escalate and track it.

**In short**

- FCS1 IRGS launched on 25 August 2026 as the guest-facing module of FCS1, not a standalone product.
- Guests scan a QR code and request services from their own phone in the browser, with no app to download.
- Every request lands in FCS1 Jobs, is routed to the department that fulfils it, and is tracked to completion.
- It covers guest requests, in-room dining, laundry and hotel facilities, with a self-service portal for the hotel.
- No customer results are published yet: FCS claims outcomes such as fewer missed requests and fewer handovers, not percentages.

## The gap is not the request, it is the fulfilment

A guest asking for something is the easy part. The hard part is what happens next: the request reaching the right team and closing without anyone chasing it. That gap is where hotel service quietly breaks.

It breaks more often when a property is short-staffed. When we [profiled FCS Solutions](/digest/fcs-solutions-40-years-hotel-operations-ai) we opened on the number that frames the whole sector: European hospitality is running roughly 10% short of the workforce it needs. A smaller team covering more rooms cannot afford calls that get missed at check-in rush, handovers scribbled on paper, or an order that never reaches the kitchen.

FCS1 IRGS is FCS's answer to that specific gap. It is not a guest app and it is not a digital directory. It is the point where a guest asks for something and the operational team responsible for delivering it picks it up.

## What a request looks like from the inside

The guest side is deliberately plain. Scan a QR code, the browser opens, browse the hotel or pick a service, submit. No download, no account.

What matters is the second half, the part the guest never sees:

| The guest does this | It becomes this inside the hotel |
|---|---|
| Requests an amenity or reports an issue | A job routed to the right operational team |
| Orders in-room dining | An order routed straight to F&B |
| Books laundry or dry cleaning | A submitted order, tracked to completion |
| Looks up facilities, hours and locations | Self-service info the hotel keeps current |

Every one of those submissions lands in **[FCS1 Jobs](https://www.fcshub.com/en/products/jobs?utm_source=hoteltech.news&utm_medium=referral&utm_campaign=irgs)**, the workflow engine underneath. From there it is routed, worked and tracked from initiation through to fulfilment, with the status visible to the teams and managers who need it.

## It is part of FCS1, not a bolt-on

This is the positioning FCS is most deliberate about, and it is the reason IRGS is more than a menu. IRGS is a module of the FCS1 platform, and FCS1 Jobs must be enabled for its request features to work. The guest-facing layer and the operational layer are the same system, not two tools stitched together.

That continuity is the through-line from the platform we covered before: FCS1 already connects housekeeping, maintenance, incidents and guest services for complex hotels. IRGS extends that same connected workflow all the way to the guest's own phone.

## What the platform underneath looks like

FCS1 IRGS inherits the FCS1 platform's shape: cloud-based, API-first, cross-platform, fully customisable, multi-language, and supported by FCS around the clock. Guests reach it through the browser on their own devices, so there is no guest app to install or maintain. Hotels keep their own information current through a self-service content management portal, without going back to a vendor for every menu change.

## What FCS is claiming, and what it is not

Worth being precise here, because FCS is. At launch there is no named customer and no published performance data, so there are no numbers to quote on response time, productivity or guest satisfaction. What FCS does stand behind are operational outcomes: fewer missed requests, fewer manual handovers, less reliance on calls to the front desk, more efficient routing, and clearer visibility of where each request stands.

Karen Bey, Vice President of Sales at FCS Solutions, framed the launch this way:

> "FCS has long focused on helping hotels optimise operational workflows and improve staff productivity. FCS1 IRGS extends that capability by making it simple for guests to ask for what they need. By connecting each request directly to hotel operations, hotels can reduce missed requests and provide faster, more consistent service."

## Our take

The interesting part of IRGS is not the guest menu, which every guest-facing tool has. It is that the menu is wired to the operations platform behind it, so a request does not have to be re-entered, relayed or remembered by a person. For a short-staffed hotel, removing that handover is worth more than another app.

For a hotel weighing it up, the useful questions are about the whole path, not the front screen. How does a request travel from the guest to the person who closes it. What happens when the assigned team is busy. Which languages does the guest side support. And how is it run day to day through FCS1 Jobs. Ask those first.

## Where to see it

FCS published FCS1 IRGS on 25 August 2026 ([launch announcement](https://www.hospitalitynet.org/news/4134075/fcs-solutions-launches-fcs1-irgs-to-connect-guest-requests-directly-with-hotel-operations)). The official product page is [FCS1 In-Room Guest Services](https://www.fcshub.com/en/products/fcs1-in-room-guest-services?utm_source=hoteltech.news&utm_medium=referral&utm_campaign=irgs), and it sits inside the broader [FCS1](https://www.fcshub.com/en/products/fcs1) platform. For the wider picture of how FCS runs hotel operations, see our earlier profile, [FCS Solutions: one operations platform for the most complex hotels](/digest/fcs-solutions-40-years-hotel-operations-ai).

## Sources

- FCS Solutions launches FCS1 IRGS (Hospitality Net): https://www.hospitalitynet.org/news/4134075/fcs-solutions-launches-fcs1-irgs-to-connect-guest-requests-directly-with-hotel-operations
- FCS1 In-Room Guest Services (IRGS): https://www.fcshub.com/en/products/fcs1-in-room-guest-services

## Citation

How FCS1 IRGS connects the in-room guest experience with hotel operations. Hotel Tech News. 2026-09-17. https://hoteltech.news/digest/fcs1-irgs-in-room-guest-services-hotel-operations