A single URL starts the setup. The customer does not begin with a blank bot builder.
How it works
Simple for the customer, rigorous behind the scenes.
Customers share a website, approve the selected sources, test the agent, and install one script. Behind that, Atithya classifies content, excludes noisy pages, builds scope, and tests answer quality.
Managed setup, productized
Customer sees the simple path. Atithya runs the operating layer.
Customer path
Eight clear steps from website to live agent.
Core website pages are shortlisted while noisy content libraries stay out by default.
The customer sees what will train the agent before any knowledge is generated.
Approved pages become structured product, company, policy, security, and pricing context.
Launcher copy, colors, starter questions, and lead CTA language are tuned with defaults intact.
The agent is reviewed on desktop and mobile before the customer installs anything.
A domain-controlled script publishes the reviewed agent onto the approved website.
The workspace shows buyer questions, lead quality, unanswered topics, and source gaps.
Operating layer
The work behind the calm setup screen.
Discover likely homepage, product, pricing, company, security, policy, and press pages.
Keep SEO content and long-form resource libraries out unless explicitly approved.
Route answers to the right knowledge category instead of searching one noisy pile.
Turn selected content into compact, source-aware context for the agent.
Define what is in scope, what should be redirected, and how sensitive claims are framed.
Test pricing, competitor, security, implementation, and out-of-scope questions before publish.
Review answers for accuracy, tone, usefulness, guardrail fit, and conversation movement.
The live script is released only after source, preview, and answer-quality checks are passed.
What matters
The customer never starts with a blank bot builder.
Atithya guides the setup with opinionated defaults so launch depends on approval, not endless configuration.
Shows the customer path beside the managed operating layer so setup feels simple without hiding quality work.
The buyer understands source selection, approval, preview, install, and post-launch monitoring before committing.
- Website intake
- Source approval
- QA questions
- One-script install
Customer-facing flow
Share the website, review selected pages, approve source use, customize the widget, test key questions, and publish.
Back-end intelligence
The platform crawls, classifies, excludes blogs by default, builds category knowledge, and creates evaluation prompts.
Preview before install
Desktop and mobile previews show the widget sitting on the customer's website before the script goes live.
QA before publish
Pricing, competitor, compliance, implementation, and out-of-scope questions are tested before launch.
Workflow
Customer path
The process should feel like a guided setup call translated into a clean product experience.
- Share website
- Review selected pages
- Approve knowledge
- Preview on homepage
- Edit widget appearance
- Test questions
- Install script
- Monitor leads
Product principle
The managed-service advantage
The customer gets the confidence of a service and the control of a SaaS workspace. That is the wedge for the first paid version.