Which actions can the assistant carry out?

The assistant acts through defined actions, with the necessary approvals. It puts together a cart in the chat, factors in coupon codes you have set up, takes appointment requests or reschedules them, requests a callback, pre-fills forms on your page, hands over structured enquiries to your inbox and, in the Custom package, also creates support tickets or entries in your system. It fills only the fields you have mapped, and only after the visitor confirms; the form is submitted only if you allow that and the visitor agrees.

Beyond that, in the Custom package, it can read and control connected systems such as calendars, inventory management or ticket systems. How this function calling with approvals works is explained on the tool control page; the cart in the chat is put together by the cart assistant.

Seventeen shapes are selectable, seven of them built in and ten connectors to outside systems, sorted by inventory management, calendar, catalog, customer management and ticket system; the ten connectors and the call to an outside system of your own come in the Custom package. Without a confirmation, only what is reading and expressly set to automatic runs; everything else is shown to the visitor as a proposal. An answer carries at most five calls, and truncation beyond that is logged rather than kept quiet.

In the window every call appears as a card with a status word and, where needed, two buttons; the states that occur are proposed, confirmed, executed, rejected, expired, failed and deadline exceeded; expired is a proposal that nobody confirmed within an hour. Every writing operation carries a one-time key that the database locks against, so a second click does not trigger a second operation. A call to an outside system checks the target, ends after eight seconds and accepts at most 64 KiB; what can be connected this way is shown on the custom functions page.