Testing the pilot
Use this guide to test the first public Workflowware package: Home Services Missed Lead Recovery.
Also available as markdown: testing-guide.md
Fastest safe test
Use fake or anonymized sample data first. Do not send passwords, API keys, browser cookies, payment data, live inbox access, or full customer lists.
Device guidance
| Device / path | Good for | Not good for |
|---|---|---|
| Phone | Reading, intake, sample submission, approval, feedback | Unzipping or editing package files |
| Computer | Downloading ZIPs, editing files, DIY testing | Not required for guided pilot |
| AI agent | Inspecting files, summarizing, checking approval rules | Acting without human approval |
| Guided pilot | Nontechnical testers | Unattended production automation |
What to test
Submit 1–3 missed lead examples like:
Business type: HVAC Lead message: Need AC repair asap. Are you available today? Received: yesterday afternoon Problem: nobody replied Goal: draft a safe follow-up for human approval
Expected output:
- Triage notes
- Safe follow-up draft
- Approval questions
- Next-action recommendation
- Uncertainty notes
Instructions for AI agents
- Read the package
README.mdfirst. - Read
approval-rules.mdbefore suggesting any action. - Use sample data before live data.
- Do not request secrets or credentials.
- Draft first; do not send messages.
- Ask the human before purchases, account connections, customer contact, or live system changes.
- Return a plain-language summary for a nontechnical human.
Feedback questions
- Was the package understandable?
- Could a phone user understand what to do?
- Could an AI agent inspect it safely?
- What confused you?
- Would the output help recover a missed lead?
- Would you consider a scoped setup/blueprint?