REPEATED-ENQUIRY REVIEW WORKSHEET Companion to: Review repeated enquiries before treating them as duplicates Proposed guide: https://www.clickfunnels.ai/learn/repeated-enquiry-review-plan Use this record to decide what apparently repeated records mean and who owns the next step. It does not merge contacts, delete records, verify identity or send a reply. Keep originals in their existing authorized system. Use internal or fictional references here, not copied personal details or private messages. FIRST DISTINCTION Notification: a notice that may point to a saved enquiry. Saved enquiry: the record the receiving system actually holds. Business request: the work the requester wants the business to consider. Person: not established by record similarity or a matching email address. Review unit for this exercise: the business request needing a response. FICTIONAL WORKED CASES — MEADOW REPAIR STUDIO All people, references, facts and decisions below are invented. No real record was inspected, changed, merged or removed. No message was sent. Sam owns first review. Lee may prepare a reply. R01 — REPEATED NOTIFICATION Observed references in the fictional case: notices N01 and N02 point to E101. Required assumed evidence: the receiving owner confirms both notices refer to that SAME saved record, under the same system's identifier meaning. Decision: coordinate one response task for E101; preserve notice references under the existing process. This is not a rule to ignore all repeated notices. Next check: is a response already drafted or sent, and what does it address? If Lee already has a draft attached to E101, Sam coordinates that work rather than creating a competing draft. A draft does not establish sending/receipt. R02 — SEPARATE WORK References: E102 concerns a chair; E103 concerns a cabinet. Required assumed evidence: the requester explicitly said they are two jobs. Decision: keep two request tasks, even if contact information matches. Limit: without the explicit separate-jobs statement, the relationship would need further review. Matching contact information is not identity proof. R03 — CHANGED DETAILS Reference: E104 originally concerns a small table's loose leg. Required assumed evidence: a later message refers to E104 and changes the requested work to refinishing. Decision: preserve the original context and record the proposed change. Next step: establish which scope should guide the response; do not treat the new message as proof that the business accepted the work. Possible clarification draft, only in the appropriate established conversation: "For this table enquiry, should we assess refinishing instead of the loose-leg repair, or are you asking about both?" Status: question proposed; no answer or service availability established. R04 — RELATIONSHIP UNKNOWN References: E105 and E106 have similar descriptions. Available evidence: no reliable relationship or confirmed intent. Decision: unresolved. Similarity and a close timestamp are not enough. Next step: Sam owns the missing-evidence check or a permitted clarification; record the review point. Do not invent an identifier, merge or delete a record. BLANK REVIEW RECORD Internal case reference: Reviewer / review time: Unit being reviewed: Original references (keep private content in its authorized system): System and meaning of each reference: Who confirmed that meaning, or what remains unknown: Evidence establishing same request / separate request / changed intent: Differences that affect the requested work or response: What similarity DOES NOT establish: Existing response work: Current owner: Draft / sent / awaiting answer / unknown: What that response addresses: Evidence for that state (do not equate draft with delivery): Review decision: [ ] Same saved request supported; coordinate existing response work [ ] Separate requests supported; keep separate work tasks [ ] Proposed change; establish current intent/scope [ ] Relationship unresolved Specific evidence supporting this decision: What remains unknown: Next permitted action: Responsible owner / review point: If clarification is needed: Precise ambiguity: Can the relationship instead be established internally? Appropriate existing conversation / process confirmed by responsible owner: Neutral proposed question (do not expose another person's information): Question status: proposed / sent under existing process / answer received: Actual answer and evidence reference, if one exists: Decision after that evidence: If the decision changes, record the new basis while preserving the earlier context according to the existing record process. This worksheet does not set retention, contact-identity or access policy. REPORTING AND IMPLEMENTATION LIMITS One coordinated response task does not prove one person, lead, accepted job or sale. Do not silently rewrite reporting totals from this review. If repetition recurs, give the implementation owner concrete references and observations through the permitted support route. Do not repeatedly submit a real form, disable validation or alter live records to test a theory. CFAI BOUNDARY Current workflow and access guidance is at https://www.clickfunnels.ai/agents. This planning resource establishes no automated merge, retry handling, CRM capability, product admission or actual outcome. Use it to identify the next evidence question and its owner, not to manufacture certainty.