Complaints and official replies: product questions with workflow routing

Review workflow routing for product questions in Complaints and official replies. Check input mappings, source evidence and failure handling before use.

What the documents look like

For product questions in Complaints and official replies, this page examines FastGPT workflow routing. Complaint product statements and inspection findings need separate evidence and retained speaker and batch identity. The examples are hypothetical.

Constraints at the workflow routing step

A hypothetical complaint says packaging colour differs from the page image, with batch identity unrecorded. The product page labels its image illustrative. Receive product and speaker identity and pass the batch gap onward without promoting a reported statement into inspection. A route may request batch evidence or organize an already documented comparison. Both retain the illustration’s purpose. Branch selection orders checks without deciding physical conformity or the complaint’s validity.

Configuration and implementation checks

Complaint checkTask materialInspection
SpeakerBuyer statementNot an inspection finding
Image purposeIllustrativeRetain qualifier
BatchUnrecordedBorrow no history
Review routeOrganize or obtain evidenceNot closure
Formal handlingSeparate processActual receipt

Documented conditions

Documented item / implementation checkCondition
Form input nodeSubmitted form values pass to subsequent steps.
User-selection nodeExecution follows the connected selected branch.
Interaction-state checkInspect waiting and post-submission states.
Output handoff checkCompare values passed between steps.
External-operation responsibilityExternal business operations require an implementation.

Three common errors

A buyer statement promoted to an inspection finding needs actual inspection evidence. A historical batch imported here needs current identity checked. Entering a review route promoted to a closed complaint needs a real handling record. These concern evidence type, batch and matter stage.

How to verify the setup

Inspect what was submitted, received and stated about each subject. Verify batch identity before comparing added material. Keep gaps explicit. Complaint submission, replies and closure require separate business procedures and receipts; node execution produces no regulatory finding. Retain separate references for the consumer account, illustrative page image and batch inspection. Each proposed reply statement should trace to its own evidence, while the unresolved batch identity remains visibly outstanding for review.

Material contextScope
Document typesComplaint Work Order, Regulatory Inquiry Letter, Order Evidence and Rectification Report
Candidate sources12315 Platform, Platform Complaint Center, Customer Service Chat and Order System
Technical baselineFastGPT v4.17.2