Quickstart: drop Klariton on a page in 5 minutes.
Add the widget to one page. Point it at your Material. Watch the first conversation happen. See whether Klariton fits without leaving your dev environment.
Heads up. You'll need a Studio account, free during pilot, and one URL we can crawl. Email hello@klariton.com if you don't have an invite yet.
1 · Drop the script tag
Add this to the page where you want the touchpoint to appear. The widget self-mounts and respects your existing CSP. We ship with strict script-src compatibility.
<script src="https://cdn.klariton.com/widget.js"
data-customer="naturbohne"
data-touchpoint="brewing-advisor"
data-layer="shop"
async></script>2 · Point at your Material
From Studio, add a source. URLs crawl on a schedule. Files upload directly. We watch sources for changes and refresh retrieval automatically.
# in Studio → Material → Add source
type: "web"
url: "https://naturbohne.de/shop/*"
refresh: "daily"
visibility: "public"3 · Configure personas
Up to five per touchpoint. Each persona is a register, not a separate document. They all read from the same Material.
| Persona | Detection | Hand-off |
|---|---|---|
beginner | Default | None |
pro | From query terms | None |
b2b | From price intent | sales-webhook |
4 · Wire the lead webhook
When a persona switch triggers a hand-off, Klariton posts to your endpoint. You decide where it lands: HubSpot, Salesforce, Slack, or your own service.
POST /webhooks/klariton/lead
{
"persona": "b2b",
"score": 92,
"transcript_url": "https://studio.klariton.com/c/4429",
"signed_at": "2026-05-08T14:22:00Z"
}5 · Watch the funnel populate
Open Studio → Funnel. Sessions, engaged, questions asked, answered, outcome. The numbers stay small on day one. They get interesting by day three.
That's it. Next, read Concepts → Personas to design yours. Or open Trust → Data residency if your DPA officer is asking questions.