Skip to content
XICBOT

Settings

Deutsch
Verifiable, not just claimed

References and project approach for your AI assistant

Instead of invented case studies, we show how we work: our competence areas around custom AI chat assistants, typical use scenarios per industry, our project approach and the technology behind it. Out of respect for our clients, we present concrete project results in a personal conversation.

In plain language

This page shows no made-up case studies. Instead, we show how we work. You will find the fields we know well. You will find typical uses for each industry. You can also read how a project runs and which technology we use. We only show the results of clients in a personal talk. Numbers only come from our own measurement.

Discuss your project Call: +49 5123 9579000

  • Answers with a source reference
  • Loads only after your consent
  • No minimum term, cancellable monthly
42 of 48
answers carrying a source reference
XICBOT, own measurement series of 11 September 2026
8 of 8
questions without a basis declined instead of guessed
XICBOT, own measurement series of 11 September 2026
2,670
sections from 70 documents in our own knowledge base
XICBOT, count in our own database
24.1 KB
loader on your page, compressed
XICBOT, own measurement of the delivered files
The question about references, answered honestly, Example conversation, reconstructed
  1. Visitor:Do you have references I can look at?

  2. Assistant:There is no invented case study here. Out of consideration for our clients we present concrete project results in a personal conversation.

  3. Visitor:And what helps me before that?

  4. Assistant:The fields of competence, typical scenarios per industry and the project approach — plus this assistant, which you can try out right here.

    • Reference · fields of competence · scenarios per industry · project approach
  5. Visitor:Are there at least figures I can check for myself?

  6. Assistant:Yes, but only from our own measurement series on this assistant, not from client projects. The method, the date and every single question are documented under measurements.

    • Own measurement series of 11 September 2026, measured on a single assistant on our own knowledge base: 42 of 48 answers carrying a source reference, 8 of 8 questions without a basis declined instead of guessed. A figure from the live operation of a client project is not available.

Ask it yourself, Assistant of this website

Automated assistant

Enter sends, Shift and Enter starts a new line.

The assistant only loads after your consent. Privacy

Our competence areas

XICBOT builds tailored AI chat assistants that truly know your website and shop: they read your content, products and documents, show product cards, put together a cart, take appointment requests and control connected tools. On this page you will find no invented figures, but an honest look at our work. We describe our competence areas, the typical use scenarios per industry, our structured process and the technology we build with. For a full overview of the scope, see services; for the matching cases per industry, see industries. Concrete results from comparable projects are something we are happy to show you directly in the initial consultation.

Every project is different, but the tasks can be grouped into recurring competence areas. In each of these areas we have built experience and developed proven approaches that we adapt to the requirements of each business. The fields interlock: an assistant that can read your content is only then able to perform meaningful actions, and conversation analytics reveals where the next competence area pays off. A click on a field takes you to the matching function page with all the details.

These fields state not only what the assistant can do but how it does it: which sources it reads, when it asks back, what it logs. The same mechanics are set out in full on the individual function pages; here they are condensed, so the initial consultation does not have to start from zero.

42 of 48

answers carrying a source reference

questions whose answer is in the knowledge base; six carried no source reference

Individual, not a kit

The difference from a standard chatbot with rigid menu trees is that every XICBOT assistant is trained on a specific business. It knows your services, products, prices, opening hours and documents, binds its answers to those sources and performs real actions on top. An AI assistant can be wrong, which is why we deliberately rely on binding to your own content, handover to humans on sensitive topics and continuous evaluation through conversation analytics. This keeps the assistant close to the reality of your operation, instead of being set up once and then left to itself.

  • Individually trained on your website, catalog and documents instead of a generic script
  • Answers bound to your own sources, with a pointer to the matching page or product
  • Real actions through defined functions, with approvals and confirmation instead of mere text snippets
  • Handover to a human with full conversation context, especially for complaints or legal questions
  • Multilingual answers from one knowledge base, without maintaining content twice
  • Continuous improvement from conversation analytics, step by step and transparently

