By Artem Korsakov ·
In short: automation support includes checking data exchange, investigating errors and updating agreed settings. Additional work may be needed when systems, documents or the process itself change. Before launch, you need to define who is responsible, how to raise issues and what the recurring costs are.
After the product is handed over, the company keeps changing services, CRM fields and approval rules. Employees leave, new documents appear, an external service updates its connection terms. These changes need to be taken into account in how the automation works.
Separate fixes from development
If the solution does not perform an agreed action, the error needs to be investigated. If the client wants to add a new stage, data source or role, that is a change in scope. It is useful to agree on how both cases are handled before handover.
A discussion needs an example: the request number, the time and a description of the expected result. A report saying “sometimes it doesn't work” is hard to verify. At the same time, employees should not send passwords or the entire client database for an initial report.
The procedure for fixing one's own errors, response times and support limits are defined by the project agreements. Publishing the product does not by itself mean that ongoing support is included.
Training example: five requests after launch, each either an error, development work or a task for the owner. The type of request determines who handles it and whether the work falls within the agreed support.
What integration support includes
The owner should be able to notice an unprocessed request and understand who is handling it. Useful tools are an error queue, the date of the last successful exchange and instructions for reprocessing.
An external system may stop accepting data because of a change in a required field or in access. An automatic retry does not always solve such a problem. You need to distinguish temporary unavailability from conditions that an employee or contractor has to fix.
The main handover situations are covered in the article about leads in the CRM. The specific scope of monitoring depends on the chosen connection and should not be assumed without agreement.
What to maintain in an AI assistant
A knowledge assistant's sources, users' questions and model settings change. That is why it is useful to keep a set of test tasks and repeat the check after noticeable changes.
Appoint someone responsible for the materials. They approve current instructions and report when old documents are removed. Technical support does not replace the owner of the business rules.
If the number of answers without a suitable source grows, you need to find out what is missing: information in the documents, search settings or a different way of doing the task. Expanding access to data at random is not a good idea.
Training example: checking the assistant after a policy update. The control questions are run before the new version is switched on. The error was found before employees saw it.
How to calculate costs after implementation
Write down all applicable items:
- hosting and storage;
- subscriptions to working platforms;
- use of AI models;
- paid notification channels;
- support within the agreed scope;
- separately ordered enhancements.
Supplier terms are checked before choosing and reviewed when the load changes. A universal fixed amount for all portals and assistants would be unreliable.
For control, it is useful to define who sees the costs and at what level of growth approval is needed. A usage limit must come with clear system behaviour: for example, handing the task to an employee instead of silently stopping processing.
Who acts when processing stops
Prepare a short guide for a regular employee: where to check the status of a request, whom to report the number to, how to continue manually and what must not be resent. The person responsible for support needs different instructions: how to verify recovery, reconcile the queue and avoid creating duplicate records.
For an AI scenario, it is useful to be able to temporarily switch off the suggestion while keeping the normal process. If the model stops responding, the manager must receive the original email or document and continue manually. A result prepared before the failure remains a draft until confirmed.
The NIST AI RMF Playbook considers governance and assessment of AI risks throughout its use. A practical recommendation for a small project: define in advance the owner, the observable errors and the procedure for returning to manual work.
How to tell useful support from a formal check
A check that “the page opens” does not prove that requests have reached the CRM. Choose a control scenario: create a request, get a record in the right system, check the status. For a knowledge assistant, add a question with a known source and a question with no answer.
After changing the model, template or required fields, repeat the related checks. If only the phone number in a signature has changed, you do not need to retest the whole product; if permissions have changed, the check must cover all affected roles.
At handover, separately demonstrate recovery from a backup where one is provided. Having a backup file and successfully restoring from it are not the same thing. Clarify what period of data may be lost and how long manual work is acceptable. These parameters affect the cost of support. They are chosen according to the importance of the process; the size of the interface plays no role here.
What materials to receive at handover
You need access within the agreed scope, instructions for routine actions, a list of connections and contacts of the people responsible. It is important to know whose account the services are on and who pays for renewal.
Agree on recovery after a failure and backups where important information is stored. For a small first version, the scope may be limited, but the owner must know it.
At trike_dev, the terms of handover, support and further work are defined for each specific project. For discussion, you can use integration or the materials assistant. The general components of a digital product budget are covered in the article about cost and timelines.
Related reading: Data exchange between systems: how not to lose requests on failures; Automation effectiveness: how to check the result of implementation.
Частые вопросы ### Can another contractor provide support?
That depends on the materials handed over, the access and the platforms chosen. The terms of handover are worth discussing before the project starts.
Is a monthly contract needed for any small integration?
Not necessarily. Different formats are possible, but the owner must still have a clear way to notice an error and ask for help.