Start here

Quickstart: your first investigation in 10 minutes

Install the desk, sign in, and get a cited root cause on a real ticket. No connector needed to start.

10 min read

Who this is for

Solvaro is an investigation desk for support engineers at every tier: CSE, TSE, L1 through L3, and the escalation engineers behind them. You bring a ticket; Solvaro reads it with its logs and attachments, checks your code and your team’s past cases, and gives you a root cause with the evidence, a workaround, and a draft you approve before anything goes out.

1. Install (2 minutes)

  1. Open the Download page and pick your build: Mac Apple silicon, Mac Intel, or Windows.
  2. Mac: drag Solvaro to Applications, then right-click the app and choose Open the first time (the build is not notarized yet).
  3. Windows: if SmartScreen shows “Windows protected your PC”, choose More info, then Run anyway.

2. Sign in (1 minute)

  1. Open Solvaro and choose Sign in. Use email or Google.
  2. You land on Home. If your org has no helpdesk connected yet, Home shows sample tickets so you can try everything right away.
Solvaro Home with open tickets, new today, SLA at risk and the queue
Home with sample tickets. Click any count to see the tickets behind it.

3. Investigate a ticket (5 minutes)

  1. In the box at the top of Home, paste a ticket ID, a log line, or describe the symptom, then press Enter. Or click a ticket in My queue.
  2. Solvaro opens a case and starts working. You see what it is reading as it goes.
  3. Read the answer from the top: what it thinks is happening, the root cause with a confidence score, the evidence (ticket, log lines, file and line in code), what it ruled out, and a workaround.
  4. Ask a follow-up in the box at the bottom, in plain words. For example: “Why did this start today and not last week?”
Recorded in the app with the demo org. No edits.

4. Act on it (2 minutes)

  • Rate the answer with the thumbs under it. A confirmed answer teaches Case Memory, so the next engineer with the same symptom gets it faster.
  • Open ⋯ → File another bug / feature request to get a bug draft built from the investigation. Preview it, then Copy markdown or, once a tracker is connected and external posts are on, file it.
  • Choose Finish & save when you are done. The case goes to History with its findings. Leave keeps it as a draft instead.

Make it yours next

  • Connect your helpdesk so Home shows your real queue: see Connect your helpdesk and tools.
  • Add a local repository folder in Settings → Integrations → Local repositories so answers can cite your code. The index stays on your computer.
  • Ask your org admin which AI provider your org uses: see Choose your AI provider.