CFAI PLANNING WORKSHEET: HELPFUL FORM-ERROR COPY Use with: Write form errors that help someone finish. Proposed guide owner: https://www.clickfunnels.ai/learn/funnel-form-error-messages This owner is a planned route until publication is separately verified. Purpose: connect a known correctable field condition to clear wording and a clearing condition. This does not implement validation, prove saving/delivery, certify accessibility or grant CFAI access. Current workflow: https://www.clickfunnels.ai/agents FICTIONAL EXAMPLE — TEAM PHOTOGRAPHY WORKSHOP ENQUIRY All rules, wording and expected behavior below are invented planning inputs. Actual form: NONE. All implementation results: NOT RUN. Passing field checks does not prove saving, email delivery or workshop booking. EXAMPLE RULES ALREADY CHOSEN FOR THIS EXERCISE R1. Email for our reply is required. The process can distinguish an empty value from a value missing an @ sign. Other address rules are not specified here. R2. What would you like to practise? requires one choice: Product photos; Team portraits; Something else; Help me choose. R3. Describe the other topic is required only when Something else is selected. R4. Company name (optional) may remain blank. These are not recommended universal fields or evidence of CFAI behavior. E01 — EMPTY EMAIL Rule source: fictional R1 Exact field label: Email for our reply Known trigger: required value is empty Old wording: Required field Proposed field message: Enter an email address for our reply Proposed summary entry: Enter an email address for our reply Summary target: Email for our reply control Clearing condition: the empty-value error clears when a value is supplied and the rule is re-evaluated; another known format condition may need its own message Do not claim: supplied address exists, belongs to visitor or has received email Implementation result: NOT RUN E02 — SPECIFIC EMAIL FORMAT PROBLEM Rule source: fictional R1 Exact field label: Email for our reply Known trigger: nonempty entered value is missing an @ sign Old wording: Invalid email Proposed field message: Add an @ sign to the email address for our reply Proposed summary entry: Add an @ sign to the email address for our reply Summary target: Email for our reply control Clearing condition: this particular condition no longer applies after correction and rule re-evaluation; other known rules remain separate Do not claim: adding @ alone makes an address deliverable, owned or fully acceptable Implementation result: NOT RUN E03 — NO TOPIC SELECTED Rule source: fictional R2 Exact field label: What would you like to practise? Known trigger: no listed choice is selected Old wording: Selection error Proposed field message: Choose what you would like to practise, or select Help me choose Proposed summary entry: Choose what you would like to practise, or select Help me choose Summary target: the practice-topic question's appropriate control Clearing condition: one supported choice is selected and the rule is re-evaluated Valid uncertainty: Help me choose Implementation result: NOT RUN E04 — CONDITIONAL DESCRIPTION EMPTY Rule source: fictional R3 Exact field label: Describe the other topic Known trigger: Something else is selected AND the description is empty Old wording: Tell us more Proposed field message: Describe the other topic you want to practise Proposed summary entry: Describe the other topic you want to practise Summary target: Describe the other topic control Clearing condition: required description supplied, OR another supported topic choice means R3 no longer applies, followed by rule re-evaluation Separate unresolved decision: handling any previous other-topic text after switching choices; no retention or deletion behavior assumed Implementation result: NOT RUN ACCEPTED EMPTY ANSWER Company name (optional): blank Expected field error: NONE under fictional R4 Implementation result: NOT RUN TWO-ERROR WALKTHROUGH — EXPECTATIONS ONLY Starting condition: email empty; Something else selected; other-topic description empty; optional company name blank. Expected active errors: E01 and E04. Expected summary entries, also used beside their respective fields: - Enter an email address for our reply - Describe the other topic you want to practise Actual observation: NOT RUN Correction 1: supply an address accepted by the example's format rule. On next validation pass: E01 absent; E04 remains. Actual observation: NOT RUN Correction 2: select Help me choose instead of Something else. On next validation pass: E04 absent; conditional description no longer required. Optional Company name: still permitted blank. Actual observation: NOT RUN Saved request / sent email / booking: NOT ESTABLISHED by any of these steps. PROBLEMS EXCLUDED FROM FIELD CORRECTIONS Workshop no longer accepts enquiries: business availability explanation required; do not tell the visitor to change correct contact information. Unknown save result: use the actual state/recovery plan; do not invent failure, success, a status lookup, a support deadline or a safe resubmission instruction. YOUR FORM — REPEATABLE MESSAGE RECORD Page/form/version: Planning date: Rule owner: Rule source and date: Field's exact visible label: Related choices / condition making this field applicable: Known problem the system can identify: What the visitor can change: Proposed field message: Matching summary message: Summary target: Instruction or example already shown near the field: Condition that removes this error: Other answers expected to remain available: Sensitive or conditional value-handling decision needing its own review: Unsupported claim to exclude: Open question / owner / next action: PERMITTED IMPLEMENTATION CHECK Environment and form/version: Permission / safe test-data and side-effect boundary: Starting choices and known condition: Expected message and associated field: Actual message and associated field: Does the summary wording match? Does its link reach the intended answer? What remains after the first correction? What changes when the conditional question stops applying? Keyboard and assistive setup used / focus and announcement observations: Answers retained or changed, if checked: Status: NOT RUN / BLOCKED / OBSERVED AS EXPECTED / ISSUE OBSERVED Evidence reference (no unrelated customer data or secrets): Owner / next step / recheck version: Copy approval is separate from an implementation result. Resolve one known condition clearly before extending the message plan to another one.