How to Add an AI Agent to a Framer Site
Framer ships AI agents that sit on a published site and answer visitor questions, scoped to content you choose. You pick which pages the agent can read, set its tone, and publish. Setup takes about ten minutes on a site that already exists.
It is not a support desk bot. It is a site guide: it explains what is on your site and points people to the right page. Set expectations that way and it works. Expect it to answer questions about your product’s internals and it will improvise.
What are Framer AI agents?
A Framer AI agent is a component that answers questions in a chat interface on your site. Its knowledge comes from pages you grant it access to, and its answers link back to those pages.
Key characteristics:
- Available on sites published with Framer, not exported HTML.
- Knowledge is limited to selected CMS collections and pages.
- Answers can include links to specific pages or CMS items.
- Runs on Framer’s infrastructure, so no external bot service to wire up.
- Counts toward your site plan’s agent usage allowances.
Because it reads your pages, quality is a direct function of how clearly your pages are written. A vague product page produces a vague agent.
How do you set up an agent on a Framer site?
- Open the project and find the AI agent option in the site settings panel.
- Choose the knowledge scope: all pages, specific pages, or CMS collections. Start with three or four core pages.
- Write the agent instructions: what it is, what it may answer, and what it must hand off.
- Set the greeting. One sentence explaining what the agent can help with outperforms a friendly noise opener.
- Style it to match your brand: colour, corner radius, placement.
- Publish and test on the live domain, not the preview.
Step six matters because CMS content and page visibility can differ between preview and production. Testing in preview gives false confidence.
What should the agent instructions say?
Short, restrictive, and specific to your pages:
You help visitors understand our product plans and features. Answer only from the pages provided. If a question is about billing, account access, or anything not on those pages, tell the visitor to contact support and give the support link.
Two things this does: it prevents invented pricing, and it creates a clean handoff path instead of a dead end.
Add a sentence about tone if your brand voice is unusual. Skip personality paragraphs; they eat prompt space and visitors do not notice them.
How good are the answers in practice?
Good on navigational questions: “do you have a free plan,” “where are the API docs,” “what does the enterprise tier include.” The agent finds the page and quotes it.
Weaker on anything comparative or numeric across pages. Ask “which plan is cheapest for 20 seats” and it may quote plan prices without doing the multiplication. For pricing questions, put an explicit comparison table on a page rather than hoping the agent synthesises one.
Also expect generic answers for questions your pages only imply. If your competitor comparison lives in a blog post you did not include in scope, the agent will not find it.
What are the practical limits?
- No file uploads or PDF sources; pages and CMS content only.
- No access to account data, so it cannot answer “where is my order.”
- Usage tied to your Framer plan, with agent conversations counted.
- No multi-language knowledge separation: mixed-language pages can muddy answers.
These are not complaints so much as boundaries. Framer’s agent is best understood as a smarter site search with a conversational front end.
Who should use it and who should skip it
Use it for a marketing site with a handful of well-written product and pricing pages, where visitors bounce between pages looking for a spec. It measurably reduces “where do I find X” emails.
Skip it if your site is small enough that navigation works fine, if you sell a complex product requiring real support triage, or if your content lives mostly in a helpdesk outside Framer. In those cases a dedicated support bot reads more sources.
One more caveat: if you redesign pages often, agent answers change with them, including the wrong ones. Re-test after each major page rewrite.
Quick Summary
- Framer AI agents answer visitor questions using pages and CMS content you scope in.
- Setup is about ten minutes: choose knowledge pages, write restrictive instructions, publish.
- They excel at navigational and feature questions and struggle with cross-page numeric comparisons.
- No PDFs, no account data; usage counts against your site plan.
- Best for marketing sites with clear product pages; not a replacement for support triage.
