Operator READY and browser requirements

The dialer now treats both supported operator modes as persistent operator sessions. Prospects only dial when the operator is READY. READY means the operator participant is connected and stayed stable long enough to be trusted for prospect dialing.

Core rule If the operator is not READY, the dialer should not place new prospect calls.

Browser operator requirements

Use Chrome on desktop.
Use a wired headset.
Turning Bluetooth off is recommended if audio is unstable.
No VPN is required.
Leave the dialer tab open while the operator session is active.

The dialer UI can show estimated browser CPU/network capacity for troubleshooting. Browsers do not expose live CPU usage, live Bluetooth state, or live VPN state, so those checks are best-effort only.

Phone operator flow

Select Phone operator.
Enter the operator phone number.
Click Start Call to prepare the session.
Call the displayed Twilio number inbound from that same registered phone.
Wait for the UI to show READY.
Only then start prospect dialing or autodial.

In Phone operator mode, browser audio buttons are hidden because the operator audio path is the phone call, not the browser.

Campaign import note for platform staff

Campaign import uses the signed-in account organization automatically when one exists. Platform staff who are working across organizations must enter the correct Organization ID in the dialer before loading campaigns.

What pauses autodial now

Browser audio disconnects or becomes unstable.
The operator phone leg ends.
The operator is connected, but never becomes stable enough to reach READY.

What happens when the operator drops

Autodial pauses immediately.
If no approved buyer handoff is active, any live prospect leg is ended instead of leaving the prospect waiting.
If a real three-way handoff to the buyer is already active and the operator intentionally drops, the buyer/prospect call is allowed to continue.

Support checklist

Ask which operator mode was selected.
Ask whether READY ever appeared.
For browser mode, ask whether Chrome desktop and a wired headset were used.
For phone operator mode, ask whether the rep clicked Start Call and called the displayed Twilio number from the registered phone.
Capture the conference name and last visible runtime log line if the issue persists.