Questions answered
The contract language can wait. Start with plain answers.
These answers clarify the service direction while leaving exact commitments where they belong: in discovery and the written agreement.
Fit and scope
Who is White Glove MSP for?
Growing companies that want ongoing ownership across support, maintenance, Microsoft 365, and the decisions connecting them.
What does managed IT include?
Likely lanes include user support, devices, Microsoft 365 administration, maintenance, and practical security fundamentals. Exact inclusions and exclusions are confirmed in scope.
What if we only need a project?
Describe it during the introduction. We will determine whether a scoped project fits or whether another specialist path would be more appropriate.
Price and commitments
Are the plan prices final quotes?
They are honest starting bands: Essential at $39 and Plus at $49 CAD per user, per month. Discovery confirms fit, covered environment, and separate project work.
Do you promise a response time or universal coverage window?
This public site does not publish an unverified SLA. Service hours, escalation expectations, and commitments belong in the actual agreement.
Transition and Microsoft 365
Can you take over from another provider?
A transition may be possible. Onboarding identifies documentation, access, incumbent coordination, vendor dependencies, and safe first priorities.
Is Microsoft 365 support included?
Microsoft 365 management is part of the service direction, including tenant administration, account hygiene, licensing context, and collaboration support within scope. We do not claim affiliation with Microsoft.
What should we prepare for the first conversation?
Approximate user and device counts, locations, important applications, Microsoft 365 context, current support, recurring friction, and near-term changes are useful. Unknowns are fine.
Devices, vendors, and service boundaries
Does managed IT cover every device?
No universal device coverage is implied. Supported device types, ownership, operating-system expectations, locations, lifecycle conditions, and exceptions are confirmed during discovery and written scope.
What happens when another vendor owns the problem?
The managed IT team can retain context, coordinate the escalation within scope, and keep the next owner visible. It cannot control a third party’s actions, timing, contract, or product responsibilities.
Is after-hours support included?
This public site does not claim after-hours or 24/7 coverage. Service hours, escalation paths, response expectations, and any exception process must be confirmed in the service agreement.
Are projects included in the monthly plan?
Recurring service and project work are different commitments. Major migrations, office moves, platform changes, remediation, and deployments may require separate discovery, scope, pricing, and acceptance criteria.
Transition, continuity, and exit
What if the current provider has incomplete documentation?
Treat missing documentation and access as visible transition risks. The incoming team should identify what can be verified, what needs incumbent cooperation, and what remains unresolved rather than promise a frictionless takeover.
How should credentials be transferred?
Never send passwords, recovery codes, or other secrets through the public contact form. A secure transfer method and authorized recipients must be agreed directly during onboarding.
What should happen if we later leave?
Exit responsibilities should be addressed in the agreement. A responsible transition should identify company-owned information, access paths, active vendors, known open work, and reasonable coordination boundaries without implying that every tool or artifact transfers unchanged.
Can service begin immediately after signing?
No universal start date is promised. Timing depends on agreed scope, access, incumbent cooperation, discovered conditions, and the sequence needed to establish a safe support path.
Fit by situation
How is managed IT different from paying a break-fix provider by the hour?
The payment model changes the incentive: one bills for the incident, the other is paid to prevent it.
Can we add security layers beyond the standard baseline?
Yes. Awareness training, MFA enforcement, email filtering, and credential-exposure monitoring coordination are available as separately scoped add-ons.
Do you support professional services firms like law or accounting practices?
Yes. Client confidentiality, document workflow, and practice-management software tend to be the priorities worth discussing first.
Do you support nonprofit organizations?
Yes. Predictable budgeting, donor data management, and a mixed staff-and-volunteer access pattern are common starting points.
We operate more than one location. Does that change the service?
It changes what needs standardizing-device and account setup, per-site connectivity, and access governance across sites.
Still weighing fit?
The walkthrough gives your questions a working shape.
Reach the team
Tell us what needs an owner
Share your team size, current support setup, and the responsibilities you want clarified. We will use that to figure out whether an MSP introduction makes sense.
Online requests are not available right now. No message is sent from this page.