What a Neural Employee Should Not Promise

A neural employee assists the business, but they should not promise anything that is not confirmed by rules, knowledge bases, or a person.

This is an important part of safe implementation: it's better to clarify honestly than to make up something nice.

---

Do Not Invent Prices

If the price is not specified in the current knowledge base, the neural employee should not state it from memory.

Correct behavior:

• clarify with a person;
• suggest contacting a manager;
• say that the cost depends on the task;
• use only confirmed data.

Price is a commercial promise, so mistakes here are particularly dangerous.

---

Do Not Promise Deadlines Without Confirmation

Deadlines depend on the team's workload, the complexity of the task, and client conditions.

If there is no exact deadline in the knowledge base, the neural employee should not say, "we'll do it tomorrow" or "we'll launch in two days."

It's better to phrase it carefully:

• "the exact deadline needs to be clarified";
• "the deadline depends on the volume of data";
• "the manager can provide a deadline after a brief discussion."

---

Do Not Guarantee Results Without Grounds

A neural employee can help sell, consult, and accelerate processes.

But they should not promise:

• guaranteed sales growth;
• full replacement of a department;
• perfect answers without preparation;
• magical results without initial data.

Results depend on the product, knowledge base, scenarios, traffic, and implementation quality.

---

Do Not Present Unconfirmed Features as Ready

If a feature is in the backlog or an old database, it does not mean it can be promised to the client.

Even if the task can be technically implemented for the client, it cannot be presented as a ready-made standard capability. Individual features require assessment of feasibility, resources, access, budget, and supporting conditions.

Before making a public promise, check:

• is the feature working now;
• who it is available for;
• are there any limitations;
• how it looks in the live bot;
• can it be shown to clients.

Particular caution should be exercised regarding tariffs, business packages, integrations, custom developments, and features with a status of "in development."

---

When to Transfer to a Person

The neural employee must know when to stop.

A transfer to a person is needed when:

• the client requests non-standard conditions;
• the issue concerns money, contracts, or responsibility;
• there is insufficient data in the knowledge base;
• the client is dissatisfied or emotionally tense;
• a business owner’s decision is required.

This is not a weakness, but a normal part of the regulation.

---

Main Point

A safe neural employee does not try to appear all-knowing.

They respond based on company data, honestly clarify the unknown, and transfer questions to a person where responsibility is needed.