Work order
What was requested.
Review the early access form and make the first buyer step feel like a work order instead of a generic demo request.
Work receipt rec_sample_sal_lead_flow
Sal tightened a buyer path
A manually crafted example receipt showing what a sales ai robot trial should prove.
Operational proof
What actually happened.
This block is safe to share: it records runtime context, scope, cost and mode without exposing secrets.
- Project
- Not recorded
- Runtime / model
- Not recorded / Not recorded
- Mode
- manual_sample
- Cost
- n/a
- Tokens
- n/a
- Duration
- n/a
- Work order
- wo_sample_sal_lead_flow
- Run
- run_sample_sal_lead_flow · completed
- Risk level
- Not recorded
- Allowed tools
- No tool grant recorded
At a glance
The receipt shape.
A receipt should be readable without knowing the internal workflow.
- Work order
- Review the early access form and make the first buyer step feel like a work order instead of a generic demo...
- AI robot assigned
- Sal · Sales AI Robot
- Checks run
- 3 logged
- Output
- Recommended changes: - Rename the CTA from "Request demo" to "Give work order". - Ask for selected AI robot...
- Proof
- Timeline has 5 events
- Limit
- No analytics were reviewed.
- Next action
- Human approval required before using this output externally.
Buyer proof brief
Use this receipt before buying more work.
The request, output, checks, limits and approval point a buyer can review before giving the AI robot a larger work order.
- Reusable case-study frame
- Request, AI robot, output, checks, limitations and next action are all visible.
- Review evidence
- 3 steps, 3 checks and 3 limits recorded.
- Next buying decision
- Human approval required before using this output externally.
After this proof
Next ways to inspect Sal.
A receipt should make the next decision concrete: read the resume, compare non-binding pricing examples, inspect the advanced workflow, or send one more small work order for human review.
Basic resume
Read Sal's resume
Best-at work, limitations, required inputs and example first tasks.
Pricing examples
Compare example bands
Non-binding starter bands, work-order shapes and receipt-to-value examples before more spend is approved.
Advanced usage
Inspect the workflow
Run modes, permissions, evidence, guardrails and human handoffs.
Next work order
Send a small job
Use this receipt shape to ask for the next checked piece of work.
AI robot assigned
Sal · Sales AI robot
Sal improves the in-app buyer path and makes lead handoff cleaner.
Steps taken
-
1. Reviewed path
Read the homepage, navigation and early access form.
-
2. Reduced fields
Kept only fields needed to route the first work order.
-
3. Wrote handoff
Left next-step rules for a human owner.
Checks run
Form friction
Checked that the form only asks for name, email, company, AI robot, task and next step.
Buyer language
Replaced demo-first wording with work-order language.
Handoff
Marked unclear AI robot selections for human follow-up.
Output
What came back.
Recommended changes:
- Rename the CTA from "Request demo" to "Give work order".
- Ask for selected AI robot, work order/task and preferred next step.
- Keep the form short enough for a busy buyer.
- Route unknown AI robot choices to human review.
Handoff:
Paige should polish the final labels.
Frank should check the form on mobile.
Proof / evidence
What happened.
17:22:24 · received
Task received
The sample work order was logged.
17:23:24 · assigned
AI robot assigned
Sal was assigned to the sample run.
17:24:24 · worked
Output drafted
The manually crafted launch output was produced.
17:25:24 · checked
Checks run
The sample was checked for clarity, limitations and approval notes.
17:26:24 · receipt
Receipt issued
The receipt was stored as a shareable proof object.
Limitations
What is not proven.
No analytics were reviewed.
No real buyer interviews were used.
Human follow-up still decides whether the task is a fit.
Next action
Human approval required before using this output externally.