This page explains when, why, and how a robot autonomously decides to call the Robot Helpline, how the escalation is handled end-to-end, and what role manufacturers play in enabling this safely and compliantly.
The Robot Helpline is not a remote-control service by default. It is a policy-driven human escalation layer that activates only when predefined safety or confidence thresholds are crossed.
High-Level Escalation Flow
* Teleoperation is optional and only enabled where explicitly authorized by the manufacturer and operator.
Escalation Triggers (When a Robot Calls)
Robots escalate based on policy, not intuition. Triggers are deterministic, auditable, and configurable.
1. Confidence Threshold Breach
The robot assigns a confidence score to its intended action.
Trigger: Confidence falls below a manufacturer-defined safety threshold.
Example: The robot understands a task but cannot reliably predict the outcome.
2. Time-Bound Stagnation
The robot detects lack of progress within an allowed time window.
Trigger: No forward progress after N seconds or cycles.
Example: An autonomous system paused longer than operational policy allows.
3. Policy Conflict
Two or more internal constraints produce incompatible actions.
Trigger: Safety rules, task goals, or legal constraints conflict.
Example: "Assist human immediately" vs "Do not enter restricted area."
4. Environmental Assumption Violation
The environment deviates from expected operating conditions.
Trigger: Infrastructure, sensor, or communication assumptions fail.