Tool Control: The Assistant Acts Inside Your Systems
A XICBOT assistant does not stop at information: through defined actions (function calling) it reads and controls your connected tools — calendar, CRM, inventory, ticketing and shop. Reading, it fetches current facts; writing, it completes real operations, each write action with a clear permission. GDPR-compliant, hosted in Germany.
Read + Write
actions in your systems
Permissions
write actions safeguarded
in seconds
instead of the next working day
24/7
even at night and on weekends
An assistant that only gives information helps with half of all matters — for the other half, customers want something to actually happen: an appointment booked, an order checked, a lead created. This is exactly where tool control comes in. Through defined actions, known technically as function calling, a XICBOT assistant reads and controls your connected systems: calendar, CRM, inventory, ticketing, shop and internal tools. It does not act at random but only performs the actions you have defined and approved. Reading actions provide it with current facts, writing actions complete real operations. Which actions can be freely combined is shown on the custom functions page; how the assistant technically reaches your website is covered under integration and embedding.
An assistant that reads and controls your systems
What the Assistant Reads and Controls
Tool control means the assistant does not stop at words but works inside your systems. Two directions are possible. When reading (read), it queries current information — the free appointment, the stock level, the order status — and answers with facts from your system instead of a generic standard reply. When writing (write), it triggers a real operation: books the appointment, creates the lead, opens the ticket. Both directions run through clearly defined actions, and every write action is bound to a permission. This turns the chat window into a continuous path from first interest to completed operation, without customers having to leave the page or wait until the next working day.
Reads Your Systems
Reading actions fetch current facts: calendar availability, order and delivery status, stock levels from inventory, prices and terms as well as records from the CRM. The assistant answers with real data instead of outdated standard phrases.
Performs Real Actions
Writing actions complete operations: book an appointment, create a lead, open a ticket, change an order, note a callback. The assistant acts inside your systems instead of merely pointing customers to a form.
Books Appointments in the Calendar
It shows free slots from the calendar, books and reschedules appointments and sends confirmations and reminders — around the clock. More on the booking assistant page.
Creates Leads in the CRM
It qualifies enquiries with follow-up questions, captures contact details and creates the lead in a structured way in the CRM or inbox — without duplicate entry. Details under lead assistant.
Acts Only With Permissions
The assistant performs defined actions exclusively. For each write action you decide whether it runs automatically or requires a confirmation. Actions performed are logged.
Connects Inventory and Tools
Whether inventory, ticketing or an internal tool: through defined actions the assistant reads and operates your systems. Which actions can be freely combined is shown by the custom functions.
Try XICBOT live
This is not a video or a recording — you are chatting with a real assistant trained on XICBOT. Ask a question or click an example to start.
This demo processes your input to reply — also via a provider outside the EU (standard contractual clauses). Please do not enter sensitive data. Click “Understood” to start the chat. Privacy
Read and Write: Query and Act
The difference between reading and writing matters because it determines the safeguarding required. Reading actions fetch information but change nothing — they can usually run without an additional confirmation. Writing actions actively intervene in your systems and therefore get clear rules: some may run automatically, others only after a confirmation by the customer in chat or by your team. Which action is safeguarded how is defined by you, not by the assistant.
Read — The Assistant Queries Your Systems
Reading actions give the assistant current facts from your systems. This way it answers questions about availability, appointment slots or order status with real data instead of a generic reply that quickly goes out of date. What it may read we define together — and expand over time. How the assistant additionally knows your content and documents is covered under knowledge base and training.
- Calendar availability and free slots
- Query order and delivery status
- Stock levels and availability from inventory
- Prices, tariffs and terms from price lists
- Customer data and records from the CRM
Write — The Assistant Acts, With Permission
Writing actions complete real operations in your systems. So that only what should happen happens, every action gets a clear rule: automatic or only after confirmation. Operations performed are logged, and for anything beyond the defined scope the assistant hands over to a human. How to turn any operation into a custom action is shown on the custom functions page.
- Book or reschedule appointments and send confirmations
- Qualify a lead and create it in the CRM or inbox
- Create a support ticket and escalate to a human
- Change an order or appointment with confirmation
- Run a configurator or calculation
| Action | Permission |
|---|---|
| Book appointment | automatic |
| Create lead in CRM | automatic |
| Change order | confirmation |
| Cancel appointment | confirmation |
| Create ticket | automatic |
Concrete Actions in Your Systems
Which actions make sense depends on your business. The following selection shows what a XICBOT assistant can take on through tool control — from pure reading to active operations. We put together the right actions for your case and expand them over time as new needs emerge.
- Show free appointments from the calendar, book, reschedule and send confirmations
- Query order and delivery status and state it directly in the chat
- Read stock levels and availability from inventory
- Add products to the cart, change quantities and apply vouchers
- Show shipping costs and delivery time and take visitors to checkout
- Qualify leads, capture contact details and create them in the CRM or inbox
- Pre-fill contact forms and submit them on request
- Create support tickets and escalate to a human when needed
- Request a callback and note the time for the response
- Run configurators and calculations and explain the result
- Deep-link to the right page or the right product
- Provide quotes or files and handle the newsletter sign-up
Permissions: Only What Should Happen
As soon as an assistant acts in a writing capacity, control is decisive. With XICBOT the assistant performs only the actions that were defined and approved beforehand — there is no open access to your systems, but a fixed list of permitted operations. For each of these actions you decide whether it runs automatically or requires a confirmation, for example by the customer in chat or by your team. Actions performed are logged, so it is always traceable what happened. And when a request goes beyond the defined scope or becomes sensitive, the assistant hands over to a human instead of guessing. Because an AI assistant can be wrong, this framework of permissions, logging and handover is the core of a responsible deployment.
Acting With the Handbrake On Where It Is Needed
How We Set Up Tool Control
Connecting to your systems sounds like a lot of effort but follows a clear process. We guide you from the first idea to live operation in four manageable steps. Throughout, you stay in control of which systems are connected, which actions the assistant may perform and which require a confirmation.
Clarify Systems and Goals
In the free initial consultation we look at which systems you use and which operations the assistant should take on. Calendar, CRM, inventory, ticketing or an internal tool — we check which interfaces exist and which actions bring the greatest benefit.
Individual package · net plus VAT
- Individual package: setup from 4,900 € net, operation according to scope
- Connection of your tools through defined actions (function calling)
- Reading and writing actions with clear permissions
- Hosting in Germany, self-hosted language models on request
Tool and API control belongs to the Individual package: a one-time setup from 4,900 € net, with operation according to scope of the connected systems and actions. Included are the connection of your tools through defined actions, reading and writing operations with permissions, hosting in Germany and care. On request, European or self-hosted language models. All packages at a glance under pricing. Every project begins with a free initial consultation and a demo.
With and Without Tool Control Compared
The difference between an assistant that only answers and one that also acts shows up in everyday practice in concrete situations. The following comparison makes clear where tool control goes the decisive step further.
| Situation | Assistant without tool control | With tool control |
|---|---|---|
| Appointment request in the evening | note about opening hours, callback needed | free slot shown and booked directly |
| Question about availability | generic standard answer, often outdated | current stock from inventory |
| Prospect with a specific need | text in chat, but no record | qualified lead created in the CRM |
| Question about order status | referral to the customer account | status queried live and stated |
| Writing operations | not possible, information only | performed with clear permissions |
| Data processing | often outside the EU | hosting in Germany, actions logged |
Typical Usage Scenarios
We do not advertise with invented success stories. The following journeys are anonymized and illustrative and show which operations tool control takes on in practice — from reading to a performed action.
What Tool Control Takes On
Illustrative examples from typical project histories (project experience) — anonymized.
Concrete Results on Request