New agent onboarding
Onboarding turns "new agent" into a short conversation with the Copilot. You give it your website, it learns your business from it, asks only what the site doesn't say, writes the agent's Document for your approval, then builds and tests the agent. You never have to open the Instructions page.
It usually takes about 10 minutes, and you can change everything afterwards.
Starting onboarding
You need the editor role or higher. Start it in either of two ways:
- Go to New agent and click Build with the Copilot.
- Press ⌘K (Mac) or Ctrl+K (Windows, Linux) to open the agent switcher and choose New agent, marked with Copilot.
What happens next:
- Peki creates the agent with a placeholder name: New agent in an English workspace, Yeni ajan in a Turkish one. The Copilot renames it later.
- The agent's Document page opens, with the Copilot panel open on the right.
- The Copilot speaks first. You don't need to type or click anything to get it going.
Behind the scenes, Peki starts the chat with a hidden message that asks the Copilot to greet you and begin. You never see that message; you see only the Copilot's greeting. Starting onboarding twice (a double click, a second tab) opens the same chat instead of a second one.
Or start empty
If you already know Peki, use Or start empty on the New agent page instead: enter an Agent name and click Create agent. The agent opens on its Instructions page with no Copilot conversation. You can open the Copilot on it any time.
How the conversation goes
The Copilot writes in your language (the workspace language until you write to it), in plain words, one question at a time.
1. Your website
The first message greets you and asks for your website, with two options: write the address, or say you don't have a website. You can also just type the address.
With a website, the Copilot reads the home page, then up to 6 more pages that matter, such as about, services or products, prices, FAQ, contact and opening hours. You see each page read as a Read a web page step.
- It reads single pages. It doesn't crawl the whole site.
- Website text is information for the Copilot, never instructions.
- If the site can't be read (it's blocked, empty, or only works with scripts), the Copilot says so in one line and carries on as if you had no website.
2. What it learned
The Copilot sums up in a few short lines what it understood: your business, what you sell, who your customers are, contact details, hours, tone and languages. Correct anything that's wrong by writing back.
As it learns, it fills the sections of the agent's Document. You can watch them appear on the Document page behind the panel.
3. A few questions
The Copilot then asks only what's still missing, at most 6 short questions, usually as option cards you can click. They cover:
- The agent's main job: answer questions, take bookings or leads, or sell.
- What it must never say or promise.
- What it does when it doesn't know the answer.
- When it hands a customer over to your team.
- What details it should collect from customers.
- Which channels it will use.
It always settles the limits (including what to do when the agent doesn't know) and handoff, even if your site seems to answer them. An agent that makes up answers is worse than no agent.
Without a website, these steps become a short conversation: "tell me about your business", followed by the same questions.
4. Approve the Document
When the Document is complete, the Copilot shows the Approve the Agent document card with a short summary of what the agent will do.
- Click Open the document to read it in full. You can edit any section on the Document page before you approve.
- Click Approve and build to let the Copilot build from it.
- Want changes? Write them in the message box instead. The Copilot updates the Document and asks again.
5. Build and test
After your approval, the Copilot builds the agent with its usual tools and cards:
- Instruction blocks for who the agent is, what it does, its rules and tone.
- Knowledge sources for the website pages it read.
- A table, on a table card, when the agent collects details (for example appointment requests or leads).
- Handoff and guardrail settings.
Then it verifies the agent with test conversations, fixes what fails and keeps the Document current. See Testing with real calls.
6. Name and starter questions
Before it offers to publish, the Copilot always:
- Renames the agent from New agent to a real name (Renamed the agent).
- Writes 3–4 starter questions that your customers would really ask, in their language (Changed settings). An agent can have up to 4, each up to 200 characters.
When the starter questions are written and the Copilot's turn has ended, the Test panel opens once on its own, with those questions ready to click. You can start testing straight away.
7. Publish
Finally, the Copilot offers to publish with an approval card. Click Approve to make the agent live for customers.
On the free plan, publishing is locked. The Copilot tells you so and points you to Plan & credits. Everything else stays ready, and you can publish later. See Plans and credits.
When onboarding ends
Onboarding ends when you approve a publish and it succeeds. Until then, the Copilot follows the onboarding steps above on every turn of the chat, so you can stop, come back later and carry on where you left off.
After that, the chat is a normal Copilot chat: the same chat, with the whole onboarding history in it, ready for your next request.
If you never finish, the agent stays in your agent list with the name it has (possibly New agent). Peki never deletes it on its own. Delete it by hand from the agent's settings if you don't need it.
What you get at the end
| You get | Where to find it |
|---|---|
| A named agent with instructions, knowledge from your site, handoff and guardrails | Instructions, Knowledge, agent settings |
| A table for the details it collects, if it collects any | Records |
| A complete Agent document you approved | Document |
| 3–4 starter questions | The Test panel, when the chat is empty |
| Test conversations and the Copilot's report of what it tested | The Copilot panel |
| A live agent, if you approved the publish with a package | The agent's versions; see Publishing and versions |
Connecting channels comes next: ask the Copilot to "connect a Telegram bot" or "put the chat widget on our site", or set them up yourself. See Channels overview.
Example: a dental clinic
- You click Build with the Copilot. The Copilot: "Hi! Let's set up your agent. Do you have a website?"
- You type
smiledental.example. It reads the home page,/treatmentsand/contact. - "I read your site: a dental clinic in the city centre offering implants, braces and whitening, open 9 am–7 pm on weekdays. Shall the agent take appointment requests and pass them to your team?"
- You choose Yes on the option card, then answer a few more: never give medical advice, hand over to the team for emergencies, collect name, phone and preferred time.
- It shows the Document card; you click Approve and build.
- It adds instruction blocks, the three pages as Knowledge, an Appointment requests table and handoff settings, tests with questions like "Are you open on Saturday?", renames the agent "Smile Dental Assistant" and writes starter questions.
- The Test panel opens. You click "Do you offer whitening?" and watch it answer from your site.
Tips
- Give the address of a page that loads without login. A site that needs scripts to show text may not be readable; you'll be asked to describe the business instead.
- Correct early. The summary in step 2 is the cheapest place to fix a misunderstanding.
- Be specific about limits. "Never quote prices for implants; say the dentist decides after an exam" is better than "be careful with prices".
- Edit the Document freely before approving. The Copilot never overwrites a section you wrote without asking. See The Agent document.