# Zapier Agents + Jodoo Lead Qualification Recipe

## Agent prompt

You are a lead qualification agent for a B2B sales team. Review each inbound lead and return structured fields that Jodoo can store, route, and report on.

Score the lead from 0 to 100 using these signals:

- Fit: Does the company and request match the offer?
- Intent: Is the lead asking for something close to purchase, evaluation, or implementation?
- Urgency: Is there a clear timing signal?
- Company relevance: Is the company type, size, region, or workflow relevant?
- Missing information: What details should sales collect before follow-up?

Return only structured output using the schema below. Do not return a loose paragraph without these fields.

```json
{
  "ai_score": 0,
  "lead_tier": "hot | warm | nurture | disqualified",
  "fit_reason": "One short reason a sales owner can trust",
  "missing_info": ["Missing detail 1", "Missing detail 2"],
  "suggested_owner": "Sales owner or queue",
  "next_best_action": "Recommended next step",
  "follow_up_draft": "Short email or call note",
  "routing_priority": "high | medium | low"
}
```

## Jodoo starter app

Use the starter app created for this workflow as the Jodoo writeback target:

- App name: AI Lead Qualification
- Form name: Lead Qualification Record
- Public template URL: not packaged as a one-click clone template
- App ID: 6a1f85776c9c72ae9990793f
- Form ID: 6a1f85989cf23588e17c40ba

The starter app field model includes lead source, contact details, campaign, request text, AI score, tier, fit reason, missing information, suggested owner, next best action, follow-up draft, routing priority, review status, and original agent output. Use the blueprint to recreate or adapt the app; it is not a one-click clone template.

## Tier rules

- Hot: score 80-100. Strong fit, clear intent, or urgent timing.
- Warm: score 55-79. Reasonable fit, but timing or context needs review.
- Nurture: score 25-54. Potential future fit, but not ready for sales action.
- Disqualified: score 0-24. Poor fit, spam, student request, vendor pitch, or irrelevant message.

## Zapier workflow

1. Trigger: receive a new form submission, email, spreadsheet row, partner lead, or Jodoo form record.
2. Formatter step: normalize the lead source, contact details, company, message, and request type.
3. Zapier Agents step: run the lead qualification prompt.
4. Parser or mapping step: map each structured agent field to a Jodoo field.
5. Jodoo action: create or update the lead qualification record.
6. Filter: if routing priority is high, continue to notification or task creation.
7. Notification: send the owner a message with score, reason, and next best action.
8. Review queue: if missing information exists, place the lead in a Jodoo review view.

## Jodoo mapping

| Agent output | Jodoo field |
| --- | --- |
| source record name | Record title |
| ai_score | AI score |
| lead_tier | Lead tier |
| fit_reason | Fit reason |
| missing_info | Missing information |
| suggested_owner | Suggested owner |
| next_best_action | Next best action |
| follow_up_draft | Follow-up draft |
| routing_priority | Routing priority |
| full JSON response | Original agent output |

## Test leads

### Hot lead

Company wants to replace manual spreadsheet lead routing this month, asks for a demo, and names their sales operations pain.

Expected result: high score, hot tier, demo or sales call as next action.

### Warm lead

Company asks for workflow automation examples but gives little timing or team context.

Expected result: medium score, warm tier, request more details before routing.

### Nurture lead

Student, vendor pitch, generic research request, or no business context.

Expected result: low score, nurture or disqualified tier, no urgent owner notification.

## Zapier plan note

The first test run was completed on the free Zapier plan. Production use may require a paid Zapier plan depending on task volume, premium app usage, polling speed, and routing complexity.