Framer's fast rise among freelancers and small agencies means a lot of client sites launch fast and stay lean on maintenance afterward. A Framer chatbot trained on the site's own pages gives visitors a way to get real answers without anyone rebuilding the site to add a support form. This guide covers training the bot and Framer's four custom-code slots, only one of which is the right place for a widget.
Confirm the site is on a paid plan
Framer's free plan doesn't expose custom head/body code. That's gated behind the Basic plan or higher. If the site is still on Framer's free tier, upgrade before the Custom Code section will do anything.
No Framer plugin needed
Askvo isn't a Framer plugin. The bot runs on Askvo's servers; the site loads one script and a custom element through Framer's built-in Custom Code feature, the same mechanism used for analytics tags, not a marketplace install. Same snippet as every other platform. See what an AI chatbot for your website actually does for the bigger picture.
Step 1: Train the bot on your content
- Create a free Askvo account. One chatbot on the Free plan, no card required.
- Paste your published Framer site's URL. The crawler reads your live pages and builds the bot's knowledge base. Re-crawl after publishing changes.
- Add what it can't see. A linked PDF, pricing details in an image, seasonal notes. Upload documents or add Q&A pairs directly; see how to train a chatbot on your own data.
- Test it in the dashboard first. Strict mode keeps it answering only from your content, and it says so honestly when it doesn't know.
Step 2: Get your embed snippet
Copy the snippet from your bot's install page in the Askvo dashboard. Match the widget color to your site first, and on Business or Agency, decide on lead capture.
Step 3: Paste it into the right custom-code slot
- In the Framer app, open Site Settings from the left sidebar.
- Find the Custom Code section under General.
- You'll see four slots: Start of <head>, End of <head>, Start of <body>, and End of <body>. Paste the Askvo snippet into End of <body>, the standard spot for a chat widget, so it loads after the rest of the page.
- Make sure you're editing under Site Settings, not an individual page's settings. The site-level slot is what applies to every page in the project.
- Publish the site for the change to go live.
Step 4: Verify before you call it done
- Confirm you published. Custom code changes don't go live until publish, same as any other Framer edit.
- Check multiple pages, including any CMS-driven pages if you're using Framer's CMS.
- Ask it a real question and confirm the reply streams in with a citation.
- Test "talk to a human" and confirm the conversation reaches your Askvo dashboard.
- Ask something it can't know and confirm it declines instead of guessing.
Keeping answers accurate as your site changes
Re-crawl after publishing content changes. Check the Unanswered Questions report to spot gaps. If lead capture matters, read the chatbot lead generation guide. Compare plans on pricing.
Frequently asked questions
Which of the four custom code slots should the chatbot go in?
End of <body>, under Site Settings. That's the standard placement for chat widgets: after the page content, and applied site-wide rather than to a single page.
Do I need a paid Framer plan?
Yes. Framer's free plan doesn't include custom head/body code, so you'll need at least the Basic plan.
Site Settings vs. Page Settings: does it matter?
Yes. Page Settings custom code only runs on that specific page. A chat widget needs Site Settings so it appears everywhere.
What happens if the bot doesn't know an answer?
It says so using a fallback message you control, and logs the question so you know what to add to the site next.