What to call things
Use BrainSite for the public page, Agent for the visitor-facing AI, Knowledge for approved facts and sources, Agent Inbox for conversations and leads, and Sales Agent for qualification, booking, and suggested actions.
BrainSite is a public AI agent built from a website or social media profile. This support manual explains how to create one, add approved knowledge, manage conversation context, qualify visitors, configure booking and payments, review leads, and connect supported channels.
Last materially updated July 30, 2026.

BrainSite is your public AI profile: a shareable page with an agent that answers questions, learns from approved knowledge, qualifies visitors, and helps move people toward the right next step.
Use BrainSite for the public page, Agent for the visitor-facing AI, Knowledge for approved facts and sources, Agent Inbox for conversations and leads, and Sales Agent for qualification, booking, and suggested actions.
Create or scan your BrainSite, review the Agent page, add your logo and bio, set brand colors, add social links, add knowledge sources, then test the public chat.
Dashboard shows status. Agent controls the public page. Knowledge controls answers. Agent Inbox stores conversations. Sales Agent controls qualification and booking. Account manages owner details and privacy.
Copy your public BrainSite URL from the Agent page, paste it into the website or link field on Instagram, TikTok, X, LinkedIn, YouTube, or your link-in-bio tool, then test it from a signed-out browser.
A unique URL and QR-ready profile that visitors can open, scan, share, and talk to.
Visitors ask questions and the agent answers from approved business context and sources.
Approved source material, corrections, and teaching become reusable business memory.
Review conversations, captured contacts, qualification status, and follow-up opportunities.
Start with a smart public profile or scan an existing website to generate a draft agent.
Your public page can reflect your business identity, visual style, and preferred contact channels.
BrainSite answers best when its knowledge is source-grounded and reviewed. Read the governed learning method for the distinction between approved knowledge, pending proposals, and conversation context.
Read how BrainSite learnsConversation Memory preserves the minimum useful visitor and conversation context. It remains separate from approved Knowledge Memory.
The inbox turns public chat activity into a reviewable lead workflow.
BrainSite runs on three separated layers. The public agent only answers from Knowledge Memory the owner has reviewed and approved, kept apart from Conversation Memory, which holds just enough context to keep one exchange coherent. Between the two sits a set of deterministic safety rules, fixed checks that run the same way every time rather than depending on model judgment. Owner workflows, including Agent Inbox and the knowledge review queue, sit outside that runtime, so approving what the agent knows is a separate step from the agent using it.
A branded public profile or business page with links, contact channels, QR sharing, and a conversational agent.
A governed runtime that combines approved Knowledge Memory, bounded Conversation Memory, public-source context, and deterministic safety rules.
Dashboard, Agent Inbox, knowledge review, identity controls, integrations, usage, and deployment tools keep the owner in control.
Paid plans use soft conversation limits: your agent keeps responding, and overages apply according to the plan.
BrainSite can support web chat, Telegram, SMS, WhatsApp, voice/call workflows, email notifications, and seller onboarding depending on configuration.
Legacy Growth-plan accounts can add a floating BrainSite chat widget to an external website with one script tag.
Owners can create scoped API keys for one BrainSite deployment and use REST or the local MCP bridge.
Read API markdownBrainSite appeared in 3 of 10 ChatGPT Search answers and 0 of 10 answers tested in Perplexity, Gemini, Google AI Overviews, and Microsoft Copilot. The largest problem was entity recognition: four platforms described the wrong product or could not connect BrainSite with its official website. Test completed July 29, 2026, published July 30, 2026.
Method: the same 10 queries were entered manually in each platform on July 29, 2026, and checked for a BrainSite mention, a clickable citation, description accuracy, and named competitors. This is a point-in-time observation, not a controlled ranking experiment; results can change as platforms update their indexes and retrieval systems. The next test is planned once the category page, comparison pages, and qualified third-party listings have been indexed.
Use a normal public `https://` website. Localhost, private network, internal, and unsafe redirect targets are blocked.
Add source material, approve pending knowledge, and test again. If provider keys or usage limits are missing, fallback behavior may appear.
Check the public slug, deployment status, publish status, and whether the BrainSite is live or published.
Confirm the file type is supported and the account has storage available. Knowledge uploads and seller document uploads have different limits.
Confirm the Stripe checkout completed. If support is investigating, they should check webhook delivery and plan metadata.
Confirm the channel is connected, webhook URLs are configured, and the owner or deployment mapping exists.
This public support page is generated from the BrainSite knowledgebase. Internal support and admin runbooks stay in the private KB so public support remains focused on user setup and troubleshooting.
Create a BrainSite