What the documents look like
For after-sales questions in General export declarations, this page examines FastGPT multi-turn prompts. Ask separately about declaration handling, delivery and the service request, tracing the documents carried into each answer. The examples are hypothetical.
Constraints at the multi-turn prompts step
A proposed conversation starts with an export-processing note saying that a declaration was returned for supplementary information. The follow-up asks what to do about the customer’s service request. That return concerns declaration material; it establishes neither delivery nor the customer’s requested remedy. Specify the missing request, order correspondence and delivery sources. If the answer immediately prescribes a return or replacement, inspect whether history contains such a request. Extending declaration handling into a service conclusion leaves its basis unverifiable.
Configuration and implementation checks
| Conversation check | Declaration and service material | Acceptance action |
|---|---|---|
| Initial scope | Declaration returned for more information | No inferred return or replacement request |
| Added request | Email asks to correct a packing description | Check shipment and requested action |
| Reference inspection | Identify the email or declaration meant by this case | Compare original and optimized questions |
| Gap location | Unobtained email versus omitted input | Collect the source or inspect delivery |
| Action boundary | Answer organizes proposed next steps | Verify business-status updates separately |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Prompt and task | Define sources, the task and evidence-gap handling. |
Conversation history | Inspect the history actually submitted. |
Question optimization | Review reference resolution and question expansion. |
Model and length | Inspect context and reply length separately. |
Reply format | json_schema needs its format and parsing validation. |
Three common errors
- If a returned declaration becomes a customer return or replacement request, inspect customer, order and delivery originals. Retain the filing note and added handling statement; a document return establishes no product remedy.
- If packing-description correction becomes a refund or this case changes shipment, compare questions and shipment identity. Inspect actual history; more context does not automatically correct the task.
- If an obtained customer email is absent from input, compare source selection and actual request to inspect transfer. An unobtained email needs collection instead; neither case is simply insufficient memory.
How to verify the setup
Acceptance can compare an empty history, the declaration note alone and the note with the customer email. Check whether each answer identifies the corresponding evidence gap. An obtained email omitted from input requires investigation of delivery; an unobtained email requires source collection. Do not label both as insufficient model memory. The response may organize known material and proposed next steps, but drafting an action does not update a declaration or service status in the business system.
| Material context | Scope |
|---|---|
| Document types | Export Declaration Form, Commercial Invoice, Packing List and Contract |
| Candidate sources | China International Trade Single Window, Customs Code Database, Freight Forwarder Bill of Lading and Enterprise ERP |
| Technical baseline | FastGPT v4.17.2 |