Bring website enquiries into intake
Get the source data and prepare the review

Documented form/link build handoff; receipt-view validation remains account-specific and blocked until observed; not tested

WHAT WAS CHECKED
Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- No website edit or actual inquiry is created. Exact receipt/export UI across regions remains account-dependent.

STOP IF
- Missing approved form, real generated link/code, mapping evidence, notification owner or regional feature access.

KEEP THE ANALYSIS COPY SEPARATE
Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent.

INPUT FORMAT LIMIT
All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data.

NATIVE REVIEW INPUTS
version: 1
status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible
compatibleWithoutMapping: False
existingKitFilesInspected: - file: form-policy-template.txt
firstLine: Practice area: [required]
- file: input-preparation.txt
firstLine: 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.
requiredNativeInputs: - name: ApprovedFormSpecification
kind: approved_text_section
proposedDistinctTemplate: native-approvedformspecification-template.txt
requiredContent: Existing form ID/link or code, approved questions, observed CRM destinations, existing notified roles, plan/region and missing receipt evidence.
- name: WebsiteBrief
kind: approved_text_section
proposedDistinctTemplate: native-websitebrief-template.txt
requiredContent: Approved placement, privacy/confirmation wording and developer handoff requirements.
- name: Scope
kind: approved_text_section
proposedDistinctTemplate: native-scope-template.txt
requiredContent: 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.
templateFilesCreatedByThisTask: False
requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence.

OPEN THE INPUT MAPPING GUIDE
NATIVE-INPUT-MAPPING.txt
Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain.

ApprovedFormSpecification: native-approvedformspecification-template.txt
WebsiteBrief: native-websitebrief-template.txt
Scope: native-scope-template.txt

STEP 1: Inspect the existing form and link
Tool: Smokeball, US documentation
Open: Desktop File > Intake Forms; or web Settings gear > Intake Forms > selected Lead Intake Form > three-dot menu > Web Enquiry Link Actions
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Existing form/link specification, or an explicit no-link blocker.
Use it next: Provide only the public form question specification and placeholder internal field names to the drafting workspace.
Check: 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.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
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

STEP 2: Draft from the approved source packet
Tool: Acrobat PDF Spaces / AI Assistant, optional
Open: Acrobat home > PDF Spaces > Create a PDF Space > Paste copied text > Add to PDF Space > chat
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: downstream_application_ai

Paste only the approved nonconfidential packet, source IDs and full Scope note. Paste the exact prompt into the Space chat. Do not upload raw client records; this is a downstream drafting assistant, not an AI in the source application.

PASTE THIS PROMPT
Using only the approved Smokeball form specification and website brief, prepare a website-intake handoff: existing form ID/link, proposed placement, allowed questions, intended Smokeball field destinations, notified-role aliases, confirmation wording and synthetic test cases. Mark unknown field mappings, receipt evidence, required disclosures or notification owners blocked. Do not create new legal questions, promise representation, fabricate an embed code or form URL, or activate anything.

Expected output: Website-developer and intake-owner implementation checklist.
Use it next: Copy reviewed output into an internal review document or the named downstream tool, preserving evidence IDs.
Check: The AI must copy a real existing code/link verbatim or leave it missing; it cannot generate product-specific embed credentials.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html
https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html

STEP 3: Give the operator the native build path if approved later
Tool: Smokeball form owner and website developer
Open: Form Builder > Share > Create Link and QR Code > internal link name / notification staff > Create Link and QR Code > Share > Copy Link or Copy Code
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

This is a future handoff only. An authorized operator verifies regional controls and permissions, creates or reuses the approved link, and gives the unchanged generated code to the website developer. The Active toggle and website publication are separate release gates.

Expected output: Approved link/code handoff plus release checklist; not a published form.
Use it next: Developer implements only in the authorized website environment; staff tests with synthetic data after explicit approval.
Check: US documentation verifies generated embedding, not automatic arbitrary-form import or a generic intake-export CSV.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.smokeball.com/hc/en-us/articles/8015208933911-Set-up-and-manage-Lead-Intake-forms

STEP 4: Human review and final action
Tool: Responsible firm reviewer
Open: Internal Review worksheet / review document
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

Form owner verifies each synthetic submission reaches the intended lead and mapped fields, notification recipients and retained form evidence before release. Current research performs no submission, activation or website edit.

Expected output: Reviewed implementation/test plan; deployment remains untested.
Use it next: If receipt evidence is unavailable, keep launch blocked and ask the firm’s Smokeball administrator to verify the regional intake view.
Check: Existing intake access may require Prosper+ or an Intake add-on on Grow/Boost; exact subscription was not inspected.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.smokeball.com/hc/en-us/articles/16155606566679-Getting-Started-with-Intake
https://support.smokeball.com/hc/en-us/articles/8015208933911-Set-up-and-manage-Lead-Intake-forms

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- The live account, entitlement, exact headers, records and field coverage have not been observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
