FUNNEL HELP-REQUEST WORKSHEET Companion: Prepare a useful help request when a funnel task gets stuck Purpose: describe one obstacle and the next useful question without guessing the cause or sharing unnecessary data. Preparing this packet sends nothing, grants no access and makes no support-response or repair promise. WORKED EXAMPLE — FICTIONAL, NOT A REPORTED CFAI DEFECT Summary: Garden-layout page opens worksheet v2 while promising v3. Task: Open the current worksheet from the main resource link. Page reference: G3, an invented page draft. Environment: agreed review environment in this fictional scenario. Browser / operating system versions: unknown; obtain if needed for a real report. Occurrence: October 10, 2026, 10:15 America/Chicago (invented). Starting state: G3 introduction open; no form, checkout or account action involved. Steps represented: 1. Read text beside "Open the layout worksheet." 2. Activate that link. 3. Read the version identifier on the opened file. Expected: version 3. Expectation basis: page promise plus content owner's intended v3 file, both assumptions in this example. Fictional actual observation: opened file identifies itself as version 2. Repeat history: one represented occurrence; second attempt not checked. Other browsers / editor / public page: NOT CHECKED. Cause: UNKNOWN. Affected visitors or lost enquiries: UNKNOWN. Narrow impact: reviewer cannot confirm intended worksheet destination. Proposed evidence: crop of link and nearby promise; file's visible version label. Actual example attachments: NONE. No PDF or screenshot was created. Requested next step: page owner checks intended file target and identifies the page/file version for a later recheck. Real product runtime verified: NO. Later recheck: NOT RUN. ILLUSTRATIVE INTERMITTENT VARIATION — NOT AN ADDITIONAL EXECUTED TEST First attempt opens v2; later permitted attempt opens v3. Conditions that changed: UNKNOWN. Repeatable sequence: NOT ESTABLISHED. Conclusion: retain both observations; do not claim fixed, always broken, a cause or a reliability percentage. No second attempt was performed for this example. YOUR REQUEST — ONE OBSTACLE Summary: Visitor/creator task: Product and relevant host: Exact private project/page reference (retain only in appropriate work area): Shareable neutral label or redacted address: Page/file version: Editor / preview / public page / other: Browser version: Operating system version: Occurrence date, time and time zone: Starting state: Step 1: Step 2: Step 3: Expected result: Expectation source (page promise / agreed brief / current docs / unknown): Actual observation: Exact relevant wording or file identifier: What remains unknown: Attempts already made and individual results: Last known working observation, if any (otherwise UNKNOWN): Narrow impact actually observed: Wider impact not established: BEFORE ANOTHER ATTEMPT What could another attempt change, submit, send, charge or publish?: Permission and controlled setting: Decision (permitted recheck / stop before action / ask owner): Reason: Do not repeat a live side effect merely to fill in a missing result. EVIDENCE LIST — COPY FOR EACH ITEM Item: Which statement does it support?: Original location and access owner: Shareable copy, if appropriate: Sensitive or unrelated values removed: Does the filename, content or address still reveal unnecessary information?: If URL was redacted, has that limitation been labeled?: Who may receive this copy, through which established channel?: What necessary detail remains unavailable?: No actual artifact? Write PROPOSED ONLY; do not label it attached. BEFORE SHARING [ ] No password, token, secret key, session identifier or unreviewed log. [ ] No unnecessary customer information or complete customer list. [ ] Final attachment opened and checked, not merely renamed. [ ] Product, host and environment are stated or explicitly unknown. [ ] Expected result and its source are distinct from actual observation. [ ] Unknown cause or wider impact has not become a diagnosis. [ ] Intended recipient/channel is established; this worksheet does not send. [ ] Account access follows the existing authorized process. NEXT STEP Question or decision requested: Intended owner: Current request status (prepared / sent under separate authority / reply received): Response actually received: Proposed change or instruction: Changed version: Permitted recheck and scope: Recheck result: NOT RUN Date / evidence after actual recheck: Remaining issue or uncertainty: Next owner/action: Primary reading: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html#data-to-exclude Product identity: https://www.clickfunnels.ai/learn/choose-clickfunnels-product-and-ai-connection CFAI workflow and access owner: https://www.clickfunnels.ai/agents