Add the Allinaa chatbot to a Softr site

Softr builds a real website rather than an embedded frame, which means a chat widget works normally - one line of custom code, added once for the whole site. The question worth more thought on a Softr site is which pages it should appear on, because many Softr sites have a public front and a members' area behind a login.

Before you start: copy your embed code

Create your account at bot.allinaa.com/start using your site's address. The setup wizard reads your own public pages and drafts the knowledge from them so you can edit and approve it. Step 5, "Install", shows your line with a copy button:

<script src="https://bot.allinaa.com/widget.js" data-bot-id="your-bot-id" defer></script>

Where it goes: the site's custom code

Softr has a custom-code setting that applies to the whole published site, with separate places for code in the document head and code at the end of the body. The chat line goes in the end of body one, so the page renders before the widget loads. Paste it, save, and publish - a change to custom code reaches visitors only once the site is published again, which is the most common reason somebody thinks the paste did not work.

Settings move between versions of any builder, so if the menu does not look like this, search Softr's own help for "custom code" rather than trusting a screenshot on a vendor page. The line itself does not change wherever it ends up.

Members' areas: decide before you publish

A lot of Softr sites are a public marketing front plus a signed-in portal built on your data. A public chat assistant belongs on the first and usually not on the second, for a reason that is worth being clear about: a signed-in member's questions are nearly always about their own records, which the assistant has no access to. It cannot see your Airtable, your Google Sheet or whatever the site is built on, and it should not appear to.

If Softr's custom code applies everywhere and you want the widget only on the public pages, the honest options are to accept it site-wide and write a clear "I cannot see your account" sentence into the knowledge, or to keep the assistant on a public sub-site. Either is defensible; what is not is letting a member ask about their own data and get a confident, wrong answer. The assistant's page reading already skips private path segments such as account and portal paths, so it will not read a member's page for context even where the bubble is present.

Do not use an embed block for this

Softr has blocks that let you drop custom HTML into a page, and people reach for one here. It works - on that one page, inside the flow of the content. A chat widget needs to be site-wide and floating: visitors from search land on deep pages, not on your home page, and a chat confined to a box in the middle of a page is not a chat widget in any useful sense. Use the site-wide custom code setting instead.

What to write in the knowledge for this kind of site

Softr sites are often a product in themselves - a directory, a portal, a marketplace - so the questions are about the product rather than about a shop. Write what the thing is, who it is for, what membership costs if anything, what a member can do, how to sign up, and what you do about data and cancellation. Then write the boundary: the assistant explains the product and does not act inside anybody's account. See what to put in the knowledge.

Check it worked

1. Publish the site, then open it in a private window - an editor preview can behave differently.
2. Check the bubble on the home page and on a deep public page.
3. Ask the assistant something about the page you are on.
4. If you have a members' area, sign in and ask an account question. The answer should decline and offer a person.

See install troubleshooting and the launch checklist.