Embed Your AI Assistant with a Single Snippet
One short code snippet is enough, and your XICBOT assistant lives inside your website, your CMS or your shop. Everything is delivered first-party over your own domain, in the design of your site and without a bloated third-party widget — lean, fast and GDPR-compliant with hosting in Germany.
1 snippet
integration into website, CMS or shop
first-party
same-origin over your own domain
< 1 day
approval to live (project experience)
any CMS
website builder, Shopware CE or site
Many chat solutions come as a heavy third-party widget: they load over a foreign domain, bring advertising ballast, slow the page down and look like a foreign body that belongs to someone else. XICBOT takes the opposite route. You add a short snippet — one line in the page head — and the assistant becomes a fixed part of your site. It loads first-party over your own domain, adopts your colours and fonts and is then exactly the assistant we trained on your business beforehand: one that reads your website content, shows products, books appointments and controls your tools. The integration is the same short step whether you run a website builder, a CMS or a shop based on Shopware Community Edition. For you this means no change of system, no rebuild of your site and no second presence just for the chat — the assistant comes to your existing site, not the other way around.
One Snippet — and the Assistant Lives in Your Site
How the Integration Works
The technical integration is deliberately kept as simple as possible, because it should hold no one up. You receive a short snippet from us that you insert once into your site — or that we insert for you. From that moment the assistant is active, the one we trained individually on your business beforehand. It knows your content, your catalogue and your processes and carries out real actions in the chat. The following six points show what sets the XICBOT integration apart and why it differs from an ordinary third-party widget.
One Snippet, Everywhere
One short line in the page head is enough. You add it in a website builder, in a CMS or directly in the theme — the same simple step for website, landing page and shop.
Delivered First-Party
The assistant loads same-origin over your own domain, not over a foreign widget domain. That is lean, controlled and fits our principle for privacy and hosting.
Fast, No Ballast
No bloated third-party widget, no advertising code. The assistant loads lean and asynchronously so your page stays fast and neither load time nor user experience suffers.
Adapts to Your Design
The assistant adopts colours, font and corner radii from your site. It looks like a natural part of your presence rather than an added-on foreign element.
Website, CMS or Shop
Whether an individual website, a common CMS, a website builder or a shop based on Shopware Community Edition — the snippet embeds the assistant everywhere in the same way.
GDPR-Compliant Integration
The integration is privacy-friendly, with hosting in Germany and without selling data. We clarify details and data processing under privacy and hosting.
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
Just as important as the technical step is that you keep control. You decide on which pages the assistant appears, which content it may read and which actions are approved for it. Changes to text, products or processes are maintained by us for you, without you having to touch the snippet again. Because the assistant runs first-party over your own domain, it fits cleanly into an existing consent management setup and is treated there like any other component of your site. This keeps the integration not only simple but also transparent and in your hands — today and with every later adjustment. And because a XICBOT assistant can speak several languages on request, the same single snippet also covers international visitors without you having to embed a second chat.
First-Party Instead of a Bloated Third-Party Widget
The most important difference is not the chat window itself, but where it is loaded from and what happens afterwards. A typical third-party widget loads over a provider's domain, often brings additional code and knows nothing about your specific business. XICBOT delivers the assistant first-party over your own domain — and after that it is not just any chat window, but the assistant trained on your company that reads and acts.
First-Party Instead of a Foreign Domain
Same-origin means the assistant belongs to your site, not to a third-party domain. That is leaner, gives you control and fits cleanly into your presence and your data-protection structure. No advertising ballast, no foreign branding, no unnecessary cargo that slows your page down.
- Delivery over your own domain instead of a widget domain
- Loaded lean and asynchronously, without advertising code
- Your site's design instead of a foreign appearance
Embed Once, Then the Assistant Reads and Acts
Once the snippet is in place, the assistant we trained on your business gets to work. It reads your content and your catalogue and carries out real actions with permissions in the chat — from the answer through the product card to the booked appointment and the handed-over lead. The integration is a one-off; the benefit runs continuously afterwards.
- Reads website, catalogue, opening hours and documents
- Adds products to the cart and books appointments
- Hands over structured leads and tickets, with human handover
From Enquiry to the Embedded Assistant
The integration itself is the last, short step of a clear process. Before it comes the individual training, so the assistant knows your business before it goes live. At every step you keep control over what the assistant reads, which actions it may perform and when it hands over to a human. This is what the path from the first enquiry to the embedded assistant looks like.
Initial Consultation and Demo
Every project begins with a free initial consultation and, on request, a free demo with a test assistant for your own website. You see in advance how the assistant works on your content before you decide.
Start entry point · net plus VAT
- Integration with one snippet, first-party over your domain
- Start: operation from 49 € per month net, setup from 990 € net
- On request we handle the integration for you
- Free initial consultation and demo with a test assistant for your website
Pricing model: a one-off setup from 990 € net (individual training and integration) plus monthly operation from 49 € per month net (hosting in Germany, maintenance, updates, GDPR). The Pro package with shop connection, product cards and cart starts from 149 € per month net, individual tool and API control starts at a setup from 4,900 € net. You will find all packages under pricing. Every project begins with a free initial consultation and a free demo.
Third-Party Widget and XICBOT Compared
Where is the difference in everyday practice once the assistant is embedded? The comparison shows why a first-party integrated solution that knows your business works differently in loading behaviour, appearance and benefit than an interchangeable third-party widget.
| Aspect | Bloated third-party widget | XICBOT · first-party |
|---|---|---|
| Delivery | over a foreign widget domain | same-origin over your own domain |
| Loading behaviour | additional code, often advertising ballast | loaded lean and asynchronously |
| Appearance | foreign branding, added on | your site's colours and font |
| Knowledge of your business | generic, does not know your offering | individually trained on your content |
| Actions in the chat | mostly text answers only | shows products, books appointments, controls tools |
| Data protection | data flow to third-party domain unclear | hosting in Germany, without selling data |
What the Assistant Takes On After Integration
The integration is a means to an end: in the end the assistant should help your customers and relieve your team. The following examples show, anonymised and illustrative, which concrete tasks an embedded assistant takes on from reading and actions — combined differently depending on the industry.
Typical tasks after integration
Illustrative examples from typical project histories (project experience) — anonymized.
Concrete Results on Request