Typical use scenarios per industry

Which tasks an assistant takes on depends heavily on the industry. The following scenarios describe typical starting situations that businesses bring to us, without referencing specific client projects. They illustrate the kinds of tasks we regularly solve and the building blocks involved. You can find all industries at a glance under industries.

  • Online shop: advice, product cards and cart

    A shop wants to relieve support and guide more visitors to a purchase. The assistant for online shops advises on products and variants, shows product cards in the chat, checks availability, gives the order status through a connected inventory system in the Custom package and puts together a cart in the chat, right through to the move into the shop.

    • Product search returns a handful of hits instead of a list to scroll through
    • An order status comes only from a connected inventory system and belongs to a person: by default the assistant asks for confirmation before disclosing it
    • The cart is built in the chat and sits with XICBOT; it only reaches your shop's cart through an integration of its own
  • Service providers and trades: qualifying enquiries

    A business receives many unstructured enquiries. The assistant for service providers answers questions about services and coverage areas, qualifies requests with follow-up questions, pre-fills forms once the visitor confirms, collects documents and hands over clean leads with their context. For trade businesses it adds emergency routing to a human.

    • The lead carries name, request and the transcript; uploaded files are attached to it
    • The handover visibly sets the conversation to escalated and notifies a person
    • What the assistant does not know, it says - the emergency line does not run on a guessed answer
  • Practices and law firms: appointments and guidance

    Phone and reception are overloaded. The assistant for practices takes appointment requests, states consultation hours and preparation. In law firms it qualifies initial enquiries and points the way. Important: no medical or legal advice, but guidance and handover to humans.

    • The assistant calculates free times from your appointment types without changing anything
    • Requesting, rescheduling and cancelling happen only after a confirmation
    • Advice is under a fixed block: sensitive topics are meant to go to a human, with the full transcript
  • Hospitality, hotels and real estate: reservation and viewing

    Guests and prospects want fast answers. In hospitality the assistant handles table requests, menu, allergens and catering enquiries. In real estate it answers listing questions, arranges viewings and qualifies prospects by budget and needs.

    • The appointment types of the business are offered to the assistant as a fixed selection, not as free text
    • A second confirmation does not create a second appointment - every writing action carries a one-time key
    • Allergens, opening hours and listing details come from your material, not from the language model
  • Software and SaaS: onboarding and ticket relief

    Support keeps answering the same questions. The assistant for software and SaaS answers feature and pricing questions from the docs, helps with onboarding, takes demo requests and takes on ticket deflection before an enquiry lands in the inbox. More under support assistant.

    • Creating a ticket is a writing action and runs through proposal and confirmation
    • One answer carries only a limited number of tool calls; beyond that the run stops and is logged
    • Sourced answers from the documentation name the excerpt they rest on

These are starting situations, not client projects. Which of these building blocks carry in your case depends on what your material contains and which of your systems offer an interface - we clarify both before we talk about effort. All industries at a glance are under industries.

2,670

sections from 70 documents in our own knowledge base

the corpus of the assistant answering on this site

Source 11 September 2026

XICBOT, count in our own database
Measurement series
select count(*) from knowledge_chunks c join knowledge_documents d on d.id=c.document_id -> 2670

What an assistant achieves is stated as a number

  • Self-resolved and handed to a person stand side by side for the same period.

  • Answers with a citation shows how much rests on a source.

  • A figure without a basis stays visible as not measured.

Demo account with sample data, German interface
Analytics: a seven-, thirty- or ninety-day window, followed by the usage and answer-quality groups with figures such as self-resolved, handed to a person, answers with a citation and no answer.

Our project approach

The process is where the sentence "we show no case studies" turns into something you can check. Every phase leaves a result you can look at: a test assistant on your own content, the list of sources it has read, the list of actions it is allowed to perform, and after that an analysis that also states what it could not measure. Results from comparable projects we show in the initial consultation, because they are not on this page; contact with an existing client we arrange after checking with them.

