Turn your website into your receptionist's brain

Nobody reads the FAQs.

You and I both know it, and we are both still nice enough to answer the same question for the 48th time anyway.

The receptionist from the first post answers from its system prompt. Good enough to start. Not enough if you are an information-heavy business: a coach, a content creator, a lawyer, an architect, a financial advisor.

For that, your receptionist needs a knowledge base. There are two ways around this, depending on whether you have a website you are happy with or want a website that will make you happy.

The line of balance

First, the rule that decides what goes in at all.

What is needed to do business goes on the cloud. What is not needed to do business stays on your machine.

Whatever is on your website, whether pages, blogs, tutorials or newsletters, is public knowledge. The notes, ideas and reflections on your laptop are not, and they never touch the cloud. You slice the pie however you like, and the Second Brain OS respects the slice.

Structured vs unstructured

Then a second concept, inside the public domain. Everything your business knows falls into two categories.

Unstructured data is the explaining stuff: your pages, your blog posts, your policies. Things you explain. It has no fixed shape, and its value is in the wording.

Structured data is records: products, services, prices, employees. Things you list. Every entry has the same fields (a name, a description, a price), and its value is in being exact.

The two are handled differently on purpose, because they fail differently.

A slightly loose sentence is fine.

A price that is slightly loose is a refund conversation.

So ideally, the explaining stuff should go into a vector (loose text) database, and the exact stuff go into a schema (column, row) database.

Option one: Clone Yourself, $98

Clone Yourself switches on three tools:

• addToMyKnowledge puts content in.
• searchMyKnowledge reads it.
• deleteMyKnowledge takes it out again, behind a deliberate type-to-confirm step, because a knowledge base you cannot prune fills up with last year's prices.

The knowledge base itself is the unglamorous name for a vector store of your writing that an AI can search by meaning, not by keyword. From the moment searchMyKnowledge is enabled on your receptionist, a customer's question gets answered from what you actually wrote, not from the model's general training and guesses.

And it runs on every public channel your receptionist sits on. The clone of you on WhatsApp answers from the same knowledge as the one on your website. Push a post in from the terminal and the receptionist knows it on every channel the same minute.

How content gets in

You manage the tools from Claude Code, and the content is markdown: plain text with the lightest possible formatting marks, which happens to be the format AI models are most comfortable writing.

So the workflow is a conversation:

• A question keeps coming up in chats.
• You draft a proper answer in markdown, with Claude Code, in your voice.
• You push the file in with addToMyKnowledge.
• The receptionist answers from it, on every channel, the same day.

Already have pages and posts on your site? Same thing. Give it the specific link to a page or post on your website, let it pull the content. And the receptionist now agrees with your pricing page instead of contradicting it.

For the website you already have

Clone Yourself ships with a single HTML file that shows exactly how the receptionist sits on a page. You, or Claude Code, copy the pattern into WordPress, Squarespace, Wix or whatever you are on.

No rebuild. Your knowledge, scoped by you, answering as you, on the site you have got.

A lot of you will stop here, and that is correct. If all you need is "answer from what I have written on a website I already have", $98 is the whole job.

Where it stops

Three things the $98 does not do, and each one is a reason the second option exists.

The markdown file you pushed in teaches the receptionist, but it does not become a page or blog on your website. Your site is still edited the (manual) way it always was. And it's your job to keep the knowledge base for your AI Receptionist and the content on your website in sync and up to date.

Next, everything you push is stored in the unstructured database. And it is treated as the explaining stuff.

So your prices, services and team land in the knowledge base as loose sentences. Any risk that arises out of this, such as the AI Receptionist getting confused OR even quoting stale info lands on you. A knowledge base that swallows everything answers from noise. At $98, it's your job to mitigate this.

Option two: the SBOS Website Operator, $397

The Operator is the step where the website itself joins the system. It includes the three tools above and closes the three gaps. Remember the two piles from the line of balance: Clone Yourself only ever had the explaining pile. The Operator gives you both piles, and both your website and your receptionist read from them.

Markdown in, page out, receptionist taught

The website the Operator runs has a blog built in, on the simplest possible flow. Drop a markdown file into the content folder and it becomes a styled page on your site. Heck, get it to write the blog in the first place from you broken notes or transcripts of your voice notes.

Which means the workflow from option one gains a step, and the step is the whole point:

• A question keeps coming up in chats.
• You tell the Operator to write a post answering it, in your voice.
• The finished file publishes as a page on your website and syncs to the knowledge base.
• The receptionist answers from it, on every channel, the same day.

One piece of writing, teaching two surfaces. Write in the raw, publish in the pretty, nothing to keep in sync because there is only one file.

Dynamic updates: change it once, everywhere

Now the exact stuff. With the Operator, structured data goes through dedicated records, never into prose and never into code:

• Products, services and prices through addProducts and listProducts. One catalogue, upserted from the terminal.
• Your company details, the name, address, phone and bank details that proposals and confirmations need, through updateUserCompanyDetails and getUserCompanyDetails.
• Your team through addFireStoreEmployee and getFirestoreEmployeeRecord, one record per person.

The products section on your website renders from that catalogue live. The receptionist reads the same catalogue when a customer asks what something costs. The team page and the footer read the same employee and company records.

Change a price once and the pricing section on your site, the answer on WhatsApp, the answer on Instagram and the answer on Telegram all use the new price. Nobody edits code, nobody retrains anything, nobody updates the system prompt. "Call to confirm" pricing, may you rest in peace.

The Operator also decides what goes into the knowledge base and what stays out. Last year's prices, the internal note, the half-finished page. It knows the difference between prose worth searching and records that belong in the catalogue, and between public knowledge and things that should never reach a customer-facing answer. A receptionist that has been curated answers like someone who has actually been trained.

And notice what never happened in any of the above: nobody edited website code. The content layer and the code layer are deliberately separate. Updating what your business knows, its writing and its records, never requires touching how the website works. You buy the Operator once; your knowledge keeps moving without it.

The products post and the team post later in the series go through the records in detail.

The two side by side

Same knowledge, same receptionist. One is a tool you switch on. The other is an employee that runs the whole website around it, and the rest of what it does is the next post.

Choosing between the two, or unsure whether your current site is worth keeping? Book a call before you buy either.

A note on prices: every price in this series is the price inside its funnel, where each purchase unlocks the next. Bought on its own, outside the funnel, the same product can cost up to 30% more.

Next up: the SBOS Website Operator, the agent that makes the free website live.