ENQUIRY REVIEW WORKSHEET Companion: Plan a review step before someone sends an enquiry Proposed CFAI guide: https://www.clickfunnels.ai/learn/enquiry-review-before-send Purpose: Specify the answers shown before sending, how a visitor changes them, which questions depend on other answers, and what evidence will verify the send. This is a planning worksheet. The example is fictional, not an implemented or tested ClickFunnels AI form. No builder admission or product capability is implied. 1. NAME THE ACTION Visitor task: _______________________________________________ Action still awaiting the visitor's decision: ________________ What that action does NOT establish: _________________________ Proposed review heading: ____________________________________ Proposed final button: ______________________________________ Does this task need a separate review step? Why? ______________ Draft-saving behavior, if any, and its evidence: ______________ Unresolved implementation questions: ________________________ 2. FICTIONAL WINDOW-DISPLAY ENQUIRY Review heading: Check your display enquiry before sending Final button: Send my display enquiry An enquiry requests a discussion. It does not book a visit, produce an estimate or prove receipt by the business. These are planned values and actions only. Reply address | The address the visitor supplied | Change reply address Discussion format | Visit my shop | Change discussion format Shop town | Brookford | Change shop town Topic | Seasonal window layout | Change topic Additional note | Not provided | Add or change additional note The note is optional. "Not provided" means a known optional blank, not a loading failure. Shop town is relevant and required for Visit my shop in this example. Display only relevant information; decide explicitly how to handle sensitive fields. Do not collect extra personal information to fill a summary. 3. YOUR SUMMARY ROWS (repeat for each relevant answer) Review label: _______________________________________________ Where the current answer comes from: _________________________ When this row is relevant: __________________________________ Display rule for a known optional blank: _____________________ Display rule for an unavailable or invalid value: _____________ Any special data-display handling: ___________________________ Change action label and accessible context: __________________ Change destination: ________________________________________ What existing value is available there: ______________________ Return point after an acceptable edit: _______________________ How the new answer is reflected on review: ___________________ Unrelated answers that must remain available: ________________ Owner and unresolved question: ______________________________ 4. MAP A DEPENDENT CHANGE Controlling answer: _________________________________________ Old choice -> new choice: ___________________________________ Questions newly required: ___________________________________ Questions no longer relevant to this enquiry: ________________ Path through new questions before returning to review: _______ Expected relevant values on the returned review: _____________ Separate storage/deletion decision and responsible owner: ____ Hiding a row does not prove deletion of a previously entered value. 5. FICTIONAL CHECK CASES -- ALL NOT RUN Use fictional inputs and an authorized environment for actual checks. V01 | Edit Topic from Seasonal window layout to Display lighting discussion. Expected: the new topic appears; unrelated relevant answers remain as entered. Status: NOT RUN. Actual observation and evidence: ___________________________ V02 | Change Visit my shop to Video call. Expected: Shop town is no longer required or shown as a relevant answer. Status: NOT RUN. Actual observation and evidence: ___________________________ Data-handling decision remains separate from the displayed summary. V03 | Start with Video call and NO town available; change to Visit my shop. Expected: ask for the required town before returning to a complete review. Status: NOT RUN. Actual observation and evidence: ___________________________ Do not assume this case reuses the town from V02; its starting state is separate. V04 | Review context is unavailable or expired. Expected: explain the known state and supported recovery. Do not invent answers or imply an enquiry was sent. If recovery is unspecified, mark it unresolved. Status: NOT RUN. Actual observation and evidence: ___________________________ For each actual case record: Version / environment / permitted test scope: ______________________________ Starting answers and context: _____________________________________________ Exact action: _____________________________________________________________ Returned answers / message / focus observation: ____________________________ Status: NOT RUN / BLOCKED / OBSERVED AS EXPECTED / ISSUE OBSERVED Evidence location and observation time: ___________________________________ Owner / proposed change / recheck version and result: ______________________ 6. VERIFY THE FINAL SEND SEPARATELY Latest reviewed relevant answers: _________________________________________ Permitted final-send check and expected effects: ___________________________ What the receiving record actually contains: _______________________________ Evidence of receipt (separate from on-screen values): ______________________ What the confirmation is justified in saying: _____________________________ Handling when submission state is unknown: _________________________________ Behavior at an old bookmark/direct review address: _________________________ Unresolved items, owner and next check: ____________________________________ An updated screen is not evidence of an updated receiving record. A saved enquiry is not a booked consultation. Keep each conclusion within the evidence observed. Source principle: GOV.UK Design System, Check answers https://design-system.service.gov.uk/patterns/check-answers/ The fictional task and cases are editorial planning examples, not outcome claims. For CFAI workflow/access requirements: https://www.clickfunnels.ai/agents