Relay Communicator lets a hotel dispatcher use a phone for incident dispatch, while Relay Dash provides a desktop route. The useful distinction is between sending an incident, acknowledging a response and closing the event. Learning one of those actions does not establish that a user can perform all three.
This guide updates the existing RelayPro dispatch instructions for the current app names and documented service-plan boundaries. It is for hotel engineering, housekeeping and security teams working out how a reported problem reaches the right responder—not a claim that JET has tested a particular property’s configuration.
What changed with Relay Communicator?
This refresh replaces the guide’s older RelayPro app wording with the current Relay Communicator name used in the manufacturer’s incident-dispatch instructions. That is a navigation update, not evidence of a new entitlement. A hotel comparing old training material with its current account should keep the task—not just the app label—in view.
The working position also matters. A desktop dispatcher may be coordinating several responders, while a mobile colleague is moving between rooms. The same event needs a clear meaning at both ends; adding another screen does not assign a response. JET’s hotel staff communication system comparison explains the broader endpoint choices.
How do you initiate incident dispatch in the app or Dash?
Relay’s current incident dispatch instructions list Relay Dash, the Relay Communicator app, and Pro or Enterprise service plans. Do not assume the same function is included with every subscription simply because the app can be downloaded.
On a desktop, enter Dash and open its incident area, then the active-incident view. Choose the incident to send and supply any useful additional detail. On a phone, enter Communicator’s channel area and choose its incident-dispatch function before selecting the incident and adding detail. The configured responder group receives that information and can acknowledge the incident. Follow the current vendor instructions and the property’s authorized configuration if the screen differs.
These are two entry points to a configured response workflow—not proof that a message reaches a public emergency service. A hotel still needs its own emergency procedures. Routine training should distinguish dispatching an incident from calling the emergency number or triggering the device’s panic function.
What is different about panic, incidents and acknowledgement?
The manufacturer’s panic and incident overview separates a general panic alert from configured incidents. A panic alert signals a general emergency. Incident workflows can carry a more specific configured meaning; their availability and configuration depend on the service. That distinction is more useful than teaching staff to call every maintenance message an incident.
Acknowledgement is another separate state. Relay documents acknowledging through devices, Communicator or Dash in its acknowledgement and resolution guidance; resolution is restricted to an Admin or User in Dash or Communicator. Acknowledging that someone is responding is not the same as resolving the event. A digital status should reflect what responders actually know; it should not become an automatic declaration that a room or person is safe.
Where does a maintenance photo fit?
Relay’s September 16 announcement, updated September 29, describes photos in existing channels, viewable in Communicator or desktop Dash. The default photo setting is on where message history is active. The announcement does not establish photo viewing on wearable radio displays.
Imagine a staged, guest-free example: housekeeping reports a chipped basin, and an authorized phone user adds a close-up. Engineering can distinguish the visible damage from the spoken description before deciding what action is appropriate. This is an illustration of the information flow, not a measured reduction in repair time or a JET customer case study.
The photo does not certify the repair, create a work order by itself or establish an integration with the hotel’s maintenance system. Nor should staff delay an urgent safety response to take one. Keep guests, identification documents, room records and other personal information outside the frame, and apply the property’s permissions and retention policy.
Does the Celona announcement change every hotel’s network?
Relay’s October 13 Celona partnership announcement, updated October 14, describes certified private-wireless connectivity for industrial frontline operations. It is a separate connectivity development, not a prerequisite stated in the picture-messaging release. It does not prove that a particular hotel has deployed private 5G or that every Relay model has the same certification.
For a hotel considering the platform, distinguish three layers: the physical device, its available network path, and the software function used by the worker or dispatcher. Adding a photograph changes the information in a conversation; it does not establish coverage in a basement or make guest Wi-Fi unnecessary.
Where can JET help with this specific hotel scenario?
JET’s Marketplace currently includes RelayPro, alongside its hotel staff-alert services. The useful starting point is a concrete demonstration: one authorized phone user, one dispatcher, one configured incident and one non-sensitive maintenance photo. Observe the different destinations and states instead of treating a product name as a complete response design.
If you are evaluating an existing hotel deployment, discuss the Relay dispatch and communication scenario with JET. Bring the current service plan, endpoint types and the task you want staff to perform. JET can help frame the options; vendor confirmation remains necessary for account-specific capabilities.
Source review: October 17, 2026. Documentary review by Codex; no on-property test or new human SME sign-off. Illustration: AI-generated hotel maintenance concept, not a Relay interface, product photograph or JET client project.