capture-website-intake-in-smokeball: native input mapping Bring website enquiries into intake Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs ApprovedFormSpecification -> native-approvedformspecification-template.txt Required content: Existing form ID/link or code, approved questions, observed CRM destinations, existing notified roles, plan/region and missing receipt evidence. Complete each required field from approved source evidence. WebsiteBrief -> native-websitebrief-template.txt Required content: Approved placement, privacy/confirmation wording and developer handoff requirements. Complete each required field from approved source evidence. Scope -> native-scope-template.txt Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Complete each required field from approved source evidence. Old files and reviewed mapping form-policy-template.txt Original first line: Practice area: [required] input-preparation.txt Original first line: Supply practice area, jurisdiction, approved minimal field policy, approved privacy wording and intake reviewer. Verify Smokeball plan/region and website access before implementation. Prepare a field specification only: labels, purpose, required/optional state, help text and owner. Do not collect real details during the pilot. form-policy-template.txt and input-preparation.txt -> ApprovedFormSpecification and WebsiteBrief: carry approved minimal questions, privacy/confirmation wording, placement and developer requirements only after verifying the current form and CRM mapping. Acquire real existing form ID/link/code, current notified roles and plan/region evidence separately. Record missing receipt evidence in ApprovedFormSpecification and Scope. A proposed field specification is not a generated link, submitted enquiry, delivery receipt or tested website integration. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. Responsible lawyer/operations reviewer approves scope, definitions and any later action. AI optional; use only approved minimized data and retain originals separately. No website edit or actual inquiry is created. Exact receipt/export UI across regions remains account-dependent. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Inspect the existing form and link Location: Desktop File > Intake Forms; or web Settings gear > Intake Forms > selected Lead Intake Form > three-dot menu > Web Enquiry Link Actions Copy an existing form link/code only if already present. Read approved form fields and the existing notified staff. If no link exists, capture that blocker; creating a link, selecting notifications and activating is a later authorized build. Verification: US and AU/UK menus differ. US help also documents Settings > Intake > New Link and the Form Builder Share flow; choose the route actually visible in the subscribed region. https://support.smokeball.com/hc/en-us/articles/8015208933911-Set-up-and-manage-Lead-Intake-forms https://support.smokeball.com/hc/en-us/articles/16155606566679-Getting-Started-with-Intake Do not proceed when - Missing approved form, real generated link/code, mapping evidence, notification owner or regional feature access. Scope template requirements Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documented form/link build handoff; receipt-view validation remains account-specific and blocked until observed; not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.