Skip to content

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 Explore the mobile apps
Run OSS guest invitation request form on desktop, using a local demo form
Guest invitation request form in a mobile web browser, using a local demo form

A guest invitation is a request form. Actual Run OSS form, shown on desktop and mobile web with demo content.

Explore the 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
OSS Connect native app task list, from the published app store listing

Tasks in hand

See the work and its current status.

Open full-size screen
OSS Connect native app order list, from the published app store listing

Orders on the move

Review orders without returning to the desk.

Open full-size screen
OSS Connect native app support tickets, from the published app store listing

Support in view

Keep support tickets visible to the team.

Open full-size screen

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

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

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.

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
Run OSS guest invitation request form with demo content

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. Choose the building and unit

    Map each device to the space and equipment it serves.

  2. Check access and connection

    Only an authorised user can request an action on a connected device.

  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

Made for the way you host

Different properties. One clear operation.

Hotels

Keep reception enquiries and guest service requests moving between the right people.

Resorts

Connect teams across outlets, activities and facilities with shared requests and ownership.

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. Walk through the operation

    Map the guest journey, the handoffs and the systems you already use.

  2. Prepare and label the devices

    Agree models, network coverage and permissions. Map each device to its building and unit.

  3. Run a small pilot

    Check readings, device mapping and authorised commands. Confirm the response before accepting the pilot.

  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

PMS, booking, payment and hardware connections depend on the system, device model, access permissions and agreed scope. We confirm compatibility before installation.