Webflow sites are usually beautifully built and thinly supported, because the people who build them are designers rather than support teams. That is why an AI assistant that learns from the pages you already wrote is such a natural fit — and why the install path matters more here than on any other platform: if it touches the Designer, breaks on publish, or does not see CMS collection pages, it will be switched off by Friday.
We make one of these, and it is listed first. The six below were compared on the same five things: how it installs on Webflow, whether Webflow's paid-plan gate applies, whether it reads CMS pages, what the answer shows, and what the entry plan meters. Read us with the same scepticism you would read anyone; the last section is a test that needs no vendor present.
The two ways anything installs on Webflow
There are exactly two routes. A listing in the Webflow Apps marketplace installs through OAuth — no snippet, no custom-code panel — and is the only route that works on a free Webflow site. Everything else is a script pasted into Site settings → Custom code → Footer code, which is applied site-wide, covers CMS collection templates automatically, and needs a paid site plan. Both are fine. The difference is who you are: an agency running many client sites usually prefers the snippet (it is the same two lines everywhere); a designer on one site may prefer the App.
The comparison
| Tool | Installs via | Reads CMS pages | Citations | Entry paid plan |
|---|---|---|---|---|
| Matter Chat | Footer custom code, two lines | Yes — crawler reads published collection pages | Every answer, linked to the page | $29/mo yearly: 2,000 replies, 200 pages, seats included |
| Social Intents | Webflow App + custom code | Crawls URL/sitemap; CMS not called out | Not documented | $29/mo: 60 conversations, 1 seat, 1 widget |
| Ultimo Bots | Webflow App (OAuth) or one-line code | Not documented; site-URL training unavailable on Webflow App installs | Not documented | $29/mo per agent: 500 responses, then pauses |
| Chatling | Head custom code | Crawl up to 1,000 pages; no CMS connector | Optional, off by default | $25/mo: 1,750 credits, 2 agents |
| WeblyChat | Footer custom code | Yes — “static and CMS Collection pages” | Not documented | $19.99/mo: 1,500 messages, 2 MB knowledge |
| Chatbase | Embed element (iframe) or bubble script | Full crawl/sitemap; no CMS connector | Not documented | $40/mo: 700 credits, 2 seats |
Matter Chat
Ours. Install is the two-line snippet in Footer code; it renders over the page rather than inside your layout, so nothing in the Designer changes and collection pages inherit it on publish. The crawler reads published CMS pages the same way it reads static ones, which is the point on Webflow — a CMS full of case studies or help articles becomes answerable, and every answer carries a citation to the item it came from. When your pages do not cover a question the bot refuses and logs it; you see the list and write the page. Plans meter replies with hard caps and no overage, and every plan includes its team seats.
What to weigh against it: there is no Webflow Apps listing yet, so it needs a paid site plan like every other custom-code install, and there is no built-in live chat suite — handoff goes to the inbox, Slack or email, with WhatsApp and SMS on Agency. The Webflow install page has the snippet and the click path; domain locks matter once a client site goes live.
Social Intents
Best if your team already answers chat from Teams, Slack or Google Chat — that is its whole model, with AI on top. It has a real Webflow Apps listing and a custom-code route, and its docs state the paid-plan gate plainly. Knowledge comes from URLs, sitemaps and files. Two things to check: citations are not documented, and the help articles describe bringing your own OpenAI key while the landing page says AI usage is included — ask which applies to your plan before you buy.
Ultimo Bots
The most Webflow-native install of the six: an App Market listing, OAuth, no code, and the script updates itself on publish. The catch is in its own docs — website-link training is unavailable for Webflow App installs under marketplace rules, so you train from files, FAQs, Drive or Notion instead. Pricing is per agent and hard-pauses at 500 responses a month on the entry plan. Good fit for a single designer-run site with a small FAQ; less so for a content-heavy CMS.
Chatling
The cheapest entry plan here with live chat, voice minutes and several channels included, installed by head custom code. Citations exist but are off by default, so turn them on before judging the answers. Model the credit multiplier: an answer costs 0.5 to 25 credits depending on the model, so the 1,750 on the entry plan is either plenty or about seventy premium answers. Removing the badge is a $35 add-on, more than the plan.
WeblyChat
The budget pick, and unusually clear in its Webflow docs — it says which Webflow plans support custom code and that it covers CMS collection pages. Knowledge is sized in megabytes rather than pages, it stops answering at the monthly cap until the next cycle, and the badge only comes off on the top tier. Live chat is not documented; the fallback is a contact form or your phone number.
Chatbase
Best if you want the bot, a helpdesk and voice from one vendor. On Webflow its documented route is an Embed element on the canvas, which is simpler than custom code but also not site-wide — plan where the bubble lives. Citations and refusal behaviour are not documented, there is no CMS connector, and the costs to watch are the credit meter, $25 per extra agent and $99 to remove branding.
Which one, for whom
- Content-heavy Webflow CMS, agency or founder, want every answer to cite the page: Matter Chat or WeblyChat.
- One designer-run site, no code at all, small FAQ: Ultimo Bots via the App Market.
- Your team lives in Teams or Slack and wants to answer live: Social Intents.
- Budget first, live chat included: Chatling.
- One vendor for bot, helpdesk and voice: Chatbase.
Test it on your own site before you decide
Every tool above has a free tier or trial. Install on a staging publish, let it read your site, then ask four questions: one a CMS item answers, the same one badly paraphrased, one your site does not answer, and “can I talk to someone”. Check that the citation resolves to the actual item, that the paraphrase lands the same answer, that the out-of-scope question gets a refusal rather than an invention, and that the handoff keeps the conversation. The full protocol is how to test an AI support tool in twenty minutes; on Webflow, also read staging domains will poison your answers before you go live — the .webflow.io subdomain is exactly the kind of host that leaks into an index.