You could also set the assistant up entirely on your own: create an account, add sources, embed the script - no step strictly requires us to intervene. Our support is an offer, not a condition. The scope grows with you instead of being locked into a rigid package: you can start with a website assistant and later add shop functions, appointments or the control of your own tools, without starting over.

  1. Initial consultation and test assistant

    We listen: what defines your business, which questions come up often, which tasks should the assistant take on? On request we set up a free demo with a test assistant for your website, so you can see on your own content where it carries and where it does not. The initial consultation is free and non-binding.

  2. Training on your content

    We train the assistant individually on your sources: website, documents, FAQ, price lists and the shop catalog. Every source stays visible on its own and can be switched off; answers stay bound to that content instead of being invented out of thin air.

  3. Defining the Actions

    You decide what the assistant may do: read only, or also take an appointment request, create a ticket, put together a cart. Writing actions go to the visitor as a proposal and run only after confirmation, and every call leaves a protocol row. More under tool control.

  4. Integration

    We embed the assistant with a short code snippet into your website, CMS or shop. Only the loader runs on your page; the chat window sits in a frame of its own and loads only once your page has finished loading. Without JavaScript nothing appears - but then nothing slows your page down either. Details under integration.

  5. Operation, test set and improvement

    After launch we take over operation, maintenance, updates and hosting in Germany. A fixed set of questions runs against the knowledge base every day and reports when an answer loses its source. Through conversation analytics you see frequent questions and knowledge gaps; the person from the initial consultation stays your contact.

What this process deliberately does not state is a deadline. How quickly an assistant is ready depends on how many sources come together and how fast approvals come back from your side - neither is ours to control, and a promise about it would be a figure without a basis. After the initial consultation we name an effort, not a date.

Check it on the test assistant

As long as no released client testimonial stands on this page, one route remains: look for yourself. The assistant on this page is the same one we ship, and it answers from our own knowledge base. Six moves you can make yourself without signing up; each one states what should happen. If something deviates, you have a finding rather than an impression - and please bring it to the initial consultation.

  1. Ask something that is on our website

    Expected: an answer that names the excerpt it rests on. The assistant builds its answer from the sections it retrieved and numbers them. If not a single excerpt is used, the answer appears without a source reference and is logged as a gap in our gap list.

  2. Ask something that is stored nowhere

    Expected: a refusal rather than an invention. If no excerpt carries the answer, the assistant says it has nothing on this and points the way to a human. Nor is it supposed to invent contact details when they are not in the material.

  3. Ask for a human

    Expected: a visible change of state. The handover sets the conversation to escalated, creates a contact with the full transcript and notifies a person. The visitor gets a clear statement, not an endless loop.

  4. Let it do something

    Expected: a proposal, not an accomplished fact. Writing actions show beforehand what will happen and wait for confirmation. The protocol row is created before execution, and tapping Confirm a second time does not create anything twice.

  5. Switch language mid-conversation

    Expected: the assistant switches with you, without you changing a setting. Detection runs in our own code on function words, for nine languages each with its own word list. If the result is not unambiguous, the field stays empty instead of guessing German. More under multilingual.

  6. Look into the analysis

    Expected: figures with a basis - and where the basis is missing, the note not measured plus a reason instead of a zero. A zero would look like a measured result, and exactly that difference decides whether an analysis is worth anything. To be seen under conversation analytics.

What this route does not answer: how an assistant behaves with your traffic, your catalog and your edge cases. The figures on this page come from our own measurement series on a single assistant on our own knowledge base, not from client projects. Every question and every answer of that series is documented verbatim under measurements.

8 of 8

questions without a basis declined instead of guessed

eight questions deliberately outside the material; the wording of every answer is in the measurement file

43 of 48

questions without a handover to a person

measured on a single assistant on our own knowledge base, not on customer projects; a figure from live operation is not yet available

Technology we use

