---
{"title": "Relay voice cues to crane operators by phone", "description": "Relay voice cues while slinging loads with phone browser options, setup steps, tool choices and checks for rigging supervisors.", "url": "https://2dig.com/how-to-relay-clear-voice-cues-to-the-operator-while-slinging-loads-for-rigging-supervisors/", "date": "2026-10-12"}
---
Relay voice cues while slinging loads with phone browser options, setup steps, tool choices and checks for rigging supervisors.

OperatorLink lets a jobsite crew share STOP, HOLD and SLOW signals and pass button presses, chat and voice between phones in a phone browser. [^1]

| Option | What it does | Fee | Card fee |
|---|---|---|---|
| OperatorLink | Shows STOP, HOLD and SLOW to the jobsite crew and passes button presses, chat and voice between phones in a phone browser. [^1] | Currently free to use, and no paid plan is built yet. [^1] | not published |
| Phone video call option | not published | not published | not published |
| Two-way radio option | not published | not published | not published |

## What you need before you start

To relay voice cues while slinging loads, have a phone with a working browser and a data signal ready before the lift. [^1] The person who starts the jobsite needs to share a link or QR code, and the crew joins from it. [^1] Decide how the crew will pass urgent directions and how everyone will confirm a signal before movement starts.

For OperatorLink, the crew sees STOP, HOLD and SLOW on a phone browser, and button presses, chat and voice pass between phones in the browser. [^1] Anyone who joins can take part in a voice call run from the phone browser. [^1] A jobsite link stops working 12 hours after the first person joins it. [^1] A jobsite with nobody in it is wiped after 3 idle hours. [^1]

## Step by step

1. Check that the phones being used for communication have a working browser and a data signal for the shift. [^1]

2. Choose the communication method before the lift and confirm that the crew understands the signals and voice cues that will be used.

3. If using OperatorLink, have the person who starts the jobsite open the session from a phone browser, with no app install needed. [^1]

4. Share the jobsite link or QR code with the crew so each member can join from it. [^1]

5. Confirm that every crew member is in the session before movement begins, so each person sees the same signals. [^1]

6. Use one-tap radio-style calls such as Go Ahead, Copy That and All Clear when short confirmations are needed. [^1]

7. Use the voice call if the crew needs spoken communication, because anyone who joins can take part in a voice call run from the phone browser. [^1]

8. Remember how the signals behave during the lift. STOP releases every held direction on every phone and shows a full-screen alert to everyone else. [^1] HOLD and SLOW stay on for everyone in the jobsite and are cleared when the last person leaves. [^1]

## Tools that can do it

OperatorLink is made by the team that publishes this site. It shows STOP, HOLD and SLOW to the jobsite crew and passes button presses, chat and voice between phones in a phone browser. [^1] The page runs in a browser with no app install. [^1] The person who starts a jobsite shares a link or QR code, and the crew joins from it. [^1]

A phone video call option can be considered for voice communication. Check whether the crew can keep the call open for the lift and whether the needed phone settings work for the site.

A two-way radio option can be considered for voice communication. Check that the crew agrees on the words to use and that everyone who needs to speak can access the radio.

A mix of tools can also be considered when the crew needs both spoken cues and visible signals. Match the option to the site conditions and keep a fallback method available.

## Common mistakes to avoid

Relying on one phone without checking its data signal can create a communication issue, so confirm the phones are ready before the lift. For OperatorLink, button presses, chat and voice pass between phones in a browser. [^1]

Assuming every phone alerts the same way can cause confusion. On Android browsers, signals such as STOP make the phone buzz, while iPhone Safari ignores the buzz. [^1]

Forgetting that HOLD and SLOW stay on until the last person leaves can lead to missed signal clearing. [^1] Not checking a move signal can also cause confusion because if a move stops arriving for 2 seconds, the other phones drop it. [^1]

## Frequently asked questions

### Is OperatorLink free to use?

OperatorLink is currently free to use, and no paid plan is built yet. [^1] The signals and voice features run through a phone browser, so the phone needs a working data signal for use. [^1] Check the phone setup before relying on the tool for a lift.

### How does OperatorLink share voice cues with a crew?

OperatorLink passes button presses, chat and voice between phones in a phone browser. [^1] Anyone who joins can take part in a voice call run from the phone browser. [^1] The person who starts the jobsite shares a link or QR code, and the crew joins from it. [^1]

### How does OperatorLink handle STOP signals?

STOP releases every held direction on every phone and shows a full-screen alert to everyone else. [^1] HOLD and SLOW work differently because they stay on for everyone in the jobsite and are cleared when the last person leaves. [^1]

### Do STOP alerts buzz on every phone with OperatorLink?

On Android browsers, signals such as STOP make the phone buzz. [^1] iPhone Safari ignores the buzz, so the alert behavior is different on those phones. [^1] Check each phone before the lift so the crew knows what to expect.

### How long does an OperatorLink jobsite link work?

An OperatorLink jobsite link stops working 12 hours after the first person joins it. [^1] A jobsite with nobody in it is wiped after 3 idle hours. [^1] Start a new session when a fresh link is needed.

OperatorLink is currently free to use, and no paid plan is built yet. [^1] - [Visit OperatorLink](/go/start)

## Sources

[^1]: OperatorLink's own description of itself (the product of this site's publisher) (/go/start)
