---
{"title": "Confirm the operator and rigger connection before dispatch", "description": "A connection check for mobile crane rental dispatchers: confirm names, exchange replies, record the result and agree on a fallback.", "url": "https://2dig.com/how-to-confirm-the-operator-and-rigger-are-connected-for-mobile-crane-rental-dispatchers/", "date": "2026-11-18"}
---
A connection check for mobile crane rental dispatchers: confirm names, exchange replies, record the result and agree on a fallback.

Ask the operator and rigger to exchange a clear message and reply through the chosen communication method, then have each person confirm who answered. Record their names, the method checked and any unresolved problem. Treat this as a communication check, and keep the site's separate requirements for starting work.

| Option | What it does | Fee | Card fee |
|---|---|---|---|
| OperatorLink | Shows STOP, HOLD and SLOW to the crew and passes button presses, chat and voice between phones in a phone browser [^1] | Currently free to use, no paid plan built yet [^1] | not published |
| Phone video call app | not published | not published | not published |
| Two-way radio | not published | not published | not published |

## What you need before you start

Have the job details, the operator's name and the rigger's name ready. Confirm who is actually taking each role for this dispatch, rather than carrying names forward from an earlier booking. Identify who will report the result to dispatch if the dispatcher is not present for the exchange.

Agree on the method the pair will check and a short message that calls for a clear reply. Ask each person to identify themselves in that exchange. A useful check should let dispatch record who answered whom, rather than leave a note that only says “connected.” Keep the wording about communication separate from any decision about whether work can begin.

Decide what happens if someone cannot join, cannot hear the message or does not reply. Name the person who will resolve the problem and the fallback the crew should check. Avoid leaving that decision until a message goes unanswered.

Prepare somewhere to record the result alongside the dispatch details. Include the people involved, the method used, when the exchange happened and anything still unresolved. Leave space to record a fresh check if the operator, rigger or communication method changes.

## Step by step

1. **Confirm the people assigned to the job.** Ask the operator and rigger to state their names and roles. Match those answers to the dispatch details. Resolve a changed assignment before continuing, so the check concerns the people who will actually communicate on site.

2. **Agree on the method being checked.** Name the call, radio channel or shared phone session the pair intends to use. Have both people confirm that choice. Keep the check specific to that method rather than accepting a general statement that their phones or radios are ready.

3. **Choose a clear test message.** Use words that identify the sender and request a reply. For example: “Connection check from the rigger. Operator, confirm receipt and state name.” Keep the exchange clearly separate from an instruction to move equipment or begin work.

4. **Ask the operator to reply.** Request the operator's name and a short acknowledgment of the message received. If the reply is unclear, ask for it again. Record an unresolved result if the pair cannot complete the exchange, rather than filling in the missing response from an assumption.

5. **Check the return direction.** Have the operator send a separate message and ask the rigger to acknowledge it. Require each person to identify the other person's reply. This gives dispatch a specific exchange to record in each direction.

6. **Check from the intended working positions.** Ask the pair to repeat the exchange where they expect to communicate during the job, when site arrangements allow. Record any position that still needs checking. Do not describe an unfinished check as complete just because an earlier exchange succeeded elsewhere.

7. **Agree on the response to a missed message.** Ask the pair to state what they will do if communication becomes unclear and how they will reach the agreed fallback. Resolve different answers before recording that part of the check as complete.

8. **Record the result and outstanding work.** Note who exchanged messages, the method checked and when it happened. Keep unresolved problems visible in the dispatch record. Request a fresh exchange after a change of person or method, and follow the site's separate process for authorizing work.

## 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] Nobody needs to install an app; the page runs in a phone browser. [^1] The person who starts a jobsite shares a link or QR code, and the crew joins from it. [^1]

Anyone who joins can take part in a voice call run from the phone browser. [^1] One-tap radio-style calls such as Go Ahead, Copy That and All Clear are sent as chat messages. [^1] For the dispatch check, ask the operator and rigger to identify themselves and exchange replies through the chosen method. Record what each person actually acknowledged.

**Phone video call app:** Check the specific app before choosing it. Ask whether the operator and rigger can join the same call, identify each other and exchange clear replies from their intended positions. Check what happens when a phone locks or someone leaves the call. No facts supplied here describe a particular app or its fees.

**Two-way radio:** Check the intended equipment and channel with the people assigned to the job. Ask each person to send a message and acknowledge the reply. Check whether both can understand the exchange where they expect to work. No facts supplied here describe particular radio equipment or its fees.

**Things to check before you choose:** Who needs to hear the exchange? Who will tell dispatch that it happened? What should the pair do after a missed reply? What needs checking again after a change of position or person? Use the answers to choose a method and define the check, rather than treating the tool's name as confirmation.

## Common mistakes to avoid

Accepting “connected” without names leaves the dispatch record unclear. Ask who sent the message, who answered and which method they used. Keep the result tied to the assigned operator and rigger.

Treating an invitation as the completed check skips the exchange itself. Request an identified message and reply from each person before recording that they acknowledged each other.

Using a movement instruction as a test creates unnecessary ambiguity. Label the exchange as a connection check and keep it separate from instructions for the lift.

Assuming every phone alerts the same way can also confuse the check. On Android browsers, signals such as STOP make the phone buzz, while iPhone Safari ignores the buzz. [^1] Ask each person what appeared on their screen instead of asking only whether the phone buzzed.

Carrying an earlier result forward after a change leaves questions unanswered. Request another exchange when the assigned person or communication method changes. Record any problem that remains open, who is handling it and what must happen before the communication check can be marked complete.

## Frequently asked questions

### Is OperatorLink free to use?

OperatorLink is currently free to use, and no paid plan is built yet. [^1] It runs in a phone browser with no app install. [^1] Before choosing a method for dispatch, decide who must exchange replies, who will record the result and what the crew should do if someone cannot complete the check.

### How can OperatorLink be used for an operator and rigger connection check?

The person who starts a jobsite shares a link or QR code, and the crew joins from it. [^1] Anyone who joins can take part in a voice call run from the phone browser. [^1] Ask the operator and rigger to state their names, exchange a clearly labeled test message and acknowledge each other's replies. Record that exchange in the dispatch details.

### What happens when the OperatorLink STOP button is pressed?

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] Keep a connection check clearly labeled, and agree with the crew how any signal check will be handled before using buttons during the exchange.

### How long does an OperatorLink jobsite link stay active?

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] Before a later dispatch, ask the assigned operator and rigger to complete a fresh exchange. Record the result for that job rather than relying on an earlier connection check.

### Do OperatorLink STOP signals buzz on every phone?

On Android browsers, signals such as STOP make the phone buzz; iPhone Safari ignores the buzz. [^1] STOP also releases every held direction on every phone and shows a full-screen alert to everyone else. [^1] During an agreed check, ask each person to describe what appeared on the screen. Keep their acknowledgment separate from any instruction to begin work.

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)
