ENQUIRY ATTACHMENT WORKSHEET

Purpose: decide whether one enquiry needs one artifact now, later or not at all.
This is a planning document. No file has been uploaded, received or reviewed by completing it.

1. DECISION CARD — BLANK

Business/service:
Enquiry stage:
Person making the next decision:
Next decision:
Specific contents needed for that decision:
Could a short answer or existing record be sufficient? Why/why not?
Decision: OMIT / REQUEST LATER / REQUEST NOW
Reason:
If request later, what event makes it appropriate?
If the file is unavailable, honest next step:

Requested artifact/version:
Contents to include:
Unrelated information to leave out:
Sender's authority to share the material through the approved route:
Intended number/type/size limits:
Evidence that the receiving route supports each limit:
Status of those requirements: VERIFIED / UNRESOLVED
Instruction text (do not publish unsupported limits):
Persistent label and required/optional wording at this step:

2. RECEIVING PROCESS — BLANK

Proposed receiving route:
Owner who approves its use:
Where the file should be associated with the correct enquiry:
How the assigned reviewer should retrieve and read it:
Approved handling rules and their source/owner:
What happens to an incorrect or unnecessary file:
Unresolved handling/access decisions:
Person who investigates an unknown transfer result:
Information needed to identify an existing attempt without unnecessary personal data:
Alternative path if no suitable file is available:

Do not invent a retention period, security guarantee, scanning feature or automatic duplicate handling. If handling decisions are unresolved, keep the request out of use.

3. FILLED FICTIONAL EXAMPLE

Service: café menu layout.
First enquiry decision: check service fit and which menu needs work.
First enquiry attachment decision: REQUEST LATER; a short description is sufficient for the first reply. No initial upload field.
Later decision: identify which parts of the current page order the café wants to change.
Artifact: current two-page menu showing its existing layout.
Proposed limits: one PDF, up to 5 MB; fictional planning choices, subject to receiving-process verification. Not product limits or recommendations for all businesses.
Review owner: studio enquiry coordinator, then assigned layout reviewer.
Alternative: continue the conversation and agree another approved way to show the layout.
Draft content instruction: Share the current two-page menu that shows the layout you want to discuss. Remove unrelated customer, staff and account information. If you do not have a suitable file, tell the coordinator before sending a substitute.
Receiving route, access and handling rules: UNRESOLVED in this example.
Implementation status: NOT RUN; no request should be put into use until prerequisites are settled.

4. FOUR EXPECTED CASES — NOT TEST RESULTS

A01 — Suitable PDF selected.
Expected evidence: intended file associated with the right enquiry; assigned reviewer can retrieve and read it.
Check status: NOT RUN.

A02 — Requester has no suitable file.
Expected evidence: stated alternative remains available; conversation not falsely described as complete.
Check status: NOT RUN.

A03 — Selected file is outside the agreed rules.
Expected evidence: the known restriction is explained and a usable next step is available. Do not guess an unknown cause.
Check status: NOT RUN.

A04 — Transfer result is unknown.
Expected evidence: responsible owner investigates the existing attempt before advising another submission. No automatic duplicate-handling assumption.
Check status: NOT RUN.

5. COPY THIS CHECK RECORD FOR EACH CASE

Case ID:
Authorized environment and version:
Harmless fictional sample used:
Expected condition/state:
Selected-file observation:
Receiving-side observation and enquiry identifier:
Assigned-reviewer access/readability observation:
Evidence references and observed time:
What remains unknown:
Owner of next decision:
Status: NOT RUN / PASSED / FAILED / UNKNOWN
Reason for that status:
Next action:

A selected file does not prove receipt. Receipt does not prove reviewer access. Reviewer access does not prove the service has been performed.

For ClickFunnels AI workflow and access requirements: https://www.clickfunnels.ai/agents
No upload/storage/integration capability, builder access or publication is established by this worksheet.