---
name: inquiry-review
description: Route synthetic bilingual buyer inquiries into review-only queues. Use when checking DEMO- ids, example-domain mail, missing fields, or unverified price/certification claims. Never send mail or write CRM.
license: Apache-2.0
compatibility: Offline Node 22 policy script only. No network, credentials, models, or production n8n.
metadata:
  task: synthetic-inquiry-routing
  policy: examples/inquiry-routing/policy.mjs
---

# Inquiry review (synthetic)

You classify **shipped synthetic fixtures only**. Routing is a queue label, not delivery.

## Hard rules

1. Call the local policy (`policy.mjs` `routeInquiry`) or the MCP tool `route_synthetic_inquiry`. Do not reimplement heuristics from memory.
2. Every result has `requiresHumanReview: true` and `sendAllowed: false`. Do not flip them.
3. Do not invent prices, stock, lead times, certifications, or human approval.
4. Do not echo the original email or message in your own summary.
5. Regex hits are triage hints, not injection or compliance proof.

## Inputs

JSON object with only `id`, `email`, `language`, `message`, `quantity`. See the repository README for exact formats. Unexpected keys are invalid.

## Expected statuses

| Status | Meaning |
| --- | --- |
| `draft_for_review` | Fixed bilingual internal draft; quantity only |
| `needs_information` | Missing required fields |
| `policy_review` | Instruction/secret or unverified-claim heuristic |
| `invalid_input` | Type, range, language, or extra keys |

Compare a full batch with `expected-output.json`. Stop on mismatch.

## Out of scope

Customer data, live models, n8n GUI, sending, and production deployment.