How it works

From problem to solution.

Five steps, no technical vocabulary required at any point.

01

Describe

Tell Horjely what happened, in your own words. No technical vocabulary required.

02

AI Analyzes

The assistant asks targeted questions and analyzes the symptoms you report.

03

Get a Recommendation

Receive a likely cause, a confidence score, a recommended service and estimated Credits.

04

Choose Your Path

Use guided AI troubleshooting, or hand the diagnosis to a professional.

05

Get It Resolved

Complete the service, confirm the issue is fixed, and only spend the Credits it took.

Technician diagnosing a laptop

Why it works

Diagnosis first, service second.

The expensive part of technology support is usually working out what's wrong. Horjely moves that step to the beginning, and makes it cheap.

You never need the right vocabulary

Traditional support forms ask you to pick a category before you know what's wrong. Horjely reverses that: you describe behaviour — "it gets hot and turns off" — and the system works out the category for you.

The AI asks what a technician would ask

When did it start? Does it happen on charge? Did anything change just before? These questions do most of the diagnostic work, and they're the same ones an experienced technician opens with.

You get a confidence score, not a guess dressed as certainty

Every diagnosis includes how confident the assistant is and why. When the evidence is thin, it says so and tells you which check would settle it.

Handoff carries the whole history

If you escalate, the specialist receives your description, the AI's reasoning, and everything you already tried. You never repeat yourself and you never pay for someone to re-diagnose.

FAQ

Questions, answered.

The things people ask most before they start their first diagnosis.

Don't know what's wrong?
Start with AI.

Describe the problem. Get a clear next step. Get professional help when you need it.

Horjely Assistant Online

You

"My Wi-Fi drops every evening in the back bedroom."

Horjely

That pattern points to channel congestion at peak hours combined with distance from the router. Let's confirm with two quick tests