What the data for this category looks like
Data sources for this category include the 12345 citizen hotline platform, contractor business systems, official knowledge bases, public feedback evaluation data, and local hotline management regulations. Daily generated documents include request registration forms, dispatch records, handling replies, follow-up records, delay applications, return explanations, and standardized knowledge base entries. Covered fields include request number, contracting unit, request content, reply guidelines, evaluation results, and more. Data is updated daily, and covers full business information across the entire process from request receipt to closed-loop processing.
What constraints these characteristics impose on the knowledge base retrieval and recall link
This category covers the full process from request receipt to closed-loop processing, and must meet the accuracy requirements of ticket scenarios. Knowledge base retrieval must first associate exclusive reply guidelines for the corresponding contracting unit. This avoids generalized matching that leads to inconsistent replies. Daily updated data sources require the retrieval link to support real-time synchronized updates of knowledge base entries. This prevents use of expired business content. Mixed multi-source data requires the retrieval link to distinguish business handling documents from management specification content. This ensures recalled content highly matches the responsible unit and request type of the current ticket. Ticket handling has strict timeliness requirements. The retrieval link must control response duration to avoid reducing ticket circulation efficiency.
How to set the configuration
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Matches the accurate reply requirement for hotline requests, avoids recalling irrelevant content |
limit | Top 5 entries | Controls context length, fits the concise reply requirement for tickets |
searchMode | Precise matching | Prioritizes matching core keywords in requests, meets the type judgment requirement for hotline tickets |
usingReRank | Enabled | Sorts recalled results by relevance, improves display priority of high-quality replies |
datasetSearchUsingExtensionQuery | Enabled | Optimizes public requests semantically, adapts to the indexing logic of knowledge base entries |
collectionIds | Specify exclusive collection IDs for contracting units | Narrows retrieval scope, improves matching accuracy |
Three common mistakes
- A 404 error occurs after running the initialization script, and the knowledge base configuration fails to load. The cause is failure to correctly specify the exclusive dataset for contracting units corresponding to
collectionIds. The system cannot locate target business knowledge base content. - Retrieval results are empty, and no reply guidelines for the corresponding ticket can be recalled. The cause is failure to enable the
datasetSearchUsingExtensionQueryfunction. The system cannot convert public requests into semantic queries adapted to knowledge base indexing, so it cannot match relevant entries. - Recalled results have poor matching with requests. Either too many irrelevant contents are returned, or no valid results are available. The cause is failure to adjust the
similarityvalue range for hotline ticket scenarios. Fixed thresholds for general scenarios are used instead.
How to confirm the configuration is complete
- View the dataset management interface. Confirm that the interface only contains 12345 citizen hotline business documents and knowledge base entries for the specified contracting unit.
- Enter a typical public request. Verify that retrieval results include the corresponding handling reply guidelines, and that the sorting matches expectations.
- Check the enabled status of configuration items. Confirm that
usingReRankanddatasetSearchUsingExtensionQueryare both enabled. - Simulate a ticket circulation scenario, trigger the retrieval link. Confirm that the response duration meets business timeliness requirements.
The values provided here are common starting points. They should be evaluated against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.