What the documents look like
Work in this category follows consumer feedback that arrives after fulfilment and after-sales handling finish. Compared with promotion enrolment work, copy drafting here does not set the activity price. The materials named in the brief are negative-review handling records, experience-score detail listings, service diagnostic reports and rectification ledgers, updated daily or weekly.
Three industry facts shape how routing is arranged. Negative-review handling records typically carry the consumer's own wording, the order number, the handling stage and any supplementary evidence; these fields set the range of service promises that copy may quote. Experience-score detail listings and service diagnostic reports supply metric values and attribution direction, and they do not hand over a conclusion sentence ready to be written into copy. A rectification ledger records to-do and completion status, and an unfinished item cannot be written into copy as a service fact already delivered. Routing therefore has to carry the fields of these materials through the nodes in order, so that the drafting step works only from verified input.
Constraints at the workflow routing step
The form input node belongs to the user-interaction group. When it triggers, the conversation enters an interaction state, the workflow state is recorded, the dialogue box is hidden, and execution continues after the user completes the interaction. Required information is collected on submission and passed to later nodes. The user selection node behaves in the same interaction manner: after the user makes a choice, the node judges that choice and executes the "yes" branch. Both nodes collect and pass information. Business verification, approval, database writes and external synchronisation require a separate interface or a later process; the nodes do not perform those actions themselves.
Hypothetical paper exercise sample. Source material for checking, two sentences: "Order A-2024-0311. The consumer reported a logistics delay on 12 March; customer service apologised on 13 March and sent a replacement gift; the consumer added a review on 15 March expressing satisfaction." Draft sentence to be judged: "All orders in this shop are guaranteed to arrive within 48 hours." Pending request: "Draft one after-sales experience statement based on the material above." The check compares "all orders" and "48 hours" in the draft sentence against the single order and the actual delay recorded in the source material. The subject scope and the promise content do not match, so the draft sentence is not supported by the material.
Configuration and implementation checks
| Configuration item | Setting or check relevant to this page | Relation to the sample |
|---|---|---|
| Form input fields | Collect copy type, order number, scope of quoted material | Order number A-2024-0311 in the sample is passed as a required item |
| User selection branch | Confirm whether a given material item is adopted as the basis | After the operator selects "yes" for the 15 March added review, drafting is entered |
| Output handover | Pass form information explicitly to the later drafting or judging node | Comparison of draft sentence against source material runs in a later node |
| Interaction state check | Recorded state is behaviour of the interaction node; no global switch is documented | Execution continues after the operator submits |
| Division of external actions | Order writes, document backfill and external synchronisation attach to separate interfaces | This page does not state that the nodes complete those actions automatically |
| Hypothetical trial starting point | For this exercise the number of quoted material items starts at 1 | Chosen because the sample holds one added review; compare against a multi-item material case to observe output differences |
Three common errors
- Treating "all orders" in the draft sentence as a summary of the single order in the material. Input is the sample source material and the draft sentence; compare the subject scope; the observable result is that the two cover different objects, so the draft sentence is unsupported.
- Reading the "yes" branch of the user selection node as business approval. Input is the operator's selection action on the added review; compare the node behaviour with an approval action; the observable result is that the node only judges the choice and executes a branch, while approval needs a separate process.
- Taking the order number collected by the form input node as an already verified voucher. Input is A-2024-0311 submitted through the form; compare the collection action with voucher verification; the observable result is that the node only passes information, and voucher verification happens in a later node or a manual step.
How to verify the setup
- Using the sample source material and the draft sentence, check whether the drafting node output quotes only the order, time and handling facts that appear in the material. Input is those two sentences; compare subject and promise scope between draft and source; if the output still contains "all orders", the check does not pass.
- Using the selection action in the sample, check whether the "yes" branch connects to the drafting node. Input is the operator selecting "yes"; compare the branch connection target; if it connects to an approval or write node, adjustment is needed.
- Using an explicit paper input of an empty list, check the downstream design for empty results and whether the drafting node gives a prompt to supply missing material. Input is the empty list; compare the downstream node output; if copy is generated directly, the check does not pass. Whether a real query returns an empty result has to be observed against an actual query, and this page does not claim that a fictional rule search always returns an empty list.