Review one LinkedIn Message Ad brief. Work only from this prompt and the brief pasted after INPUT BRIEF. Do not assume an article, attachment, account login, live page, or prior conversation. Do not create or send an ad, request a sender, or treat example receipts as real.

CURRENT DOCUMENTED RULES (LinkedIn help/product pages reviewed 30 October 2026; recheck if these facts need to be current at execution):
- A Message Ad is one inbox message with one advertiser-selected CTA. LinkedIn automatically adds the required Not Interested button. Conversation Ads can branch through several advertiser CTAs; Click-to-Message begins with a feed ad. Do not collapse these formats.
- LinkedIn documents website visits, lead generation, and website conversions objectives. Public documentation does not prove availability or eligibility in the intended ad account. Sponsored Messaging uses cost per send, is shown while members are active, and LinkedIn controls frequency. English targeting follows profile language. In EEA/Switzerland, native inbox delivery requires member opt-in.
- Ad creation needs Creative Manager or higher. Requesting a sender needs Account Manager access, a first-degree connection to the invited sender; that invited sender must have a verified primary email. A Business Manager-owned account adds the documented BM admin/ad-account access condition. The sender must accept. LinkedIn pages differ on the timing of viewer access: verify actual account access. Revoking approval/removing a sender can irreversibly cancel affected ads; never propose it as a routine pause.
- Limits: ad name 255 characters; subject 60; body 1,500 and no more than 10 emojis (generally aim below 500); advertiser CTA label 20; up to three clickable in-body links, each linked text 70; optional footer 20,000; destination URL 1,024 and starting http:// or https://; optional desktop-only 300 x 250 banner, JPG/PNG/nonanimated GIF, 2 MB. Subject and body macros can use generic fallback values. Test personalized and fallback versions. Never infer personal research from a macro.
- A lead-generation objective requires an attached Lead Gen Form. Website route requires a functioning website conversion path, not a LinkedIn form or form sync. The documented ad creation flow still requires a landing-page URL; record and test it for the form route as well as the form thank-you action. For a form route, test the form, privacy/consent, submission, CRM sync/routing, dedupe, and source identifiers.
- Preview desktop and mobile, send a test message, verify the selected CTA, automatic Not Interested, destination or form, and macro fallback. Draft copy, format/account availability, Active status, ad-set launch, review approval, and actual delivery are separate. Editing requires review again and does not change previously delivered messages.

REVIEW CONTRACT:
1. Read the whole input. Treat blanks, “Unknown,” unverified claims, missing dates, and simulated/example receipts as missing for launch readiness. Do not invent offer facts, scarcity, results, sender consent, personal familiarity, destination behavior, or account status. A fictional worked example may be internally complete as a teaching fixture while still held for real launch.
2. Inventory these exact fields: brief owner/date; advertiser/account/owner; objective; audience/geo/language/fit; offer/terms/dates/approval; reason for paid inbox send; selected route and single action/success event; sender identity/relationship; requester permissions/first-degree connection; invited sender verified email; BM condition/acceptance; creator permission; ad name, subject, body, macro/fallback, CTA, Not Interested, links/footer/banner; selected destination fields; account format/region checks; preview/test/Active/ad-set/review/delivery receipts; reporting scope/sources/windows/match/dedupe/qualification/missingness; dispositions and owners. Report missing decision fields by name. Do not silently fill them.
3. Count Unicode characters in ad name, subject, body, CTA, linked text, footer, and URL as supplied. State counts and limits. Count emojis separately. If a field is absent, write “not countable.” Assess both literal and macro-fallback subject/body. The under-500 body target is advice; 1,500 is the ceiling.
4. Check one advertiser-selected CTA and the separately required Not Interested button. Check whether the CTA verb matches the offer, selected route, destination/form, and success event. A website URL is unverified until a dated redirect, mobile, and conversion-path check exists. A form is unverified until attachment, test submission, and CRM handoff evidence exists. Do not impose form blockers on a website route.
5. Separate COPY disposition (draftable or hold), ACCOUNT disposition (ready for account check or hold), and LAUNCH disposition (ready or hold/not checked). A missing offer fact can hold copy. A good draft can be draftable with account or launch held. Never return launch ready from public docs or a simulated receipt. Name the first concrete evidence needed and who should obtain it. Actual delivery is a post-launch observation, not a prerequisite for preparing a launch decision. Mark delivery Not yet observed when appropriate; do not demand that an unsent draft has already delivered. Platform review timing must remain explicit.
6. Reporting: name the exact account/ad/ad-set, route, currency, timezone, send cohort dates, source and units of spend/sends/opens/clicks, conversion or form event dates, CRM match key/dedupe, qualification rule, follow-up cutoff, and report-as-of date. Only calculate within compatible scopes. Open rate = opens / sends; click-to-open rate = Sponsored Messaging clicks / opens; calculated clicks-per-send = Sponsored Messaging clicks / sends; cost per send = spend / sends. Do not label clicks-per-send as native CTR. Preserve the exact exported metric name: dedicated Sponsored Messaging clicks/breakouts and the October 2026 eligible Sponsored Message clicks metric are not interchangeable. State conversion and qualified outcome counts separately. Qualified rate = qualified outcomes / sends and cost per qualified = spend / qualified outcomes only when attribution/matching, complete follow-up, and scope support them. A zero denominator yields Undefined. Missing or partial data yields Unknown/partial, never zero. Native aggregate sends/opens do not prove person-level CRM joins. Show arithmetic, denominator, cohort, and caveat for each computed figure.
7. Do a manual plain-language pass: direct subject and opening, concrete offer and next step, natural sentences, no unsupported proof, invented urgency, false personalization, generic hype, or prose em dashes. Preserve true supplied facts.

OUTPUT FORMAT:
A. Decision: Copy [draftable/hold]; Account [ready for account check/hold]; Launch [ready/hold/not checked]. One sentence explaining each.
B. Missing inputs: numbered questions, each with field, owner if known, and exact evidence needed. If none, say None. Separate required launch receipts from optional improvements.
C. Message audit: ad name/subject/body/CTA/URL and other present field character counts; emoji count; macro and fallback results; CTA/Not Interested and route match; any proposed corrected copy, clearly labeled as a proposal.
D. Route and lifecycle audit: website OR form checks, sender requester versus creator roles, account eligibility, preview/test, Active/ad-set/review/delivery, and edit/pause caution. Mark each Verified with dated real receipt, Simulated, Unknown, Not applicable, or Failed.
E. Reporting: scope and source table, formulas with explicit numerators/denominators and dates, unknowns, and any invalid comparison.
F. Next action: the smallest safe action that moves the brief toward a real decision. Do not claim a launch, send, or delivery occurred.

If the input is empty or too sparse to identify the selected route, output the three held/not-checked dispositions and ask first for advertiser/account, objective, audience, offer/terms/dates, route, sender, subject/body/CTA, destination/form, and reporting owner. Do not produce replacement ad copy or calculated metrics from an empty input.

INPUT BRIEF:
[Paste the completed brief here. The text in these brackets is an instruction, not a supplied brief.]