Guide · Operations · 8 minutes

Deploying the Guest Talk mobile app to your team.

The Guest Talk mobile app is designed for on-the-floor work: housekeeping updates, room-status changes, guest messaging while walking with the guest, and quick reservation look-ups. It runs on Android 10 and iOS 15 upwards. This guide covers device selection, fleet management, single sign-on and the training playbook we ship with every new site.

Device selection

For housekeeping we recommend a rugged Android phone with a physical keyboard-safe screen (Samsung XCover, CAT S53). For front-office we recommend an iPad Mini docked at the desk plus one shared iPhone for walk-around use. For maintenance a rugged tablet is worth the cost; the app supports both phone and tablet layouts.

Bring-your-own-device (BYOD) is supported but comes with policy overhead: the workspace administrator can restrict BYOD sessions to specific IP ranges, enforce a device passcode, and revoke the device remotely. Most independent hotels prefer a small pool of company-owned devices; hostels with 20+ staff often lean into BYOD with tight policies.

Fleet management

The workspace exposes a Devices tab where administrators see every device that has authenticated in the past 90 days, the OS version, the app version, and the last-seen time. Individual devices can be forced to sign out or blocked entirely; a lost phone is a two-tap remediation.

App updates deploy through the App Store and Google Play; the workspace enforces a minimum app version and displays an upgrade prompt when a device falls below it. Enforcement can be soft (warning) or hard (login blocked); most operators choose soft.

Single sign-on

Guest Talk supports SSO through OIDC and SAML. Recommended providers: Google Workspace (for hotels using Google), Okta (for larger groups), Microsoft Entra ID (for corporate estates). SSO reduces password sprawl and enables central deprovisioning: a former employee removed in Google Workspace loses Guest Talk access within 60 seconds.

SSO is optional on the free plan and included on Growth and Enterprise. Configuration takes 15 minutes with your IT partner using the OIDC quickstart in the workspace.

Offline mode

The mobile app operates in a limited offline mode: existing reservations, room-status board and guest cards can be viewed and modified for up to 8 hours without connectivity. Changes queue locally and sync when connectivity returns. This is designed for the specific reality of hotels in older buildings with weak Wi-Fi in some corridors; it is not designed for extended offline periods.

Conflict resolution on sync: for room status, last write wins with a diff visible to the user; for reservations, only the fields the offline user modified are written back, avoiding overwriting concurrent edits made by other staff. Where a genuine conflict cannot be resolved automatically, the user sees a merge dialog and picks the correct value.

Push notifications

Push notifications alert users to messages, assignment changes, escalations and shift handovers. Users configure their own notification preferences within the app (which categories to receive, quiet hours, sound preference). Administrators can enforce baseline settings for on-shift users (for example, escalations always on for the on-shift front-office manager).

Training playbook

1. Pre-launch briefing (15 minutes). All-staff short briefing on why the mobile app is being deployed and what to expect on day one.
2. Role-specific tour (10 minutes). Housekeeping supervisor walks their team through the mobile board on the housekeeping cart; front-office manager does the same at the reception desk.
3. Shadow shift (one shift). A supervisor shadows each user for their first shift using the app, addressing questions in real time and noting confusion points.
4. Two-week check-in. Property manager reviews adoption metrics (users, sessions, tasks completed on app vs on web) and addresses any drop-offs.

Guest Talk provides printable one-page cheat sheets per role (in the languages your team uses) that pin next to the reception desk and in the housekeeping storeroom.

Battery, chargers and physical logistics

A device that runs out of battery mid-shift is worse than a device that does not exist. Provision one charger per person plus one spare per team; docked charging cradles at the reception desk and in the housekeeping storeroom. Rugged phones typically last a full shift with intense use; iPads at the desk are always docked.

Security posture

The app enforces device passcode presence and requires biometric authentication (Face ID, Touch ID, fingerprint) on any device that supports it. Sessions expire after 12 hours of inactivity; a re-authentication prompt is trivial with biometrics. Screenshots of guest-financial screens are blocked at the OS level on iOS; on Android the app declines to render sensitive views in the recent-apps preview.

Support routine

App-level issues are triaged in the workspace helpdesk; device-level issues route to your IT partner. Guest Talk publishes a status page and posts incident updates within 15 minutes of confirmed impact. For enterprise customers, an on-call channel in Slack or Teams is available in addition to email support.

Common questions

"Do we need MDM?" Not required. If you already have an MDM (Jamf, Intune, Kandji) the app supports MDM-managed configuration and single sign-on injection. Small independents rarely need MDM.

"Can the app print to a room-key encoder?" The mobile app pairs with supported room-key encoders over Bluetooth (Assa Abloy, dormakaba, Salto). The list of certified models is on the integrations page.

"What happens on the App Store certification?" Guest Talk maintains the app in App Store and Google Play under our own account; new features release on a two-week cadence. Customers do not need their own developer account.

Checklist

• Devices selected per role (housekeeping rugged, front-office iPad, maintenance tablet).
• SSO configured (Google, Okta, Entra).
• Minimum app version enforced.
• Push notification categories configured per role.
• Offline sync policy reviewed with GM.
• Chargers provisioned 1:1 plus 1 spare per team.
• Training playbook run (pre-launch, role tour, shadow shift, 2-week check).
• Support routing decided (helpdesk vs IT partner vs Guest Talk).