Sol logoSol Helps

Relevance check

When Sol Helps is relevant and when it isn’t.

Sol Helps is for teams who need a clearer, shared view of what users are struggling to understand — especially when signals are fragmented across docs, onboarding, support, and product usage.

This page is intentionally simple: it helps you decide whether Sol Helps is the right tool for the job, and where to go next.

Prefer details first? How it works·Trust & privacy

Browse use cases Start with: Recurring user confusion
Use this page if…
You’re not sure which page to read next, or whether Sol Helps matches the kind of problem you’re solving.
What it helps you do
Run a fit check, run a non-fit check, then pick the most relevant route (problem page or use case).
What it avoids
No big claims. No ‘automation-first’ framing. Just decision support and clear next steps.

Decision

A quick fit / non-fit check

If you recognise the fit signals, Sol Helps is likely relevant. If you recognise the non-fit signals, it probably isn’t.

Likely a fit
Sol Helps tends to help most when…
  • The same questions repeat, but you can’t name the root misunderstanding.
  • Docs exist, but you don’t know which pages actually resolve confusion.
  • Onboarding completion looks fine, but activation quality feels uneven.
  • Support feedback is fragmented across channels and hard to summarise.
  • Your product has conceptual complexity (roles, permissions, workflows, configuration, mental models).
  • You want decision-ready clarity on what to fix first — without running surveys.
Likely not a fit
Sol Helps is usually not the right tool when…
  • Your main issue is engineering defects (crashes, latency, outages) rather than understanding.
  • You already have a mature support ops stack and only want ticket deflection.
  • You don’t have stable documentation or product knowledge to ground answers in yet.
  • Your problem is primarily acquisition (traffic, positioning, pricing) rather than product comprehension.
  • You need deep behavioural analytics instrumentation first (events, funnels, experimentation) and that’s currently missing.
  • You cannot collect or process user questions/conversations due to policy constraints.
If you’re on the boundary

It’s common to have a mix (e.g. some engineering defects, some comprehension gaps). Sol Helps is most useful when the hardest part is making the pattern visible — not implementing the fix.

Routes

Pick the closest situation

Start with a diagnosis (problem) if you’re still naming the issue. Start with a use case if you already know the job to be done.

Problem
Recurring user confusion
You see repeat uncertainty, but you can’t confidently say what users consistently misunderstand or where it originates.
Go to page
Use case
Help content gaps
Docs exist, but they’re failing: users still ask repeat questions, search without success, or miss key examples.
Go to page
Use case
Onboarding confusion
Users complete steps but don’t build confidence. They need reassurance, repeat guidance, or re-ask the same fundamentals. (Choose the closest onboarding use case.)
Go to page
Route
Not sure?
If none of the routes match, start with the problems index and pick the closest diagnosis first.
Go to page
Start with: Recurring user confusionBrowse use casesHow it worksTrust & privacy

Boundaries

What Sol Helps is and isn’t

A quick clarification to prevent category errors.

What it is
A system for making user confusion and comprehension gaps more visible — using real questions and interactions as evidence — so teams can decide what to clarify first.
What it isn’t
Not a helpdesk replacement, not a generic chatbot, and not a ticket-deflection machine. Its role is to create clarity and prioritisation — not just faster responses.
Next step

If you recognised the fit signals, start with the closest route above. If you want the mechanics, read how it works. If you want data handling details, read trust & privacy.