Visual CMS & headless page building

AI Chatbot for Builder.io — install it once, and every page your team publishes has support

Q: How do I add a chatbot to Builder.io pages?

There are two routes. A developer can paste the Asyntai snippet into the host application's root layout once, for example app/layout.tsx or pages/_document.tsx in a Next.js project, so it loads on every route including every Builder.io page. Without a developer, an editor can drop a Custom Code block onto a page in the Visual Editor and paste the snippet there.

Q: Do I need a developer to install the chatbot?

Not necessarily. The Custom Code block is available in the Visual Editor and needs no code review or deployment. A developer is only required for the site-wide install, because Builder.io renders its content inside your own application and the head of that application is owned by your codebase.

Q: Can I put the chatbot on every Builder.io page without editing each one?

Yes. Either use the host app layout, which covers every route at once, or place the Custom Code block inside a Symbol that is already reused across your pages. Updating the Symbol updates every page that references it.

Q: Does it work with the Builder.io React, Next.js and Qwik SDKs?

Yes. The widget is a plain script tag with no framework dependency, so it does not care which Builder.io SDK renders the page. It runs in the browser after the page loads, the same way an analytics tag does.

Q: How does the chatbot learn what our product does?

Asyntai crawls the published site, including the pages your team builds in Builder.io, and you can add documents and written instructions in the dashboard. The bot answers using your own content rather than general AI knowledge.

Builder.io exists so marketing can ship a landing page on Thursday without opening a ticket. Support should work the same way. Asyntai is one script tag: a developer adds it to your app layout once, or an editor drops it into a Custom Code block on a single page. From then on, every page answers visitor questions from your own content, captures leads, and never blocks on a sprint.

Get Started Free See the 3-step install

Try the chatbot on a page you built in Builder.io

Enter a published URL and see the answers the bot gives on your real content.

Why Builder.io teams should not file a ticket to get a chatbot

The reason a company adopts Builder.io is almost always the same story. Marketing needed a page. Engineering had a roadmap. The page took six weeks, arrived after the campaign, and everyone agreed that could not happen again. A visual CMS on top of the real codebase fixed it: content people compose pages from registered components, and engineering keeps owning the components rather than the copy.

Then the same pattern reappears one layer down. The campaign page goes live and starts pulling traffic, and the traffic has questions — about pricing tiers, about the migration path, about whether the integration everyone asks for actually exists yet. The answers live in a docs site, a spreadsheet, and one person's head. The page itself says nothing back.

A page that ships in a day should not need a quarter to become answerable.

Adding a chatbot is where teams accidentally recreate the old bottleneck. Someone requests a widget, it goes into a backlog, and three sprints later the campaign is over. It does not need to work that way. Because Builder.io renders inside your own application, the site-wide install is a single line in a layout file — a five-minute change a developer can make once, permanently, for every page the content team will ever publish. And for a page that cannot wait even for that, the Visual Editor has a Custom Code block that needs no deploy at all.

The result matches the reason you bought Builder.io in the first place: the marketing team ships the page, and the page arrives already able to talk to the people who land on it.

How to add the chatbot to a Builder.io site in three steps

Create the bot. Sign up free at Asyntai, enter your published domain so the crawler can read your live pages, and copy the snippet from your dashboard.

Put the snippet in the host app, or in a Custom Code block. For the whole site, a developer adds it to the root layout of the application that renders your Builder.io content — app/layout.tsx or pages/_document.tsx in a Next.js project, the equivalent shell template in React, Qwik, Angular or Remix. For one page, an editor opens the page in the Visual Editor and drags in a Custom Code block, then pastes the snippet into it.

Deploy or publish. A layout change ships with your next deploy. A Custom Code block goes live the moment you publish the entry in Builder.io.

Middle option worth knowing. If you want the chatbot on many pages but do not want to touch the codebase, put the Custom Code block inside a Symbol that your pages already reuse — a global footer, for example. Every page referencing that Symbol picks the widget up, and one edit updates all of them.

Builder.io documentation recommends the Custom Code block over hand-written custom JavaScript for adding HTML to a page or section, which is exactly what a chat widget snippet is. If your Custom Code block contains script that should never execute during server rendering, the block's advanced settings include a client-only option for precisely that case.

What the chatbot does on your Builder.io pages

Answers using your own content

It reads your published pages, docs and uploaded files, then answers from those. Retrieval over your material, so it will not invent a roadmap item.

Lead capture on campaign pages

When someone is evaluating, the bot takes their details and the transcript goes to your dashboard — no extra form to build in the editor.

30+ languages automatically

The bot detects the visitor's language and replies in it, which matters when one Builder.io page serves several markets.

Framework-agnostic script

No SDK, no npm package, no build step. One tag that behaves like any analytics snippet, whichever renderer your app uses.

Builder.io chatbot questions

How do I add a chatbot to Builder.io pages?

Either paste the snippet into your app's root layout once, so it covers every route, or add a Custom Code block to a page in the Visual Editor and paste it there.

Do I need a developer to install the chatbot?

Not for the Custom Code block route — that is editor-side and needs no deploy. A developer is needed only for the site-wide install, because the application shell is your codebase.

Can I put the chatbot on every Builder.io page without editing each one?

Yes. Use the host app layout, or put the block inside a Symbol your pages already reuse. Editing the Symbol updates them all.

Does it work with the Builder.io React, Next.js and Qwik SDKs?

Yes. It is a plain browser script with no framework dependency, so the choice of Builder.io SDK makes no difference.

How does the chatbot learn what our product does?

It crawls the published site and anything else you point it at, and you can upload documents and write instructions. See pricing for plan limits; the free plan includes 100 messages a month.

Other headless and visual platforms

The same script tag drops into any front end you control.

Give the next page an answer, not a form

One snippet, one layout file or one Custom Code block, and every Builder.io page you publish can hold a conversation. Free to start with 100 messages a month.

Get Started Free