Triage Overseas Service Leads
Triage cross-border service demand into safe next actions. Do not provide legal, tax, immigration, sanctions, payment, accounting, or platform-policy conclusions.
Workflow
- Extract the client country or platform, service goal, deliverables, client inputs, data sensitivity, deadline, payment path, platform rules, revision needs, and acceptance evidence.
- Mark missing facts as
NEEDS_CONFIRMATION; never invent identity, tax, payment, platform, or client authorization facts. - Apply references/lead-triage-gate.md.
- Classify the lead as low-risk service delivery, needs human compliance check, or decline.
- Rewrite only the scope, payment-boundary, input, and acceptance wording needed for a safer quote.
Required output
1. Decision
Choose exactly one: QUOTE_CAN_BE_DRAFTED, HUMAN_COMPLIANCE_CHECK_FIRST, or DECLINE_OR_REDIRECT. Add one sentence explaining the decision.
2. Missing facts
List required facts before quote or acceptance. Prefix each item with NEEDS_CONFIRMATION.
3. Lead risk table
Use columns Severity, Area, Evidence, Risk, and Safer next step. Cover payment, platform rules, client inputs, privacy, timeline, revisions, and acceptance.
4. Safer quote skeleton
Return a concise quote skeleton with deliverables, exclusions, client inputs, schedule, revisions, acceptance, payment boundary placeholders, and human approval point.
5. No-go checklist
End with a checklist for credentials, CAPTCHA, paywalls, regulated advice, personal data, copyrighted material, fake reviews, spam, and unsupported claims.
Use assets/overseas-lead-intake.md when the lead is not structured.
