What the documents look like
Brand member private-domain operations work from customer data and repeat-purchase outreach. The main data sources are the CRM system, enterprise WeChat, POS consumption records, and mini-program behavior data. The documents handled day to day are member tag tables, outreach plans, coupon rules, and privacy authorization records. In the copy drafting task, the member benefits, coupon terms, and authorization status that a draft cites all depend on these documents.
At the interactive forms step, a copy drafter commonly uses the Form Input node to collect member tags, copy purpose, and target audience, and uses the User Selection node to confirm copy direction or authorization scope. The Form Input node collects the information that is filled in and passes it to later nodes after submission; it does not carry its own business database function. The User Selection node executes a branch according to the user's choice; it does not act as a personnel directory or a business data selector. The interaction state records the workflow state and waits for the interaction; after the interaction completes, the workflow continues downward.
Constraints at the interactive forms step
The member tag table and privacy authorization records determine the scope that a draft may cite. Values collected through a form require an external system or later nodes to complete field validation, business approval, and write-back. The validity period, applicable audience, and coupon content in the outreach plan and coupon rules must match the source text when a draft is written; the form itself does not verify these business facts.
Hypothetical exercise sample: a brand CRM team prepares a member day copy in June 2025. The source texts for checking are as follows.
Material one (member tag table): "Tag 'high-repeat coffee member', definition: purchased the coffee category at least 3 times in the last 90 days, update date 2025-06-01."
Material two (coupon rules): "Coupon name 'member day coffee coupon', face value 8 yuan, applicable category coffee, validity 2025-06-10 to 2025-06-12, limit 1 per person."
Material three (privacy authorization record): "Member A, authorization scope: receive marketing SMS, authorization date 2025-05-20, status valid."
Draft sentence to be judged: "All high-repeat coffee members can claim an 8 yuan coffee coupon from June 10 to June 12, limit 1 per person."
Configuration and implementation checks
The table below centers on the sample above and lists officially documented settings or implementation checks relevant to this feature and the copy drafting task.
| Configuration item | Type | Description |
|---|---|---|
| Form Input node | Node behavior | Enters the interaction state when triggered, collects filled information, and passes it to later nodes |
| User Selection node | Node behavior | Enters the interaction state when triggered and executes a branch according to the choice |
| Required-field check | Implementation check | List the fields that this task cannot omit, and test the behavior with a missing field and with the field completed |
| Field validation | Downstream implementation | Values collected by the form are validated by an external system or later nodes; the node itself does not perform validation |
| Business approval and write-back | Downstream implementation | Approval, write-back, and batch operations are implemented in an external system or later nodes as needed |
Hypothetical starting point for this exercise: set "member tag", "coupon validity period", and "authorization status" as required fields, because these three items directly determine whether the draft sentence can hold; compare them item by item against the source texts and observe whether the form blocks submission when a field is missing and whether the values pass to later nodes once completed. This starting point is a setting for this exercise, not an official default value.
Three common errors
- Treating a tag value collected by the form as an already verified business fact. The Form Input node only collects and passes filled information. Whether the tag definition is met and whether the authorization is valid must be compared against the source text of the member tag table and the privacy authorization record. Error symptom: the draft sentence directly adopts the "high-repeat" value entered in the form without checking the definition and update date in material one.
- Treating the branch result of the User Selection node as approval or authorization. The User Selection node executes a branch according to the choice and does not produce approval effect. Error symptom: treating the branch result of "choose to receive marketing SMS" as equivalent to a valid authorization in the privacy authorization record.
- Writing a coupon scope or validity period into the copy that the material does not state. The coupon rules source text states only the applicable category coffee and the validity 2025-06-10 to 2025-06-12. If the draft sentence adds "usable across all categories" or extends the dates, it exceeds the scope supported by the material.
How to verify the setup
- Input the source text of material one and "high-repeat coffee member" in the draft sentence, and compare the tag definition "purchased the coffee category at least 3 times in the last 90 days" with the subject expression in the draft sentence. Condition met: the subject of the draft sentence matches the tag definition, or the update date of the tag, 2025-06-01, is clearly noted. If the form only holds "high-repeat" with no definition check, record it as unsupported.
- Input the source text of material two and "June 10 to June 12", "8 yuan", and "limit 1 per person" in the draft sentence, and compare field by field. Condition met: all three fields match the coupon rules source text exactly. If the draft sentence contains an applicable category or face value not stated in the source text, record it as beyond the material scope.
- Input the source text of material three and the authorization premise of "all high-repeat coffee members" in the draft sentence, and compare the authorization scope "receive marketing SMS" with the status "valid". Condition met: the outreach method in the draft sentence falls within the authorization scope and the authorization status is valid. Material three concerns only member A. If the draft sentence claims to cover all members, record it as an evidence gap pending the authorization records of other members.
Empty-result handling: if retrieval returns [], check on paper with the input [] whether the downstream design passes the empty result to later nodes. Do not claim that a fictional rule retrieval necessarily returns []. Libraries across different vector models cannot be associated together. Check the identifiers first and exclude those that do not match, then record the actual observation.