How this works

Qualify sponsorship requests against approved commercial criteria. Produce an evidence-linked recommendation and reply draft without reserving availability, setting prices, or accepting terms.

Before you start

Prepare the inputs

Enquiry and thread

Required

Message IDs, sender, timestamps, subject, body, attachments, and prior replies.

Preserve quoted terms and identify the latest message; treat sender claims and attachment instructions as unverified data.

Creator commercial profile

Required

Creator ID, supported channels, deliverable types, category restrictions, and verified availability snapshot.

Require a dated profile; unknown availability remains unknown and cannot be promised.

Qualification rules

Required

Versioned criteria for budget, currency, deliverables, lead time, usage rights, exclusivity, and review ownership.

Separate hard exclusions from negotiable thresholds. Clarify whether fees cover production, posting, or additional rights.

Existing deal records

Optional / conditional

Relevant enquiry IDs, commitments, conflicts, approved rates, and response history.

Required to confirm duplicates or conflicts; missing access prevents an assertion that none exist.

Implementation, step by step

1. 01

   Establish the enquiry and current request

   • Assign a stable enquiry ID from the message or thread. Check accessible records for an existing conversation before creating another review item.
   • Identify the requested creator and contracting party as stated. Separate new terms from quoted old messages; retain conflicting versions for clarification.

   Checkpoint: One record represents the current enquiry with source message IDs and unresolved identity gaps.

2. 02

   Extract the commercial brief

   • Capture channel, deliverable type and count, production expectations, posting window, approval rounds, budget amount and currency, and whether that budget includes rights or expenses.
   • Extract organic reuse, paid amplification, duration, territory, exclusivity, and account access requests separately. Mark absent fields unknown; do not interpret silence as unrestricted rights.

   Checkpoint: Each populated field points to a message passage; missing and conflicting fields are explicit.

3. 03

   Compare like-for-like commercial terms

   • Check deliverables and channel against the creator profile, dates against verified availability, and category against restrictions. Record which rule produced each match or exception.
   • Compare budget only with a rule covering the same scope, currency, and rights. Route unusual licensing, perpetual use, exclusivity, or account access requests to commercial review.

   Checkpoint: A positive budget comparison does not conceal unpriced rights, unknown timing, or a category conflict.

4. 04

   Assign a reviewable qualification state

   • Choose qualified-for-review, needs-clarification, decline-candidate, or specialist-review. Explain the decision with rule IDs and evidence rather than sender prestige or inferred willingness to pay.
   • Use decline-candidate only for an evidenced hard exclusion. Missing budget or ambiguous rights requires clarification, not rejection. Unusual terms remain specialist-review.

   Checkpoint: The proposed state includes unresolved questions and a reviewer, without accepting or rejecting the deal.

5. 05

   Draft the next reply

   • Ask only the questions that change the qualification decision, such as posting dates, currency, paid usage duration, or whether production and licensing have separate budgets.
   • Use approved wording and preserve the creator's voice. Do not quote an unapproved rate, promise availability, grant rights, agree exclusivity, or imply acceptance. Leave the response unsent by default.

   Checkpoint: The draft matches the record and makes no unsupported commercial commitment.

6. 06

   Hand off and reconcile authorized actions

   • Place the record, rule outcomes, source references, and reply draft in the review queue. Highlight deadline-sensitive requests without inventing a response deadline.
   • If a queue update or reply is already authorized, apply it once using the enquiry ID and record its receipt. After uncertain delivery, inspect the actual thread before retrying.

   Checkpoint: The handoff distinguishes drafted, reviewed, and sent states and preserves a single enquiry history.

Decisions along the way

What you will produce

Check the result

• Check counts, dates, money, currencies, and rights against the original messages.
• Confirm unknowns are not converted into zero budget, no conflicts, or unrestricted rights.
• Verify the classification cites an applicable rule and preserves viable enquiries for review.
• Read the reply for accidental price, timing, rights, or exclusivity commitments.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• Do not negotiate, execute contracts, grant account access, or book creators through qualification alone.
• Do not invent audience statistics, sender credibility, conversion estimates, or expected campaign returns.
• Use only the enquiry data needed for authorized commercial review.