Sol — the Solidlio AI Assistant
An assistant that lives in every portal, already knows which ticket, asset or invoice you are looking at, and can read your live data to answer — with every answer bounded by the same permissions the rest of the product enforces.
How Solidlio helps
Sol is embedded in all four portals and receives the record you are viewing as context. It can call 23 read tools across tickets, assets, projects, invoices, quotes, contracts, changes, monitoring, clients, services, store orders, users and the knowledge base — and it answers from what those tools return rather than from memory. Which tools exist for a given conversation is decided by the portal you are in, and the data a tool returns is scoped and redacted by the same rules the underlying screens use. Answers stream token by token, with the reasoning summarized as it goes, and every turn is metered against your plan’s AI credits before it runs.
Capabilities
| Capability | What it does |
|---|---|
| Context-aware chat | Opens already pinned to the ticket, asset, project or invoice on screen |
| Live data tools | Reads 23 tools across 14 domains rather than answering from training data |
| Portal-scoped tooling | A customer’s Sol cannot call MSP or platform tools — the tool set differs per portal |
| Knowledge grounding | Searches your knowledge base per turn and cites what it used |
| Retrieval transparency | Reports whether grounding succeeded, so “no results” is distinguishable from an outage |
| Image understanding | Attach a screenshot; Sol reads it as part of the question |
| Credit metering | Every turn — and every tool call inside it — is charged and capped before it runs |
| Conversation history | Threads persist per person, searchable, with auto-generated titles |
Built for MSPs and their clients
Sol runs in the customer portal, not just the staff portals — and the difference between them is enforced in code, in two independent places.
| Organization / customer | MSP staff | |
|---|---|---|
| Tools offered | Read-only tools for their own records | The full staff tool set across managed clients |
| Ticket context | Public correspondence only — internal notes are stripped before the prompt | Full thread including internal notes |
| Staff surfaces | Change plans, project budgets, monitoring telemetry and purchasing are withheld | Available |
| Attachments | Scoped to their own uploads | Scoped to their own uploads |
The portal is derived from the signed session, never from a request parameter, and an unrecognized portal resolves to the least-privileged one.
How it works
- Open Sol from any portal. The panel is in the layout, so it is available on every page.
- Sol picks up context — the record you are viewing becomes the conversation’s subject, resolved and summarized into the system prompt.
- Ask in plain language. The turn is charged against your AI credits first; if the account is out, you are told so rather than silently degraded.
- Sol searches the knowledge base and reports whether that search succeeded.
- Sol calls tools as needed — each call is shown as it happens, and each is charged and bounded, so a runaway loop stops rather than billing indefinitely.
- The answer streams back, with sources listed and reasoning summarized.
Credit cost per turn
| Turn type | Credits |
|---|---|
| Text conversation | 3 |
| With an image | 5 |
| With tool use | 5 |
| Each tool call inside a turn | +1 |
Plan tiers set the monthly credit allowance. Organizations can be granted access to their MSP’s credit pool per feature group, so an MSP can enable the assistant for a client without handing over the whole allowance.
Limits
- Sol reads; it does not act. The one exception is raising a ticket.
- MSP staff tools are scoped to the MSP’s own organization for record lookups; cross-client roll-ups are available through the client tools, not the per-record ones.
- Conversation rename, pin, archive and delete are available through the API but are not yet surfaced as controls in the panel.
- SVG images can be attached and displayed but are not sent for visual analysis.
Plans and access
Availability depends on your plan, role and account permissions. Capacity limits and service terms apply. Compare current plans and integration requirements, or ask us about your setup.