What the documents look like
Refund-only dispute handling centers on four record types: the refund-only application, the shipment proof, the delivery signature proof, and the appeal material. The evidentiary weight sits on dispatch, signature, and product value, because this category commonly has no returned-goods warehouse receipt. These records appear per order, and drafting copy requires reading each order's own wording rather than applying one template to every case. Copy drafting here means restating facts already recorded in the material as submittable explanatory text; anything the material does not record stays pending verification.
Constraints at the model connections step
Model access depends on AI Proxy. Per the v4.17.2 configuration document, both the App service and any Admin service reusing App/Service configuration must set AIPROXY_API_ENDPOINT and a non-empty AIPROXY_API_TOKEN; missing either item causes startup validation to fail. Legacy OpenAI environment variables or a single-model custom request address cannot replace these two settings. AIPROXY_API_ENDPOINT holds the service root address without an appended /v1. AIPROXY_API_TOKEN is an administrator token and cannot be substituted with an application API key.
The model configuration document states that the system requires at least one language model and one index model to function normally. Model probe configuration accepts an integer interval between 5 and 60 minutes. Retrieval is not authorization: a relevance score is not a category, entity, or permission filter, and a similarity setting does not exclude unrelated businesses or unauthorized records.
Hypothetical paper exercise: a shop after-sales supervisor handles one refund-only application on 12 March 2026. The material wording reads: "The order was collected by the carrier on 5 March 2026, and showed signed by the recipient in person on 8 March 2026; the recipient-name field is blank." The proposed draft sentence reads: "The buyer confirmed receipt on 8 March and product value is undisputed." The comparison object is the blank recipient-name field; the phrase "confirmed receipt" has no corresponding record in that material.
Configuration and implementation checks
| Configuration item | Hypothetical starting value for this exercise | Reason and comparison object |
|---|---|---|
AIPROXY_API_ENDPOINT | AI Proxy service root address | Document requires the root address; compare against a form with /v1 appended |
AIPROXY_API_TOKEN | Non-empty administrator token | Document requires consistency with the server side; compare against an application API key |
| Language model enabled state | At least one language model enabled | Document requires at least one language model for normal operation |
| Index model enabled state | At least one index model enabled | Document requires at least one index model for normal operation |
| Model probe interval | 30 minutes, as a hypothetical starting value | Document supports integers from 5 to 60; compare against both boundaries |
| Channel and model test | One test run on the configured channel | Document provides channel test and model test entries |
Three common errors
- Writing a carrier signature trail as buyer confirmation of receipt. In the sample, the recipient-name field is blank, and the draft sentence adds a confirmation act the material does not record.
- Treating a similarity setting as a permission decision. A relevance score does not constitute an entity or permission filter, and retrieval results do not replace an authorization check.
- Writing a pending review state as an approved outcome. A refund-only application under review does not constitute confirmation of the refund amount or of responsibility.
How to verify the setup
- Input the sample material wording and the proposed draft sentence; compare whether "the recipient-name field is blank" and "confirmed receipt" refer to the same field over the same period. When the draft sentence states a confirmation act the material does not record, the sentence is unsupported.
- Input two forms of
AIPROXY_API_ENDPOINT; compare whether a/v1suffix is appended. A form with the suffix conflicts with the documented requirement. - Input a hypothetical material that contains no signature information; compare whether the draft sentence still produces a signature conclusion. When the material lacks a signature field, the conclusion remains pending verification.