A good assistant comes from the interplay of individual training, clean integration and privacy-compliant operation. We rely on modern AI language models combined with a firm binding to your own content, so the answers stay dependable. Integration runs via snippet in your site's design, on request as a first-party solution over a path on your domain, instead of a bloated third-party widget. Actions run through clearly defined functions with approvals, so the assistant only does what you allow.

Technology that fits your business

Instead of a rigid kit script, behind every XICBOT assistant is an individually trained setup. The assistant reads your sources, performs actions through defined functions and is meant to hand over to a human on sensitive topics. Operation and hosting are in Germany; the answers are generated by a specialised model provider, also outside the EU on the basis of standard contractual clauses.

  • Integration via snippet, first-party on request, fast and in your site's design
  • Answers bound to your content, with handover to humans
  • Actions through defined functions, with approvals and confirmation
  • Shop connection based on Shopware Community Edition
  • Every tool call leaves a protocol row, written before execution
  • The chat window runs in a frame of foreign origin and does not read along on your page

1.3 s

to the first character of the answer, median

64 questions to our own assistant, not to customer projects

24.1 KB

loader on your page, compressed

only the file that runs on the host page, measured with the compression the web server actually sends; the chat window lives in its own frame and loads only once your page has finished loading

What is evidenced here, and what is not

On this page there is no testimonial, no logo and no before-and-after figure from a client project. That is not modesty: we have no release for them, and a figure without a release would be a claim about someone else's business. One column therefore names what is missing here, the other what can be read up - side by side, so you see the boundary instead of guessing at it.

For the businesses that work with us the value does not lie in yet another tool that needs maintaining, but in a dedicated contact who trains, integrates, operates and continuously improves the assistant. You keep sovereignty over your data and your content, while we take care of technology, hosting in Germany and further development.

Not evidenced

  • Results from client projects: we have no release for them. So there is no before-and-after figure, no revenue effect and no relief value on this page.
  • Testimonials, logos, case studies: a real quote needs a signed release. As long as there is none, none stands here - not even a watered-down one.
  • Number of projects delivered: an in-house experience value that cannot be recalculated from outside. That is why we do not carry it as evidence.
  • Figures from live operation: what an assistant achieves with your traffic cannot be read from our measurement series. It ran on a single assistant on our own knowledge base.
  • Deadlines and shares: when a set-up is finished and how much an assistant settles on its own at your site is nothing we promise in advance.

Evidenced and open to reading

  • The measurement series behind the figures: date, method, every question and every answer verbatim. The figures on this page come from it and from no other source: measurements.
  • Source binding: an answer without a single used excerpt is recorded as a gap. That is not a statement of intent but a condition in the code.
  • Not knowing: if nothing is on file for a question, the assistant says so and points to a human instead of guessing. That, too, can be read in the measurement series.
  • Analysis in your own account: where a figure has no basis, it says not measured plus the reason - no zero that looks like a result.
  • Contact with existing clients: on request and after checking with them. A conversation with a business that uses the assistant daily carries further than an anonymous quote.

Concrete results on requestOut of respect for our clients, we do not publish detailed case studies with numbers on the website. In a personal conversation we are happy to present concrete results and examples from comparable projects, without sales pressure. Arrange a non-binding initial consultation.

„We promise no miracle numbers and no assistant that never errs. We build assistants that truly know your business, are bound to your content, hand over to humans when needed and get more accurate with every week.“ — Our approach

How a project runs with us is described step by step in from idea to a live AI chat assistant. How we check before go-live whether an assistant is really ready is covered in accepting an AI assistant: test cases before go-live.

Frequently asked questions

Two questions almost always come first at this point: why there are no case studies with figures here, and whether you can talk to someone who uses the assistant every day. Both are therefore at the top, with the same answer we give on the phone.

Why don't you show detailed case studies with numbers?

