Quickstart

From signup to a live agent answering questions on your site in under five minutes. Each step is sized so you can stop and pick it up later.

1. Create an account

Visit the home page and click Get started. Pitchbar uses Laravel Fortify for auth, so you'll get standard email + password registration, plus optional 2FA in your account settings later.

On signup we auto-create your first workspace and a draft agent named after your company domain. If you entered a website URL during signup, that domain is also added to the agent's allowed origins so the embed works without extra setup.

2. Run the onboarding wizard

Land on /onboarding. The wizard walks you through:

1. Confirm your website URL. The agent will learn from this site.
2. Auto-discover crawlable pages. We probe your sitemap and a handful of common paths (/about, /pricing, /faq, /docs, etc.).
3. Pick which pages to ingest. Each page becomes a knowledge source — text gets chunked and embedded into the vector store.
4. Watch them flip to "indexed". Polls every few seconds. Most sites finish in under a minute.
5. Copy the embed snippet. One line of HTML.

3. Embed the widget

Paste this just before </body> on any page where you want the agent to appear. Replace YOUR_AGENT_ID with the value the onboarding wizard shows you (also visible on every Agent's Settings page).

<script
    src="https://your-app.test/widget/widget.js"
    data-agent-id="YOUR_AGENT_ID"
    async></script>

4. Publish the agent

The widget also loads in draft mode locally so you can test, but it won't answer real visitors until the agent is published. From the agent's overview page, click Publish — this snapshots the current persona, prompt, theme, and behavior rules into a versioned agent_version row that the runtime reads.

5. Open the inbox

Head to /app/inbox. As soon as your first visitor sends a message, you'll see it appear live. From there you can read transcripts, jump in as a human operator, and capture leads.

What's next?

Choosing which pages the agent learns from

On the first setup screen, under the website address, you pick how the starting knowledge is gathered:

• Show me what you found — the default. We scan, then you tick the pages before anything is added.
• Let Blengi choose — we scan and add the most useful pages straight away, so you reach a working agent without a decision. Nothing is hidden: the pages appear in Sources, and you can add or remove any of them afterwards.
• I'll enter them myself — skip the scan and paste the exact addresses, one per line. Duplicates are ignored and a bare example.com/about is understood as https://.

What "scan" means, precisely: we read your sitemap.xml (including any listed in robots.txt) and, when there is no sitemap, the links on your homepage. We do not walk the whole site. Anything missed can be added later, and pages a visitor opens are picked up automatically when that setting is on.

A page that cannot be fetched — a typo, a redirect loop, a login wall — is recorded as a failed source and skipped. The rest of the batch is added regardless, and the nightly retry sweep picks failed sources back up.

Talking to your agent before you install it

You do not have to put the snippet on your site to find out whether the agent works. As soon as the first page finishes indexing, the last setup screen shows your real widget and invites you to ask it something — while the remaining pages are still being read in the background.

It is the actual widget, not a demonstration: the same code, the same look, answering from the pages it has read so far. Nothing you ask it there counts as a conversation, a lead, or a content gap.

The install snippet sits underneath. Copy it when you are happy with what you see, rather than pasting code and hoping.