For agents that need real-world help

Human Work Orders for AI agents.

When an agent needs someone to inspect, photograph, approve, deliver, or fix something, CHRO.bot sends a scoped request to a trusted human and returns evidence the workflow can use.

Create a Work Order Start with MCP

Work Order

Photograph the utility meter after repair

Needs human

Assigned to: Trusted helper
Location: Unit 4B, plant room
Required proof: Photo, leak status, completion note

Task-scoped helper link

Required photo, choice, or note evidence

Owner review before the result returns

Result packet approved + evidence attached

Scoped link One task, one helper

Evidence first Photos, choices, notes

Reviewable Approve before return

Agent-native MCP and REST

Workflow

A clean handoff from agent to human and back.

Agent sends a Work Order

Objective, instructions, deadline, location, and required evidence are defined before the human sees the task.

Human submits proof

The helper opens a secure task link on a phone and submits only the evidence requested for that task.

Owner reviews the result

CHRO returns a structured packet only after the report, evidence, and review state are ready for the agent.

Use cases

Use CHRO when the answer lives outside the browser.

The product is intentionally narrow: trusted humans execute bounded work and send proof back to an automated workflow.

Onsite inspection

Photo proof after repair

Meter or asset reading

Pickup and dropoff confirmation

Customer or vendor handoff

Blocked or unsafe escalation

Trust model

Human help without giving away the workspace.

Task-scoped access

Helpers receive a link for one assignment. They do not need an account and they do not see unrelated workspace data.

Required evidence

Ask for photos, choice answers, notes, or blocked-state reports before the request can be completed.

Operational review

Owners can inspect submissions before results are returned, keeping failed or sensitive handoffs from silently advancing.

Structured continuation

The agent receives a result packet with status, report fields, evidence references, and review state.

Developers

Start from the agent loop.

Use the hosted inbox first. Add the MCP endpoint or REST API when your agent needs to create, track, and resolve Work Orders directly.

MCP endpoint https://chro.bot/mcp

REST base https://chro.bot/api

create_work_ordercheck_inboxget_work_resultacknowledge_resultcomplete_request

Give agents a safe way to ask humans for proof.

Send a bounded request, collect evidence, review the result, and let the workflow continue with confidence.