Out of respect for our clients and because generic before-and-after figures are rarely meaningful. Instead of invented success stories, we describe our competence areas, typical use scenarios per industry and our project approach. Verifiable figures arise where they belong: in your own account. Conversation analytics evaluates your own conversations only; it deliberately contains no industry benchmark and no revenue attribution, because both would be a figure without backing. Concrete results and examples from comparable projects are something we are happy to show you in a personal initial consultation.

Can I speak with reference clients?

If you have serious project interest, we are happy to arrange contact with existing clients who will talk about the collaboration, after consulting them. This of course only happens with their explicit consent. That way you get an honest first-hand picture instead of relying on anonymous quotes. For the same reason there are no invented voices and no before-and-after figures on these pages. If you would rather check for yourself: on request we set up a free demo with a test assistant on your own content — you can arrange the appointment for it via contact.

Which industries do you build assistants for?

Nine industries have worked-out pages with the concrete tasks: online shop, service providers, hospitality, practices, trades, real estate, car dealership, law firms and software. You will find the overview under industries. That list is a selection, not a boundary, because the assistant knows no industry logic — it knows your sources and your tools. Knowledge arrives as free text, a file, a website or a maintained question-and-answer pair; tasks come from seventeen tool types, and where none of them fits, a schema of your own with up to twenty fields describes the call into your system. Which of this your business needs is what we clarify in the free initial consultation.

Can you cover a case that doesn't exist yet?

Yes. Alongside the standard building blocks, we construct individual actions, workflows and cases as needed, with custom logic, connections to your systems, calculations or configurators. Technically every such action goes outward over the same path as the standard blocks: with target checking, a fixed time limit and a size cap. Your system’s response is filtered down to the result fields agreed in the tool — so the assistant only receives what you have released, and a response without the agreed confirmation field counts as an error, not as a result. Custom actions and cases belong to the Custom package. What is possible is described under custom functions and tool control.

What technology and shop system do you use?

We combine modern AI language models with a firm binding to your own content, embedded via snippet, on request as a first-party solution via your domain. A single script line sits on your page; it opens a shielded area and only inserts the chat as a frame of its own after the page has fully loaded, without access to the surrounding document. The loader itself makes no network call, brings no stylesheet and sets every property individually, so your layout stays untouched. Both parts of the frame carry a name derived from their content together with a checksum. For shops we work with Shopware in the Community Edition, an open-source system without license lock-in. Hosting is in Germany; the answers are generated by a specialised model provider, also outside the EU on the basis of standard contractual clauses.

How do we start a project?

With a free initial consultation and, on request, a free demo with a test assistant for your website. In it we clarify goals, the most frequent questions your customers ask and the right actions. Seven shapes are available at the core — enquiry, appointment, handover to a human, product search, cart, a fetch of your own and pre-filling a form once the visitor confirms — plus ten adapters for inventory, calendar, catalogue, CRM and ticketing, each with its own kind and its own approval mode; the fetch of your own and the ten adapters come in the Custom package. You then receive a transparent offer before implementation begins. You can find all services at a glance under services.

If your question is missing, we answer it in the initial consultation. The complete collection is under frequent questions, the set-up step by step in the documentation.

Verifiable

The measurement series behind the figures

The figures on this page come from our own measurement series against our own assistant. Method, period and the limits of each claim are set out under measurement series: the figures on this website.

Request a project: free initial consultation

Briefly outline your project: which questions should your assistant answer, which actions should it take on? You receive an honest assessment, the results from comparable projects that are not on this page and, on request, a test assistant for your website. We store your details on servers in Germany. You can reach us by phone at +49 5123 9579000.

Enquiry in three steps

  1. 1. Topic
  2. 2. Your case
  3. 3. Contact

What is this about?

One click is enough, everything else is optional.

Tell us briefly about your case

Everything in this step is optional. It helps us reply with something concrete straight away instead of asking back.

Enquiries per month, roughly (optional)
When should it start? (optional)
How can we reach you?

Name and email address are enough. We reply personally.

We use your details to handle your enquiry. More on this in the privacy policy.