From documentation to clarity in minutes
Sol Helps turns your documentation into an on-brand assistant, then turns repeated customer questions into Customer Confusion Insights — a prioritised view of where understanding breaks down, grounded in real conversations.
Prefer a concrete example?View the demo·How teams use Sol Helps
What happens after signup
Create assistant → add knowledge → test in chat → embed
- 01
Sign up and create an assistant
Set tone and guardrails so answers stay on-brand and conservative.
- 02
Connect content (files or URLs)
Upload docs or crawl pages. Choose what gets indexed.
- 03
Test in chat
Ask 2–3 realistic questions before customers see it.
- 04
Embed the widget
Add one script tag to your docs or product. Then watch signals appear as questions repeat.
No credit card. No sales call required.
Core value
Built for real customer questions
The goal isn’t more chat. It’s clearer decisions: turn real questions into patterns your team can act on, without pretending certainty.
Evidence-led clarity layer
Sol Helps turns eligible conversations into themes and friction signals, so teams can reason about why users get stuck using real question evidence.
Live in minutes
Drop in one script snippet and go live. No tagging, event schemas, or analytics pipelines required.
On-brand by default
Tune tone, style, safety rails, and fallback behaviour so your assistant feels like part of your product—conservative and consistent by default.
Works with your stack
Embed Sol Helps in static sites, React, Angular, or your docs platform. Start with one surface and expand when you’re confident.
Expectation setting
What you’ll see first
Sol Helps is designed to protect decision quality. Early signal can take time — that is part of the design, not a flaw in it.
The goal is not to turn thin evidence into instant certainty. It is to preserve enough context for patterns to become trustworthy.
Evidence, not summaries
Early value is seeing real questions in context so you can judge the signal before you trust the pattern.
Signal builds over time
Themes become more stable as similar questions repeat. Quiet early periods are normal on low-traffic surfaces.
Clarity without overreach
The product avoids forcing conclusions when data is thin, so teams don’t act on false certainty.
Repetition is the signal
A single question can be noise. But when similar questions repeat across users and channels, it usually points to a stable explanation gap — a missing prerequisite, a terminology mismatch, or an unclear concept.
This is why Sol Helps focuses on recurring question clusters — not one-off feedback.
Diagnosis
What this helps you diagnose
The mechanism matters because it preserves the clearest evidence of early confusion: the question asked at the moment understanding breaks. Those questions become Customer Confusion Insights.
Repeated questions reveal the shape of the misunderstanding
Sol Helps helps you move from isolated questions to a more stable view of what users consistently fail to understand, where that confusion appears, and what team should probably act on it first.
Process
How Sol Helps turns real questions into clarity
Analytics shows what happened. Sol Helps helps you reason about why — using the questions users already ask.
Content becomes the source of truth
Your docs, help pages, onboarding guides, and FAQs are indexed into a vector store. Responses are grounded in that documentation, not generic guessing.
Users ask questions where they get stuck
The widget runs anywhere JavaScript can run: product, docs, or onboarding. On Growth+ plans, you can lock it to your allowed domains.
Consented conversations become clarity signals
Sol Helps groups questions into themes and intent so you get a prioritised view of what to investigate or improve next, without forcing conclusions.
What’s happening under the hood
Content → assistant answers → consented conversations → clarity signals
Examples of what becomes actionable
- “Do I need admin access?” → prerequisites / permissions
- “Which plan includes X?” → pricing / packaging
- “Why won’t this work for our setup?” → edge cases / integration
Supported file types
Upload the docs you already have—no special formatting required.
Content ingestion
Crawl URLs in three common ways
Sol Helps can crawl URLs and turn selected pages into HTML for indexing, so you can start from the content you already ship.
Single URL crawl
Paste one URL and include only the pages you select. Great for quick trials.
Sitemap crawl
Point Sol Helps at your sitemap and choose what gets indexed. Best for docs hubs.
Upload your files
Upload files directly and keep complete control over what enters the knowledge base.
Trust & guardrails
Low-risk to trial, grounded by design
Sol Helps is designed to stay low-risk to trial: answers stay grounded in your documentation, deployment is lightweight, and customer conversations never train public models.
The goal is to make the product safe to evaluate before you commit to deeper rollout or integration work.
Guardrails keep it informational
Grounded in your docs by default, with guardrails that keep answers conservative, aligned with your brand, and informational.
No public-model training
Conversations are never used to train public models. History is stored only with end-user consent; retention is plan-based.
Low-coupling by default
Fast to deploy and safe to trial. Useful before any deep integration work.
See what your users are actually stuck on
Sol Helps reduces experience blindness by turning real questions into an evidence-led clarity layer, so Product, Support, and Docs can share the same signal.
No sales call. Start with one surface and expand when ready.
Need more context? Who Sol Helps is for·When user confusion starts costing you