Why an agent needs a specification
A specification fixes what the agent does, with which data and how you will accept the work. Without it, the contractor builds what it knows how to build, and the dispute about the result starts after payment.
For automated systems, Russia has GOST 34.602–2020, a national standard in force since 1 January 2022 in place of GOST 34.602–89. It requires ten sections, from general information to development sources, and it allows adding, merging and moving subsections into annexes.
For one agent, the full standard is too much. The template below keeps what matters for an agent: sample requests, knowledge, rights and a test set. If the customer requires the standard, the template points fit into its sections on system requirements and on control and acceptance.
Template: task, metric, limits
1. Process and owner. Which process the agent takes on, and who in the company is responsible for it and accepts the work. Example: answers to delivery questions in the website chat, with the head of customer service as the process owner.
2. Metric. What it was, what it should become and how to measure it: for example, the share of requests handled with no human and the response time. The “before” figures come from your reports for the last month.
3. Limits. What the agent does by itself, what it passes to a person and what it never does: discounts, refunds, promises about dates, medical and legal advice.
4. Why an agent and not a script. Anthropic advises starting with the simplest solution: if the steps are known in advance, an automation script is enough, and the specification gets shorter.
Template: scenarios, data and integrations
1. Scenarios. A list of typical requests with real customer phrases and the correct agent action for each. A dozen real examples are more useful than a page of general words.
2. Knowledge. Which documents the agent reads: the price list, internal rules, contracts, the answer base. Who updates them and how often. If there are many documents, the agent needs RAG: before it answers, it searches the document base for passages and answers from them, with no model training.
3. Integrations. Which systems the agent reads and writes: CRM, accounting, calendar, email. For each system: which actions are allowed (read, create, change) and under whose account.
4. Channels. Where the agent talks to people: the website, Telegram, other messengers, the phone. Working hours, and what it answers when no staff member is available.
Template: rules, limits and security
1. Tone and answer rules. Formal or informal address, answer length, what to do when a customer is rude, which words to avoid. From these points, the contractor writes the agent’s standing instruction, the system prompt.
2. Personal data. Which customer data the agent sees, where it is stored and who has access. Under 152-FZ, Russia’s personal data law, data of Russian citizens is collected and stored in databases inside Russia, and the operator notifies Roskomnadzor, the Russian data regulator, before any transfer abroad. The data security page explains how we store customer data.
3. Rights and log. The agent gets the minimum rights, every action it takes is written to a log, and a person confirms dangerous actions (payment, deletion, sending documents).
4. Model. An open model on your server or a cloud model, and in which country it runs. If this does not matter to you, say so directly, and the contractor will choose by price.
Template: testing, acceptance and support
1. Test set. Real questions with reference answers, collected by the process owner. The agent passes the set before launch and after every change.
2. Acceptance procedure. A pilot on part of the requests, its term, who signs the acceptance certificate and at what metric value.
3. Documentation. The agent’s instructions, a description of the integrations, a list of accounts and the procedure to roll back to the previous version.
4. Support. Who watches the agent after launch, how often the metric report arrives and who updates the knowledge when the price list changes. Our support costs from $480 a month.
Who fills in the template and how
The process owner writes the task, the metric, the limits and the scenarios: these are their figures and their rules. The contractor adds the points on the model, integrations and the log and agrees them with you.
The order is simple. The process owner collects sample requests and documents, the manager approves the metric and the limits, and the contractor returns the document with the technical points. Disputed points are settled before signing, and the specification becomes an annex to the contract.
In a pilot, we write the specification with you in the first days: the pilot costs from $1,499, the term is 14 days, and the metric from the specification goes into the contract.