Qualify Meeting

Purpose

Assess meeting appropriateness against explicit evidence. Keep account eligibility, interest, authority, meeting purpose, and consent separate.

Required inputs

• Exact relevant messages with authors and dates
• Independently verified contact and account eligibility
• Current contact-specific opt-out or stop-contact status
• Declared meeting criteria and disqualifiers
• Supplied role, problem, purpose, stakeholder, authority, timing, and next-step evidence

Mark absent or unverified inputs Unknown; a title alone never proves authority.

Workflow

1. Preserve the exact evidence and separate facts, inferences, and unknowns.
2. Evaluate hard gates first. An ineligible contact, opt-out, stop request, or clear negative makes the result NOT YET — STOP; do not propose outreach. Missing gate evidence makes it NOT YET — NEEDS VERIFICATION.
3. Evaluate each criterion independently: account/contact fit, expressed interest, defined meeting purpose, relevant problem, stakeholder involvement, authority evidence, timing, and explicit meeting consent. Use MET, PARTIAL, NOT MET, or UNKNOWN with a source for each.
4. Treat role or seniority only as persona-fit evidence unless the record explicitly supports authority. Treat a positive reply or information request only as limited interest; it is not purchase intent, qualification, availability, or meeting consent.
5. Return APPROPRIATE only when eligibility passes, no stop applies, the meeting has a supported purpose, required declared criteria are met, and explicit meeting consent is supplied. Otherwise return NOT YET and name the exact gaps.
6. Recommend only the smallest supported reviewable next step. Honor an overview or information request before suggesting a meeting. Do not draft copy, book, reserve, send, or update systems.

Output format

• Decision: APPROPRIATE, NOT YET, NOT YET — NEEDS VERIFICATION, or NOT YET — STOP
• Decision reason and blocking gaps
• Evidence ledger: exact quotes and supplied records
• Criteria table: criterion, status, evidence, inference, unknown
• Eligibility versus meeting-readiness summary
• Smallest supported next step for human review
• Actions taken: None

Guardrails

• Never invent authority, budget, urgency, timing, need, consent, contactability, availability, stakeholder interest, or calendar state.
• Never infer authority solely from a job title or infer meeting consent from interest, referral, or an information request.
• Never target from protected traits or unnecessary sensitive data.
• Never browse, draft outreach, send, book, schedule, use credentials, or mutate an external system.

Quality check

Confirm every criterion has evidence or an explicit unknown; eligibility is separate from readiness; interest alone cannot yield APPROPRIATE; meeting consent is explicit; the next step matches the reply; and no action occurred.

Example invocation

Use qualify-meeting to assess Avery Lin's overview request against fit, interest, purpose, authority, and consent without treating the request as a meeting agreement.