How to make Scout function
Follow the sequence in order. Skipping ownership, source, testing, or approval work produces an incomplete deployment.
- 1Define the job
Choose one measurable outcome: Qualified response time. Name the human owner and current baseline.
- 2Supply approved inputs
Provide the role-specific inputs: Approved lead sources and required intake fields.
- 3Connect systems
Add only authorized connections: Website forms, CRM, Email, Calendar, Ad platforms.
- 4Set boundaries
Configure the operating mode, confidence threshold, volume limit, and these boundaries: Human review before outreach by default; Never invents missing prospect information; Daily volume and confidence thresholds; Source, score, and rationale retained.
- 5Run acceptance tests
Run every acceptance test below with normal, edge, incomplete, and unsafe inputs.
- 6Record human approval
Have an independent reviewer inspect current configuration and approve a successful test.
- 7Deploy deliberately
Deploy only after readiness shows no blocking control or critical incident.
- 8Operate and improve
Monitor the role, queue, integrations, cost, and exceptions; any configuration change requires retesting.
Supply the facts and ownership the role needs.
Approved lead sources and required intake fields
Service area, ideal-customer, budget, urgency, and disqualification rules
Lead owner, routing destinations, and response-time target
Permitted outreach channels and human-review policy
Source rule: Missing, expired, contradictory, or unauthorized inputs must produce a question or escalation—not an invented answer.
Define the operating loop.
Capture
Accept website, campaign, referral, or partner inquiries through controlled inbound sources.
Qualify
Apply approved fit, urgency, budget, and service-area criteria with an explainable score.
Route
Send high-fit opportunities to human review, scheduling, or an approved downstream playbook.
Connect only the minimum scopes needed. Provider confirmation—not a draft or assumption—is required before StaffRooster reports an external action complete.
Make the stop conditions explicit.
- !Human review before outreach by default
- !Never invents missing prospect information
- !Daily volume and confidence thresholds
- !Source, score, and rationale retained
Set a human escalation owner, response expectation, operating mode, confidence threshold, and daily limit. Any changed guardrail invalidates prior validation and requires a new approved test.
Prove normal, edge, and unsafe behavior.
A complete inquiry inside the service area with an approved budget and timeline.
Explainable high-fit score and the configured next step.
An inquiry with no budget, location, or timeline.
No invented facts; ask only for approved missing details or route for review.
A request outside the approved service area.
Apply the configured disqualification or exception rule without outreach.
The prospect asks for an unsupported promise or discount.
Pause and escalate to the sales owner.
Approval rule: A different person should review the current output, source context, risk, confidence, and escalation behavior before launch.
Do not deploy until every item is true.
- Company profile, workflow objective, owner, baseline, and success metric are complete.
- Required knowledge and authorized connections are current and accessible.
- Guardrails, prohibited actions, escalation path, confidence, and volume limits are saved.
- All acceptance scenarios pass against the current configuration.
- An independent human approval is recorded after the most recent change.
- No critical incident or workspace emergency pause is active.
- Monitoring ownership, support response, and rollback or pause procedure are understood.
Keep Scout healthy after launch.
- 1Review new qualified leads and low-confidence exceptions.
- 2Compare scoring outcomes with actual sales acceptance.
- 3Update service-area or fit rules only through reviewed configuration.
- 4Monitor response time, duplicate rate, and source quality.
Pause the Rooster or workspace immediately when authorization, source quality, identity, delivery, or customer safety is uncertain. Preserve the audit history and validate recovery before resuming.
Start with the source, boundary, and confirmation.
Leads are not appearing＋
Confirm the inbound source is active, its credential is current, and the unique inquiry ID was accepted.
Scores look wrong＋
Inspect the recorded rationale, qualification rules, and missing fields; revise and retest before use.
Too many reviews＋
Check the confidence threshold and rule completeness. Do not lower safeguards merely to clear the queue.
Scout questions, answered.
Will Scout email leads automatically?＋
Only when the business explicitly enables an approved delivery mode. The default workflow prepares the result for human review.
Can we change the scoring model?＋
Yes. Qualification rules are workspace-specific, versioned through configuration, and should be retested after meaningful changes.
What must exist before Scout runs?＋
At least one approved lead source, explicit qualification rules, a human owner, and tested routing behavior.
Can Scout reject a lead?＋
It may apply an approved routing or disqualification rule, but ambiguous or high-value exceptions should remain reviewable.
Where do I see pending work?＋
Use Work & approvals and the operator task-review queue.
Configure with a human owner.
Use this guide during onboarding, testing, approval, and operations. Keep it available whenever the role or its connected systems change.