SKILL.md

---
name: joinways-qualify-lead
description: Qualify an inbound inquiry for an event venue with Joinways - review the lead, check space availability for the requested date, assess fit against capacity and requirements, and prepare a first reply.
---

# Qualify an inbound lead

Use this skill when the user asks to qualify, review, triage, or respond to a new inquiry or lead in Joinways.

## Workflow

1. **Fetch the lead.** If the user gives a lead id or name, call `get_lead`. Otherwise call `list_leads` filtered to recent or new leads and confirm which one the user means.
2. **Extract the request.** From the lead, identify: requested date(s), guest count, event type (wedding, corporate, other), requested space if any, budget hints, and the contact to reply to. List what is missing.
3. **Check availability.** Call `check_venue_availability` for the requested date(s). If the lead does not name a space, call `list_venue_spaces` and compare each space's capacity with the guest count to shortlist options.
4. **Assess fit.** State clearly whether the venue can host the event: date free or not, capacity sufficient or not, and any constraint found in the data. Do not guess anything the tools did not return.
5. **Summarize.** Give the user a short qualification verdict: good fit, conditional fit (say what is missing), or no fit (say why), plus a recommended next action.
6. **Draft the reply.** If the user wants to answer, call `generate_email_draft` with the qualification facts (availability, suggested spaces, follow-up questions for missing info). Show the draft.
7. **Send and update only on approval.** Call `send_event_email` only after the user explicitly approves the draft, and `update_lead_status` to reflect the outcome (qualified, waiting on client, not a fit).

## Guardrails

- Never state availability, capacity, or pricing that did not come from a tool call.
- Never send an email or change a lead status without explicit user approval in this conversation.
- If dates are ambiguous (no year, relative wording), confirm the exact date with the user before checking availability.