[Run OSS Hospitality](#hospitality-top) [Mobile apps](#hospitality-apps) [Guest journey](#hospitality-workflows) [Connected property](#hospitality-hardware) [Your setup](#hospitality-rollout) [Questions](#hospitality-faq) [Plan your property setup](https://runoss.com/en/demo/request) On this page [Mobile apps](#hospitality-apps) [Guest journey](#hospitality-workflows) [Connected property](#hospitality-hardware) [Your setup](#hospitality-rollout) [Questions](#hospitality-faq) [Plan your property setup](https://runoss.com/en/demo/request) For hotels, resorts and beach clubs A better stay. A connected team. ================================ Run OSS connects guest requests, staff tasks and service workflows for hotels, resorts and beach clubs. Start with invitation forms, equip your team with OSS Connect, and plan a guest app under your own brand. [Plan your property setup ](https://runoss.com/en/demo/request) [Explore the mobile apps ](#hospitality-apps) Guest invitation forms OSS Connect Connected property Run OSS ![Run OSS guest invitation request form on desktop, using a local demo form](https://runoss.com/build/assets/desktop-en-guest-invitation-DNZ4A8c8.webp) ![Run OSS guest invitation request form on desktop, using a local demo form](https://runoss.com/build/assets/desktop-en-guest-invitation-dark-CVwYAnRB.webp) ![Guest invitation request form in a mobile web browser, using a local demo form](https://runoss.com/build/assets/phone-en-guest-invitation-WXoD7uD5.webp) ![Guest invitation request form in a mobile web browser, using a local demo form](https://runoss.com/build/assets/phone-en-guest-invitation-dark-xzhVuMUG.webp) A guest invitation is a request form. Actual Run OSS form, shown on desktop and mobile web with demo content. Run OSS ![Run OSS task board on desktop with demo work assignments](https://runoss.com/build/assets/desktop-en-tasks-CgquOo1S.webp) ![Run OSS task board on desktop with demo work assignments](https://runoss.com/build/assets/desktop-en-tasks-dark-CsffhR98.webp) ![OSS Connect native mobile app showing tasks from its store listing](https://runoss.com/build/assets/phone-app-connect-tasks-rrGZga56.webp) ![OSS Connect native mobile app showing tasks from its store listing](https://runoss.com/build/assets/phone-app-connect-tasks-rrGZga56.webp) The task board at the desk. OSS Connect in the team’s hands. Web demo and native app store screens. Run OSS ![Run OSS device topology showing demo branches and staff equipment](https://runoss.com/build/assets/desktop-en-devices-DGacf4vs.webp) ![Run OSS device topology showing demo branches and staff equipment](https://runoss.com/build/assets/desktop-en-devices-dark-CL9l_rUZ.webp) See how Run OSS organises staff devices by location. Demo data; UniFi and Shelly integration has a separately agreed scope. [Explore the workflows ](#hospitality-workflows) Mobile is part of the operation Your team’s app. Your property’s identity. ------------------------------------------ OSS Connect puts daily work in your team’s hands. OSS white-label gives your property its own app identity. Plan the guest services and staff permissions around how you operate. For the people who make the stay work ### OSS Connect Open tasks, review orders and follow support tickets from a phone. Staff can use the mobile app while the desk works in Run OSS. [Plan your team’s mobile workflow ](https://runoss.com/en/demo/request) ![OSS Connect native app task list, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-tasks-rrGZga56.webp) ![OSS Connect native app task list, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-tasks-rrGZga56.webp) #### Tasks in hand See the work and its current status. [Open full-size screen ](https://runoss.com/build/assets/phone-app-connect-tasks-rrGZga56.webp) ![OSS Connect native app order list, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-orders-Bfma5tbY.webp) ![OSS Connect native app order list, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-orders-Bfma5tbY.webp) #### Orders on the move Review orders without returning to the desk. [Open full-size screen ](https://runoss.com/build/assets/phone-app-connect-orders-Bfma5tbY.webp) ![OSS Connect native app support tickets, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-tickets-CD_CVVxh.webp) ![OSS Connect native app support tickets, from the published app store listing](https://runoss.com/build/assets/phone-app-connect-tickets-CD_CVVxh.webp) #### Support in view Keep support tickets visible to the team. [Open full-size screen ](https://runoss.com/build/assets/phone-app-connect-tickets-CD_CVVxh.webp) Actual OSS Connect screens from the app store listing. These screens keep their original language and theme. OSS white-label ### Your property. Its own mobile app. Give your property an app with its own name, icon and colours. Agree the services guests can use, how their requests reach staff, and what the first release includes. - **Your name and visual identity** Set the app name, logo and brand colours. - **Your guest journey** Plan invitation forms, guest requests and the services included in your app. - **A release prepared for your property** Configure the Android and iOS app identities, then complete the store setup and review. [Plan your branded app](https://runoss.com/en/demo/request) App features, setup and store publication are agreed per project. Store review is required. ![Guest invitation request form in a mobile web browser, using a local demo form](https://runoss.com/build/assets/phone-en-guest-invitation-WXoD7uD5.webp) ![Guest invitation request form in a mobile web browser, using a local demo form](https://runoss.com/build/assets/phone-en-guest-invitation-dark-xzhVuMUG.webp) Guest request form on mobile web. This is a real form example; the native white-label app is configured for your property. From invitation to next visit Make every handoff feel effortless. ----------------------------------- Start with a guest invitation form. Give each request a clear owner and status. Keep service and return visits part of the same operation. 01Before the visit**Start with a guest invitation form** 02During the visit**Follow requests through to completion** 03After the visit**Give guests a reason to return** Before the visit ### Start with a guest invitation form Collect guest details through a request form. Set the required fields and route the submission through the review steps your property needs. [See request forms and workflows ](https://runoss.com/en/solution/workflow-and-request-automation) Run OSS ![Run OSS guest invitation request form with demo content](https://runoss.com/build/assets/desktop-en-guest-invitation-DNZ4A8c8.webp) ![Run OSS guest invitation request form with demo content](https://runoss.com/build/assets/desktop-en-guest-invitation-dark-CVwYAnRB.webp) During the visit ### Follow requests through to completion Use forms and workflows to capture a service request, pass it to the right team and follow its status. [See request and order tools ](https://runoss.com/en/solution/unified-channel-management) Run OSS ![Run OSS workflow builder showing request steps and decisions with demo data](https://runoss.com/build/assets/desktop-en-workflow-ZXgRwkE0.webp) ![Run OSS workflow builder showing request steps and decisions with demo data](https://runoss.com/build/assets/desktop-en-workflow-dark-qiw1XetO.webp) After the visit ### Give guests a reason to return Set points, stamps or tiers for your loyalty program. Choose rewards that fit your business and track their use. [See Run OSS Loyalty ](https://runoss.com/en/solution/customer-loyalty-system) Your next visit starts here Recognition that brings people back. - Points - Stamps - Tiers You set the rewards and the rules. Run OSS product screens with demo data. Your workflows are configured for your property. Software meets the property Connected from the front desk to the last device. ------------------------------------------------- Bring UniFi and Shelly into the property plan. We review your equipment and network, agree the connections, and define what each team can see or control. A property connection plan UniFi network & access Shelly devices & readings The connection scope is agreed before rollout. An energy project built around your units ### Know where power goes. Decide who can act. Plan metering by building and unit, then add controlled switching where it is suitable. A meter measures consumption; a relay switches an approved load. Each has its own role. Example control workflow to agree and test 1. 1**Choose the building and unit** Map each device to the space and equipment it serves. 2. 2**Check access and connection** Only an authorised user can request an action on a connected device. 3. 3**Send the action and check its result** Confirm the device status after the command. No response is not a success. Project scope, not a live control panel. Integration, mobile access and device response are tested during the agreed pilot. ### UniFi Network, cameras and access Plan guest and staff networks, UniFi Protect cameras and UniFi Access doors as part of your site setup. Agree which supported events and access workflows connect to Run OSS. - Guest and staff network design - Camera and door-access requirements - Supported events and staff permissions ### Shelly Energy metering and controlled switching Plan energy readings by unit with compatible Shelly meters and separate relays for approved loads. Agree mobile access, staff permissions and status checks before rollout. - Meter readings by building and unit - Separate relays for approved loads - Connection and command-status checks Device support varies by model and firmware. Hardware supply, electrical installation, network work and integration are scoped separately. Critical controls need an agreed local fallback. [Discuss hardware integration](https://runoss.com/en/demo/request) Made for the way you host Different properties. One clear operation. ------------------------------------------ 01 ### Hotels Keep reception enquiries and guest service requests moving between the right people. 02 ### Resorts Connect teams across outlets, activities and facilities with shared requests and ownership. 03 ### Beach clubs Bring guest questions, on-site service and a reason to return into one journey. Start small. Build with purpose. A setup that fits your property. -------------------------------- Start with one useful workflow. Confirm it with your team, then decide what to connect next. 1. 1 ### Walk through the operation Map the guest journey, the handoffs and the systems you already use. 2. 2 ### Prepare and label the devices Agree models, network coverage and permissions. Map each device to its building and unit. 3. 3 ### Run a small pilot Check readings, device mapping and authorised commands. Confirm the response before accepting the pilot. 4. 4 ### Train, review and expand Check the workflow with your team. Add the next part when the first is working. Questions Before we get started. ---------------------- ### Can the app use our property’s brand? Yes. OSS white-label supports a separate app name, icon, brand colours and Android/iOS identity. We agree the guest features, setup and store submission scope before the first release. ### Is Run OSS a hotel booking system or PMS? This journey focuses on guest invitation forms, mobile apps, service requests, loyalty and connected operations. We review your booking or property management system before agreeing any connection. Do not assume that a specific PMS is supported. ### Can we keep our existing UniFi and Shelly equipment? We review the device models, firmware, network and available access first. The setup proposal states what can connect, what needs work and what should remain local. ### Do we need to replace everything at once? No. Start with one workflow, such as guest invitation forms or service requests. Hardware work and other system connections can be planned separately. ### Can our team work in Arabic and English? Run OSS supports Arabic and English. We review your guest-facing forms, messages and team workflow in the languages you need. ### What determines the price? The solutions, users, setup work and hardware determine the scope. Hardware supply, installation and third-party services can have separate charges. We agree these before work starts. Built around your guests. One property. Your way of working. ---------------------------------- Bring one guest journey to a call. We will review the people, steps and systems it uses, then agree a starting scope. [Plan your property setup ](https://runoss.com/en/demo/request) PMS, booking, payment and hardware connections depend on the system, device model, access permissions and agreed scope. We confirm compatibility before installation. [ ![](https://runoss.com/build/assets/whatsapp-CraU-7tO.webp)](https://wa.me/966568088058?text=I%20am%20interested%20in%20Run%20OSS.%20How%20can%20I%20start%3F)