Skip to content
Klariton Docs

1. Getting Started

This chapter gets you from an empty organization to your first live FAQ touchpoint. The goal is a small, reliable pilot, not a full catalog rollout.

What Klariton Is

Section titled “What Klariton Is”

Klariton is an answer layer for your existing shop or SaaS site. You keep your current platform. Klariton adds governed answers on top of it: source-backed, persona-aware and displayed in your brand.

Start with one product or product group, one persona and one FAQ touchpoint. Once that works, scale to more products, languages, personas and touchpoints.

Before You Start

Section titled “Before You Start”

Prepare:

  • A pilot product or product group.
  • One or more reliable sources: Shopify product data, a product sheet, an official FAQ, a guide or a product URL.
  • The domain or staging domain where the widget will run.
  • A person who owns review and publication.

Do not start by importing every document you own. Poor or conflicting sources create more review work later.

Quickstart

Section titled “Quickstart”

1. Create or select your organization

Section titled “1. Create or select your organization”

Your organization holds brand identity, domains, billing, members, settings and all content. Configure at least:

  • Organization name and slug.
  • Production domain.
  • Default locale and timezone.
  • Brand basics.

2. Connect product data

Section titled “2. Connect product data”

Use Shopify if available. Otherwise use CSV/API or manually maintained products. Product data gives Klariton structured facts: name, description, availability, properties, product type and metadata.

3. Add material

Section titled “3. Add material”

Upload or crawl the source material for your pilot. Use documents and URLs that you would trust publicly.

Wait until processing is complete before generating BIQs. If material is still processing, Klariton may generate with incomplete context.

4. Create a persona

Section titled “4. Create a persona”

Create one clear persona for the pilot. Good personas differ by questions, knowledge level and buying criteria, not just by campaign name.

5. Create a FAQ touchpoint

Section titled “5. Create a FAQ touchpoint”

Place the touchpoint in the tree: organization -> layer -> folder -> touchpoint. Use FAQ for the first launch because it is live, crawlable and easy to review.

6. Generate BIQs

Section titled “6. Generate BIQs”

Generate from material for the first batch. Review source evidence and confidence levels before publishing.

7. Review and publish

Section titled “7. Review and publish”

Only published BIQs appear in live touchpoints. Generation is not publication. Review question, answer, source, confidence, brand voice and SafeGuard findings.

8. Embed the touchpoint

Section titled “8. Embed the touchpoint”

Copy the embed snippet from the Studio. Do not assemble it manually. Current snippets use org-slug, touchpoint-slug, mode and data-worker-url.

Go-Live Checklist

Section titled “Go-Live Checklist”

Before going public:

  • The touchpoint status is LIVE.
  • At least one BIQ is published.
  • Domain/origin is allowed.
  • The snippet was copied from the Studio.
  • The page loads the widget bundle with status 200.
  • The touchpoint request returns 200.
  • INFERRED or unsupported answers are not published accidentally.
  • One owner is responsible for Questions Inbox, SafeGuard and material gaps.

After Launch

Section titled “After Launch”

Operate the loop: