What the documents look like
For document comparison in Livestream after-sales service, this page examines FastGPT workflow routing. Livestream after-sales comparison separates order scope, refund applications and reshipment status. A script template cannot establish this order’s outcome. The examples are hypothetical.
Constraints at the workflow routing step
A proposed livestream order list contains unresolved orders. A refund excerpt concerns one order, while reshipment material records only a created arrangement. Collect the order relationships and passages. A person can request a refund outcome or shipment handoff. Template wording that says to notify after completion remains conditional, not a current completion notice. One order’s result does not cover the whole livestream, and platform and warehouse records are not assumed synchronized.
Configuration and implementation checks
| Livestream service comparison | Proposed source | Distinction |
|---|---|---|
| Order population | Multi-order list; one-order result | Not the whole event |
| Reshipment arrangement | Creation only | Not logistics handoff |
| Conditional script | Notify after completion | Not current completion |
| Branch input | Refund or shipment evidence gap | Corresponding order retained |
| Formal handling | Notices, refunds and writes separately checked | Interaction is not closure |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Form input node | Submitted form values pass to subsequent steps. |
User-selection node | Execution follows the connected selected branch. |
Interaction-state check | Inspect waiting and post-submission states. |
Output handoff check | Compare values passed between steps. |
External-operation responsibility | External business operations require an implementation. |
Three common errors
One order expanded to the event needs list coverage and result ownership. Arrangement promoted to dispatch requires the corresponding physical handoff record. Template promoted to current status needs comparison of its condition with this order’s evidence. These inspect the order population, fulfillment stage and wording status separately.
How to verify the setup
Let refund and reshipment choices receive their own outstanding evidence requests. Compare the order subject through each handoff. Added logistics evidence supports only that order’s shipment stage while its refund still needs a corresponding result. Actual refunds, warehouse dispatch, platform status writes and customer notices require separate authority and receipts downstream. Completed interaction continues execution without establishing that every after-sales case is closed.
| Material context | Scope |
|---|---|
| Document types | Livestream Order List, Refund Application, Reshipment Order and Script Template |
| Candidate sources | Douyin Shop After-Sales, Customer Service IM, Warehouse WMS and Logistics Tracking |
| Technical baseline | FastGPT v4.17.2 |