Individual Functions for Your Own Processes

Individual functions are your own actions and processes that go beyond the seventeen shapes shipped with the product. The basis is the tool control: a tool is given a schema, a kind — reading, writing or irreversible — and an approval mode. Reading tools may be set to automatic, anything that writes asks first. The way out to your system runs through exactly one connection with target check, time limit and size limit, without redirects and without access to internal addresses. The tool only ever sees its own schema fields; tenant and account identifiers are blocked as field names. This lets us cover cases no construction kit anticipates — a calculation, a configurator or a multi-step process. Overview under custom functions.

Yes, with the calculation happening where the numbers come from: in your system. The assistant guides the steps, collects the details and calls your calculation route. You describe the tool for it yourself — a schema with up to twenty fields, a title up to 120 and a description up to 600 characters; the input is trimmed to that schema before the call, values are capped, and if a required field is missing nothing is executed at all. The call goes to exactly one stored connection, waits at most eight seconds and accepts at most 64 KiB; what comes back are only the result fields you declared. Prices therefore come out of your logic, not out of the language model. More under custom functions.

In the Custom package, through tools you create per assistant: inventory, CRM, calendar, ticketing or an interface of your own. Every tool carries a kind, namely read, write or irreversible, and an approval mode; the preset is to ask back before executing. Kind and schema come from the register and not from the request. Outward, every call takes the same path: the target address is checked before the fetch, and the resolved addresses are checked rather than the name alone, redirects are not followed, a response above 64 KiB is aborted, and a deadline of eight seconds applies. Whatever comes back is filtered down to the declared result fields. More under tool control.

Yes. Every tool carries an approval mode, and the default is confirmation. Without confirmation only something that reads and is explicitly set to automatic will run; every non-reading kind is forced to confirmation when created or changed, no matter what the request says. A call that requires confirmation first ends in the state proposed and executes nothing: the visitor reads the input in plain text, and only their click triggers execution. Every call leaves a log row that is written before execution and updated afterwards, and knows seven states from proposed to deadline exceeded. The model is offered only what you have entered, switched to active and allowed for the role of the conversation.

Yes, in the Custom package. We chain individual actions into a continuous process — for example read out, calculate, create a document, create a ticket and hand over the lead. This creates a path without media breaks in which each step has its own permission: anything that does more than read is first shown to the visitor as a proposal and confirmed by them. The chain is bounded so it cannot run away: per answer the assistant performs at most five tool calls, and only one when the monthly allowance is tight. Every single call is then recorded in the log, with input, result, duration and the path by which it was approved.

Individual functions belong to the Custom package with a setup from 4,900 € net; operation follows the scope and includes hosting in Germany, care, updates and data protection. There is no list price for operation there, because the number and type of connected systems determine the effort. The package holds 50 seats, 25 assistants, 250 knowledge sources and 20,000 documents and allows tool and API control with custom actions and workflows. We name the binding scope after a free initial consultation. All packages are listed under pricing, typical cases under references. All services can be cancelled monthly; there is no minimum term.