From an empty bot to a finished setup — in conversation.
The Builder is not a wizard with twelve mandatory fields. You type what your bot should be able to do, upload sources via drag-and-drop and watch your bot page take shape in real time on the right. zep translates your answers into a system prompt, branding tokens and an indexer plan.
Three steps, one clear workflow.
No plugin, no wizard with required fields. You work at your own pace and jump between the steps — everything syncs back to the dashboard automatically.
- 1. Briefing
The builder bot asks — you answer in your own words.
zep asks four context questions: who should use the bot, which language, which taboo topics, which style. Answer in two sentences, done.
- 2. Sources
Hook up Notion, PDF, URL or a marketplace pack.
You connect your knowledge sources via OAuth or drag-and-drop. If you are missing content, you activate a ready-made pack — the bot is useful right away.
- 3. Live look
Branding & greeting in the real-time preview.
Color picker, logo upload, four suggested questions — the bot page renders live next to the Builder. There is no save button, because everything is persisted automatically.
Three pipelines, one conversation.
While you type with zep, three steps run in parallel in the background — you do not have to deal with any of them, but it is good to know what happens:
- System prompt generation. Your answers land in a template that assembles persona, allowed topics, taboos and answer format. We use our own meta-LLM that translates your words into bot behavior.
- Indexing plan. Each source is checked for size, format and language. Notion pages are pulled in via OAuth, PDFs are chunked, URLs are crawled. Embeddings land in a tenant-isolated vector store.
- Branding pipeline. A logo upload automatically generates favicon sets, the color picker writes CSS variables, and the greeting is rendered together with your bot style — no manual build, no reload.
Typical use cases we see every day.
Solo founder who wants to go live fast
Instead of building a SaaS stack: connect Notion, pick a branding color, done. The bot subdomain is up in 4 minutes.
Coach with course material
Upload PDFs and scripts, zep reads the module order automatically and answers learner questions with chapter references.
Online shop without a dev team
Shipping policy as a URL, FAQ Notion page as a source. Set the style via the builder bot — the service bot is ready to go immediately.
Club or community
Forum export plus Discord server. zep becomes the knowledge anchor that gives new members quick answers instead of long threads.
Marketplace quick start
No data of your own? Activate a travel pack, coaching pack or coding pack — you build your style around it, without an empty start.
Multi-bot setup
Pro user with three bot personas: the Builder copies setups, you only swap the knowledge base, branding stays consistent.
FAQ.
Do I have to use the Builder to create a bot?
No. Power users can create the bot directly in the dashboard and enter prompt, sources and branding manually. The Builder is the fast option — both paths lead to the same result and you can switch at any time.
What if the Builder does not match my wording?
You can open the system prompt generated by zep in the dashboard at any time, adjust it and save it again. The Builder is just the starting point — fine-tuning happens in the dashboard or the Training tab.
How many bots can I create in the Builder at once?
Free: one bot. Plus: three bots. Pro: ten bots. Bots have their own knowledge sources, styles and URLs, but you can carry over builder settings via 'Duplicate setup'.
Does the Builder save my input automatically?
Yes. As soon as you click 'Publish', everything is persistent. In the Builder itself you work on a draft that is saved with every breath — close the browser, continue later, no data loss.
Open the Builder and start the setup stopwatch.
The Free plan is enough for your first bot. If you do not have your first answer within 5 minutes — write to us and we will go through it together with you.
