What this type of data looks like
Follow-up record summary data originates from the post-completion follow-up stage of hotline tickets. It includes text records from manual follow-ups and transcriptions from automated voice follow-ups. Update timing triggers with ticket completion workflows, and can be configured for real-time generation or hourly batch synchronization to the knowledge base. The document structure of a single record includes fields such as ticket number, follow-up target, follow-up time, response content, and satisfaction rating. The ticket number is the unique association identifier. Follow-up time uses the YYYY-MM-DD HH:MM:SS format. Response content is recorded in characters, with most entries falling within the several hundred character range.
What constraints do these characteristics impose on source citation and traceability
Each follow-up record is tied to a unique ticket number. When citing for traceability, this number must be included as the association key, otherwise the correspondence between the original ticket and follow-up record cannot be matched. The real-time update feature of follow-up records requires the knowledge base to use an incremental synchronization mechanism to avoid content lag. Fields contain sensitive user feedback and personal information. Non-public fields must be filtered during traceability to comply with data compliance requirements for public service scenarios. Single follow-up record lengths vary. When citing, token usage must be reasonably limited to avoid exceeding model context limits, while ensuring core traceability information is not truncated.
Configuration settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the average character count of a single follow-up record summary, avoids truncating critical traceability information |
responseData | Return ticket number, follow-up time, response content | Extracts core traceability fields from follow-up records, ensures original tickets can be linked during citation |
detail | Enabled | Displays full original follow-up record, supports accurate verification of cited content |
| Incremental sync interval | 5 minutes | Adapts to the real-time update rhythm of follow-up records, ensures knowledge base content stays synchronized with original records |
| Association key configuration | Ticket number | Serves as the unique identifier binding follow-up records to knowledge base entries, enables precise traceability |
| Permission filtering configuration | Marked in accordance with government service scenario compliance requirements | Filters sensitive fields, meets data security requirements for public service scenarios |
Three common mistakes
- Phenomenon: Searching the knowledge base matches a follow-up record summary entry, but the returned result only shows a citation identifier with no specific content. Cause: The
responseDataconfiguration was not used to specify the association fields to return, only basic index metadata was retained. - Phenomenon: After calling the knowledge base plugin in a workflow, the code run step reports an error indicating missing traceability association parameters. Cause: The ticket number was not configured as the core association key, so the binding relationship between original follow-up records and tickets cannot be matched.
- Phenomenon: Updated follow-up records do not appear in the knowledge base beyond the preset time period. Cause: The incremental sync interval was set too long, failing to adapt to the real-time update rhythm of follow-up records.
How to confirm the configuration is correct
- Manually upload a test follow-up record, configure the corresponding knowledge base, run a search, and check if the returned result includes association fields such as ticket number and follow-up time.
- Trigger a new ticket follow-up, wait for synchronization, run a search to confirm the newly generated follow-up record summary appears in the knowledge base results.
- View the knowledge base configuration's sync logs, confirm that incremental sync tasks execute normally at the set interval with no failed records.
- Call the workflow test traceability function, check if the returned result includes the full original follow-up record and associated ticket information.
The values provided are common starting points and should be measured 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.