Social Intents

How to integrate Social Intents with Webflow

A published Webflow page can say anything and answer nothing. Forms tell you what a visitor typed after they have already left, so the questions that decide a sale go unasked. Live chat fixes that, and on a Webflow site the real decisions are narrow: where the vendor's script goes, which plan that requires, and what the extra script does to consent and page weight.

What is Social Intents? Social Intents is a live chat and AI chatbot service built around where your team already works. Rather than a separate agent console, it delivers website chats into Slack, Microsoft Teams, Google Chat, Zoom or Webex, and its pricing page lists all five as current response channels. A web dashboard is there if you want one, and an AI chatbot built on ChatGPT, Claude or Gemini answers when nobody is available.

On Webflow there are three things to get right, and they stack in this order: the marketplace app installs and maintains the widget for you, a manual script install gives you control over which pages load it, and the JavaScript SDK passes visitor context from your site into the chat. Most teams start with the app and reach for the other two when chat has to know who it is talking to.

Install the Social Intents app

The Social Intents Live Chat listing in the Webflow App Marketplace is the fastest route, and it is the one the vendor documents for Webflow. Webflow has reviewed the app, and it declares three permissions you should read before you authorize it: read information about authorized users, read and write custom code, and read site data and publishing. That second one is the whole mechanism, since the app writes the widget snippet into your site's custom code rather than asking you to paste it.

Installation runs in four steps:

1. Install the app from the marketplace listing and authorize it against the Webflow site you want chat on.
2. Create a Social Intents account, or sign in to an existing one, when the onboarding flow hands you off.
3. Select which of your Webflow sites should carry the widget.
4. Pick a response channel such as Slack or Microsoft Teams, or skip it and connect one later from the dashboard.

The widget is enabled on the selected site when you land in the dashboard, and everything after that (routing rules, office hours, branding, chatbot training) is configured on the Social Intents side, not in Webflow. Because the app holds write access to your custom code, treat it like any other authorized app: review the permissions before you install, and revoke access from your site settings when you stop using it, since an app that still holds scopes can still act on the site.

Paste the chat snippet yourself

Install the script by hand when you want the widget on some pages and not others, or when you would rather not grant an app write access to your custom code. Log in to Social Intents, open Apps in the left sidebar, and click the code icon on the widget you want; the vendor publishes two versions of that code snippet, a single line and a longer form that lets you initialize parameters, plus an iframe variant for embedding chat inside a page.

Where you paste it decides the scope. For every page on the site, put the snippet in Webflow's footer custom code, which loads before the closing body tag on the published site. For a single page or a single Collection page template, drop it into a Code Embed element instead and place that element in the layout. Both routes need a paid plan: a paid Site plan (Basic at $15 per month, Premium at $25 per month) or a paid Workspace plan on Core, Growth, Freelancer or Agency. Social Intents says the same thing in its own Webflow guide, which notes the Embed element requires a paid plan.

The "Made in Webflow" badge sits in the same corner as the chat button, and the vendor ships CSS for moving the widget clear of it:

<style>
  #si-wrapper .silc-btn { bottom: 55px !important; right: 25px !important; }
  #siWidget-chat { bottom: 120px !important; }
</style>

Two costs come with the manual route and with the app, because both end up loading the same third party script. The script is not yours, so it can set its own storage before your consent banner has decided anything: gate the snippet behind a consent category rather than hard coding it into the footer, and check what you are declaring, because Social Intents stores chat data on AWS servers in the United States and documents its GDPR position, including an option to stop storing transcripts at all. The second cost is weight. It is an extra request and extra script execution on every page it loads on, so scope it to the pages where a conversation is plausible and keep it off long CMS archive pages where it buys you nothing.

Pass visitor context with the SDK

Once the snippet is on the page, Social Intents exposes an SI_API object, and this is where a Webflow site earns its keep: you already know which CMS item the visitor is reading. Wrap calls in the onSIApiReady() callback, because the script loads asynchronously.

The JavaScript SDK covers the cases that matter on a marketing site. setChatInfo(name, email, phone, group, question) pre-fills the visitor's details and routes the chat to a department, which is how you hand a signed-in member's identity straight to an agent when you run accounts through a tool like Memberstack. addParams() attaches your own key and value pairs, such as an order number or the slug of the Webflow CMS item being viewed, so the agent opens the chat already knowing the context. showInvite(), showTab() and showPopup() control when the widget appears, and callbacks such as onChatOpened let you fire an analytics event. Chat transcripts and leads leave through the REST API or Zapier into a CRM.

One thing Social Intents does not offer is an MCP server. Its documented programmatic surfaces are the JavaScript SDK and the REST API, and nothing in its developer docs or help center describes an MCP endpoint, so do not plan an agent workflow around one.

What you can build with the Social Intents Webflow integration

The useful builds here are the ones that use what Webflow already knows about the page and hand it to whoever answers. Chat that arrives in a channel with context attached gets answered; a bare "someone is chatting" ping does not.

Four patterns hold up in practice:

• Sales chat routed by page: Send pricing page conversations to a sales channel and documentation page conversations to support, using the group argument on the pre-fill call.
• After hours AI coverage: Let the chatbot answer from your own site content overnight, then escalate to a human channel the moment someone is back online.
• Member aware support: Pass an authenticated member's name, email and plan into the chat so an agent never asks a paying customer to identify themselves again.
• Chat scoped to intent: Place the widget with a Code Embed element on high intent templates only, keeping blog and archive pages free of a third party script.

Set up GDPR consent on Webflow before the chat script reaches production, or pair it with Cookiebot so the widget only loads once a visitor has agreed to it. For the Webflow half of the work, connect the Webflow MCP server and manage content and custom code from your AI client while chat runs on top; it is included on every Site plan, the free Starter plan included.