Set Up the Receptionist That Answers From What You Already Wrote
You have bought the Clone Yourself Coach, so the agent is on your account and ready to run.
By the end of this guide, your AI receptionist answers customers in your own words, from writing you have already done, on every channel you run — and it is embedded on the website you already have, which you will not be rebuilding.
About an hour for the first useful pass. It gets better in small passes after that, which is the point.
The problem this solves
Your receptionist is live and it is guessing.
Not badly, necessarily — but generically. It does not know that you do not take same-day bookings, that your onboarding takes two weeks, or the specific reason you stopped offering the cheap tier. A customer asks, and it produces something plausible that is not quite what you would have said.
Meanwhile you have answered every one of those questions before. In a blog post. On your about page. In the same WhatsApp reply you have typed forty times this year. The answers exist and are scattered across places no customer will ever assemble.
That is the gap this closes. Not writing a knowledge base — collecting one you already wrote.
What you are actually building
A curated knowledge base, not an archive. Only public explaining material goes up. The agent proposes, you approve, nothing moves without your yes.
One source across every channel. Add an answer once; it serves your website chat, WhatsApp, Instagram and Telegram. No per-channel copies.
A pruning habit. Removing the stale paragraph matters as much as adding the good one.
The receptionist on your existing site. One HTML file, copied into whatever builder you already use.
Before you start
You need your website and your SBOS AI receptionist — both of which you already have as an SBOS user. Nothing else to install.
Then start the agent:
/secondbrainos:agent_clone_yourself_coach
Step 1 — Find the gap before you fill it
Do not start by uploading things.
Start by asking the agent what your receptionist would say to your three most common customer questions. It searches what is in the knowledge base today and shows you the answers as they currently stand.
This takes five minutes and reorders everything that follows. You will usually find one question answered well, one answered vaguely, and one answered confidently and wrongly. That third one is your most valuable find of the day.
What you get: a work list that is far shorter than “import my website”.
Step 2 — The line of balance
Before anything is pushed, the agent applies one rule: what is needed to do business goes to the cloud; everything else stays on your machine.
In practice, in belongs:
- Pages and posts that explain what you do
- Tutorials and how-to content
- Newsletters worth quoting
- FAQ answers you have already written
And out stays: internal notes, drafts, client-specific material, anything you would not put on a public page. Your knowledge base is answering strangers. Treat every entry as public, because functionally it is.
The agent tells you which files or URLs it intends to add and why, then waits. Nothing is pushed because it happened to be in the folder.
Step 3 — Push, in small passes
You can add markdown files from your machine, or point the agent at specific URLs on your own website and have it pull those pages in directly. Your about page and your three best explanatory posts are usually a stronger first pass than anything you would write fresh.
Resist the big import. Thirty scraped pages give you a knowledge base you cannot reason about — and when an answer comes out wrong you will have no idea which of the thirty caused it. Three good answers you can name beat thirty you cannot.
Checkpoint: after each small push, go back to Step 1. Ask what the receptionist now says to those same three questions. You are watching an answer improve, which tells you whether the thing you just added actually did anything.
Step 4 — Prune
A knowledge base degrades by accumulation, not by absence.
Two entries that contradict each other are worse than one that is merely incomplete, because the receptionist will confidently pick one. Duplicates, superseded posts and last year’s process are all worth removing.
Deletion is deliberately slow. The agent shows you exactly what will be removed and asks you to type the entry name back before it acts. That friction is intentional — this is the one operation here you cannot undo.
Step 5 — Turn repeated questions into real answers
Watch what keeps coming up in your actual chats.
When the same question appears for the third time, that is not a gap in your receptionist’s reasoning — it is a gap in your writing. Have the agent help you draft a proper answer in your own voice, as markdown, then push it.
Do this for a few weeks and the most-asked questions in your business stop being guessed at, because you finally answered each of them once, properly. This is the loop that does the real work, and it costs a few minutes a week.
Step 6 — Put it on your site
A single HTML file embeds the receptionist chat. The agent walks you through it and how to copy the pattern into WordPress, Squarespace, Wix or any other builder.
It will not rebuild your website and it will not ask you to move it. The reference implementation is public if you or your developer want to read it first.
You can see the finished result running at anycrmtoaiagent.com.
The limit worth understanding
Prices, services, team members and company details are records, not explaining text.
This agent stores everything as unstructured text. That is exactly right for “how does your onboarding work” and exactly wrong for “what does it cost”.
A price in a knowledge base is a sentence. Sentences do not update when you change your pricing. Your receptionist will keep quoting the old number with total confidence, and you will find out when a customer holds you to it — which is a refund conversation, not a support ticket.
So keep those in sync yourself; that responsibility stays with you here. If you want records your website and receptionist both read live, so one change updates everywhere, that is the SBOS Website Operator — a different tool for a different shape of data, not a workaround to improvise with markdown.
What you can do now
Ask your receptionist something only you would know the answer to. It answers the way you would.
More usefully: the next time a customer asks something and the reply is not quite right, you have a fix that takes four minutes and holds permanently.
What this does not do
It does not manage structured records — see above, and the Website Operator.
It does not build or redesign your website. It embeds a chat onto the one you have.
And it does not push anything unasked. Every addition and every deletion waits for you.
What is next
Blog 3 in this series covers the SBOS Website Operator: live records your website and your receptionist both read, so changing a price once changes it everywhere.
