Customers get a low-friction path
They can request help or join by code without account setup blocking the first response.
For MSP remote service
Remote support customers trust.
Fast Windows sessions, clear tenant controls, and audit trails without forcing customers through a portal first.
Customer intakeJoin by code
Host AgentExplicit enrollment
Tenant scopeWorkspace boundaries
Session evidenceReview-ready trail
Designed around the support relationship.
Customers, technicians, and admins each get a simpler path without weakening access control.
Technicians see the right context
Session, device, and customer details stay close to the remote-control workflow.
Admins keep durable control
Tenant scope, enrollment tokens, and audit review stay visible after the session ends.
Built for support teams that inherit complexity.
SoLo Support brings intake, access, tenant scope, and audit evidence into one remote support surface.
Windows-first support operations
Support customers through attended sessions, Quick Support downloads, and enrolled host agents without mixing tenant data.
Consent-led access
Enroll hosts after approval, then keep persistent access bound to tenant policy.
Tenant boundaries
Technicians, customers, devices, and sessions stay scoped to the right workspace.
Session evidence
Access decisions, device changes, and support events stay available for review.
A cleaner operating model for remote service.
Keep the customer path simple while preserving the controls MSP operators need.
Open the request
Customers can join with a code or send a request without needing a portal invite.
Authorize the device
Attended sessions stay temporary. Persistent access requires an explicit enrollment path.
Connect the technician
MSP teams get Windows-first remote control with customer context close at hand.
Review the trail
Admins can trace session activity, installer issuance, and account decisions from the console.
A good fit when access needs governance.
SoLo Support is strongest when remote access must be fast, visible, and scoped across multiple customer relationships.
Multiple customer organizations
Keep customer records, technicians, devices, and support history scoped to the right workspace.
Authorized unattended support
Use Host Agent enrollment when persistent access is needed and attended sessions when it is not.
Audit review matters
Preserve access decisions, installer issuance, and session activity for later operational review.
Deployment terms vary
Start managed, then support self-hosted control-plane requirements when customer contracts demand it.
Enterprise controls without enterprise drag.
SoLo Support is built around authorization, tenant scope, and release visibility from the first support request.
Identity
Shared Supabase Auth keeps authentication separate from tenant records and app-specific roles.
Authorization
Attended sessions stay temporary, while persistent access requires explicit device enrollment.
Evidence
Session events, device changes, installer issuance, and account decisions stay available for review.
Operations
Health probes, protected admin views, and release checks make support readiness easier to verify.
Choose the deployment path that fits.
Start with managed SaaS, or run SoLo Support in your own environment when the customer contract calls for it.
Fastest path to a support workspace.
Hosted sign-in, customer intake, support chat, analytics, and health probes are ready to connect to your workspace.
- Hosted identity and workspace setup
- Public request and quick-join routes
- Support chat and analytics hooks
- Operational health checks
For stricter infrastructure control.
Run the control plane, host-agent delivery, and monitoring stack in your preferred infrastructure.
- Customer-controlled deployment
- Host-agent delivery path
- Monitoring stack ownership
- Contract-aligned operations
Questions before the first session.
A few practical details for MSP teams evaluating attended support, unattended access, and deployment control.
Can customers request support without signing in?
Yes. The public support request and join paths are built for customers who need help before a portal account is ready.
What is the difference between Quick Support and Host Agent?
Quick Support is for one-time attended help. Host Agent enrollment is for authorized unattended access to a known Windows device.
How is unattended access authorized?
Persistent access is tied to an explicit enrollment path, customer organization scope, and technician permissions.
Can SoLo Support be self-hosted?
Yes. Managed SaaS is the fastest path, and self-hosted deployment is available when customer contracts require stricter control.
What does the audit trail capture?
The platform is designed to preserve session activity, access decisions, device changes, and installer issuance for review.
Start with a workspace, or help a customer now.
Create an MSP workspace, join an existing session, or open a support request from the public site.