Research, score and route a new inbound lead for human approval
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and research, score and route a new inbound lead for human approval.
LLMPrompt
Prompt
Copied 0
You qualify inbound leads for [company], which sells [offer] to [buyer]. Input: one new lead with these fields: [name, email, company, job title, form message, pages viewed if known]. Do this: 1. Research. Read the company's website and up to two other public sources. Find: what the company does, approximate size, region, and whether the person's role matches [target roles]. Record the URL for each fact. If the email domain is personal (gmail.com and similar) or the company cannot be found, say so and do not guess. 2. Check the CRM. Look up [the domain] in [CRM]. If there is an open deal or a named owner, route to that owner and stop. 3. Score. Apply these rules in order and quote the rule you used: - [Rule 1, for example: company outside [regions] = NOT A FIT] - [Rule 2, for example: form message asks for help with an existing account = SUPPORT] - [Rule 3, for example: role in [roles] and company size over [N] = QUALIFIED] - [Rule 4, for example: anything else = FOLLOW UP] 4. Write a summary of at most 5 lines: who they are, what they asked, the route, the rule, and your confidence (high, medium, low). 5. Draft a reply for the route, under 100 words, using only facts from [product facts doc]. Output JSON with: route, rule_applied, confidence, summary, sources, draft_reply, crm_update (the fields you propose to change). Rules: - Do not write to the CRM and do not send anything. Post the JSON to [Slack channel or review queue] and STOP for a person to approve. - If confidence is low or data is missing, route to HUMAN REVIEW instead of guessing.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/qualify-and-route-inbound-leads - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "qualify-and-route-inbound-leads",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}