Index
An assistant can lose quality when products, documents and rules change. Maintenance needs to include updating the database and evaluating behavior, in addition to keeping the API available.
How to evaluate this decision
Define who approves content and how an update reaches the assistant. Record font, configuration, and template versions when possible. Preserve a test suite that represents critical tasks and add new cases based on real failures. Changes should be evaluated before expanding use, especially when the wizard performs actions.
Criteria for comparing proposals
- Content: establish publication and removal flow of outdated material.
- Assessment: Track regressions, unanswered questions, and human review effort.
- Operation: define incident response, external dependencies and procedure for returning to the previous configuration.
A scenario to discuss with the supplier
Hypothetical example: a policy changes and the database is updated, but old responses continue to come from an unrebuilt index. Maintenance should check the queried result, not just the file upload.
What to validate upon delivery
Post a tracked change and confirm that the response uses the correct source. Perform critical testing and document accepted differences before release.
Prepare the conversation about the project
Inform Quantum9 of the frequency of changes, users and consequences of errors. The contract must separate content updating, technical adjustment and functional evolution, with realistic responsibilities.
Development with agentic AI · Map the company's priority