AI Agent
AI can be added to an existing application without replacing its business rules, data or access controls.
An existing application may hold valuable rules, customer data, integrations and operational knowledge. It need not be replaced to add AI; the suitable approach depends on the system’s condition and the business objective.
AI may summarise a message, suggest a ticket category, prepare a response draft, propose document values or search approved knowledge. These are possible capabilities, not GiSoft deployment claims.
| Element | Responsibility | |---|---| | Application | access, data, rules, business state and approved actions | | AI integration | task-data selection, provider call and output validation | | AI | suggestion or summary | | Employee | review where required by the process |
In a hypothetical Symfony CRM, a customer asks about modernisation and connection to a new ordering system. AI may propose category, priority and follow-up questions. The application selects data and an employee checks the proposal; it is not an automatic diagnosis.
For an invoice, AI may suggest fields, while the application checks required values, duplicates, formats, permissions and business rules. Structured output or confidence does not confirm correctness. A knowledge assistant may cite only documents the user can access; a citation alone does not prove truth.
Timeout, invalid output or duplicate delivery need visible state and process-specific behaviour. Manual fallback and duplicate prevention must be designed and verified. Start with a narrow case and selected users, then measure usefulness, corrections, failures and cost per completed case. Changing AI provider may require contract changes and renewed quality, security and cost assessment.
