Add the Allinaa chatbot to a Kajabi site

A Kajabi site has two halves with two different audiences: the public marketing pages where people decide whether to buy a course, and the member area where buyers take it. The chat assistant belongs firmly on the first, and this guide is mostly about why, because getting that wrong is the one way to make it worse than nothing.

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: your site's code settings

Kajabi has a settings area where you can add code to the whole site, with separate fields for the document head and the end of the body. The chat line goes in the end of body field, so the page renders before the widget loads. Save, and then view the live site rather than the editor preview - a builder's preview often loads a different set of scripts.

Settings move between versions of any platform, so if the field is not where this describes, search Kajabi's own help for site-wide custom code. The line is the same wherever it is pasted.

Keep it out of the course area

Two separate reasons, and both matter.

First, it cannot help there. A student's questions are about their own enrolment: which module they are on, whether their payment went through, why a video will not play, when the next cohort starts for them. The assistant has no access to your Kajabi data and cannot answer any of those - so the best it can do in a member area is decline politely, which is a poor experience for somebody who has already paid.

Second, it is a distraction in the wrong place. Somebody watching a lesson does not need a chat bubble in the corner, and on a phone that bubble is over the video controls. If Kajabi's site-wide code applies to the member area as well, write a clear sentence into the knowledge for signed-in questions - what your support route actually is, in your own words - and make sure that is the first thing the assistant says. The page reading already skips private path segments such as account and member paths, so it will not read a student's page for context.

What a course or coaching business should answer

The public side is where this earns its keep, because course buyers ask a very consistent set of questions before they pay:

• "How long is it, and how much time a week do I need?"
• "Is it self-paced or are there live calls, and in which time zone?"
• "How long do I keep access?"
• "Is there a payment plan?"
• "What is your refund policy?"
• "Is this suitable for a complete beginner?"
• "Do I get a certificate, and is it recognised anywhere?"

Write every one of them, in your own words, including the uncomfortable ones. The refund policy especially: stating it plainly before the sale prevents the dispute afterwards. On the certificate question, say exactly what you issue and what it is not - an overclaim there is the kind that attracts complaints.

One boundary to set deliberately: the assistant should not promise an outcome. "You will earn X" or "you will be job-ready" is not something a chatbot should say on your behalf, and the published rules of this site would refuse it anyway. See writing the way your chatbot should speak.

The time-zone question needs care

If you run live calls, people will ask what time that is for them. The assistant does not know the current date or time and cannot convert anything, so write the schedule with the time zone named explicitly and let the visitor do the conversion. A chatbot that guesses a local time is worse than one that states the zone. See what a chatbot cannot do.

Check it worked

1. Open the live site in a private window, not the editor preview.
2. Check the bubble on a sales page and on a blog post.
3. Ask it your refund policy and read the answer word for word.
4. Sign in as a student and ask an enrolment question; the answer should decline and give your real support route.

See install troubleshooting and the launch checklist.