A service-area map is a starting point. The meaningful question is how a provider will deliver hands-on work at your actual address when the usual remote fix is not enough.

List the places that need hands-on work

Create one record per office, branch, shared workspace, and recurring jobsite. Include support hours, local contacts, building access rules, equipment locations, and the work that cannot be done remotely. Record home-based employee support separately: shipping a replacement laptop is different from dispatching an engineer to an office.

Ask for dispatch specifics

Request the dispatch model for each location, including where engineers are assigned from, whether subcontractors are used, and how urgent visits are prioritized. Distinguish a target arrival time from a guarantee and identify the conditions that affect it. Do not assume that a provider’s San Francisco address establishes the same commitment for Napa, Pleasanton, or San Jose.

Resolve travel costs in the agreement

Ask whether travel time, mileage, bridge tolls, parking, and minimum visit charges are included or billed separately. Establish how a planned visit differs from an emergency dispatch. For multiple locations, request a coverage schedule rather than one region-wide sentence. These are cost questions to verify with each provider, not claims about standard regional rates.

Make premises and equipment accessible

Identify who can authorize entry, escort a technician, unlock the network closet, and contact the landlord or connectivity provider. Check whether the business needs a certificate of insurance or other building documentation before a visit. Ask how replacement equipment is obtained and configured. An engineer at the door cannot restore a failed device without the required access and parts.

Run a realistic outage walkthrough

Use an illustrative office-internet failure. Ask the provider to explain remote diagnosis, carrier escalation, backup connectivity, dispatch criteria, and employee updates. Then add a second office incident to test simultaneous coverage. Ask who decides which visit is first and what interim workarounds are available. Put material commitments into the service schedule.

Verify coverage as the business changes

Review coverage before an office move, acquisition, new jobsite, or expanded operating hours. Tell the MSP what is changing early enough to assess connectivity, access, and equipment. Review actual visits and charges after launch. A footprint that fit last year’s agreement may need a revised coverage schedule.

About this guidance

Published by Bay Area Managed IT. Examples are illustrative; they are not provider quotes, audited results, or local market survey findings. Read our editorial approach →

Continue the research

COMPARISON GUIDELocal vs. national MSP: which support model is a better fit?SERVICE GUIDEDoes your business really need 24/7 IT support?CONTRACT GUIDEHow to evaluate an MSP service-level agreement

Bring these questions to your next provider conversation.

Use a common scope and keep the evidence beside each answer.

Prepare your RFP →