Legal

Service Commitment

What we commit to on availability and support, how it is measured, and what you get if we miss it. Customers with a signed agreement should note that their agreement sets the commitment that applies to them.

This applies to ContractorX and to every site and product we operate under it: contractorx.co, rooferx.com (RooferX), solarsalesx.com (SolarSalesX), and tradesmenx.com (TradesmenX). RooferX, SolarSalesX and TradesmenX are the ContractorX platform presented for a particular trade, not separate services. Where this page says ContractorX, the Services, or we, it means all of them.

Last updated August 20, 2026. Questions about anything here? Contact us.

1. Availability commitment

We use commercially reasonable efforts to make the production environment of the platform available at least 99.5% of the time in each calendar month.

Available means the web application and authenticated APIs respond to properly formed requests without a systemic error that prevents substantial use of core functionality. The production environment is your live workspace; sandbox, preview, and evaluation environments are excluded.

Monthly availability is total minutes in the month, minus unavailable minutes, divided by total minutes, as measured by our monitoring systems.

2. What does not count as downtime

  • Scheduled maintenance performed in the window below, and emergency maintenance reasonably necessary to preserve security, integrity, or availability, with such notice as is practical.
  • Force majeure events.
  • Anything caused by your systems, networks, devices, configurations, credentials, integrations, acts or omissions, or your breach of the agreement.
  • Anything caused by a third-party service or data provider, including degradation, rate limiting, quota exhaustion, suspension, or discontinuation of an upstream property, geospatial, mapping, solar-modeling, payment, communications, or e-signature provider.
  • Requests queued or limited by the safety controls that protect the service for everyone. Those are by design, not failures.
  • Suspension applied in accordance with the Terms of Use.
  • Beta, preview, and early access features.
  • Mobile app unavailability caused by a device operating system, an app store, device-level network conditions, or your failure to install an available update.
  • Degraded performance that does not prevent substantial use of core functionality.

3. Service credits

Monthly availabilityService credit
99.5% or aboveNo credit
99.0% to below 99.5%5% of the monthly subscription fee
98.0% to below 99.0%10%
95.0% to below 98.0%20%
Below 95.0%30%
  • Submit a written claim to the support channel within 30 days after the end of the affected month, with the dates and times of the outage and its impact. Later claims are waived.
  • Approved credits are applied to the next invoice. They are not cash, not transferable, do not accrue interest, expire on termination, and do not reduce any minimum commitment in your plan.
  • Credits are capped at 30% of the monthly subscription fee for the affected month.
  • Service credits are your sole and exclusive remedy for missing the availability commitment.
  • Chronic failure: if availability falls below 95.0% in three months within a rolling six-month period, you may terminate for cause on 30 days notice given within 30 days after the third such month, and receive a pro-rata refund of prepaid, unused subscription fees.

4. Scheduled maintenance

  • Standard window: Sundays, 12:00 a.m. to 4:00 a.m. in the billing time zone.
  • Advance notice: at least 48 hours.
  • Maximum duration: 8 hours in any calendar month.
  • We make commercially reasonable efforts to schedule outside peak field operating hours and to keep it short.

5. Support channels and hours

  • Primary channel: the support channel designated inside the platform. The current support address is provided at onboarding.
  • Standard hours: Monday to Friday, 8:00 a.m. to 6:00 p.m. in the billing time zone, excluding our holidays.
  • Severity 1 coverage: 24 hours a day, 7 days a week.
  • Named contacts: up to three of your people are authorized to open cases.

6. Severity levels and response targets

SeverityDefinitionInitial responseRestoration objective
S1 — CriticalThe platform is unavailable, or a core function is completely inoperable for all users with no workaround. Field operations are halted.1 hour, 24×7Continuous effort until resolved or a workaround is in place
S2 — HighA core function is materially impaired for a substantial subset of users, or the workaround is materially burdensome.4 business hours2 business days to resolution or workaround
S3 — MediumA non-core function is impaired, or a core function is impaired with a reasonable workaround.1 business dayNext scheduled maintenance release
S4 — LowCosmetic issue, documentation question, configuration request, feature request, or general inquiry.2 business daysAt our discretion

We assign the initial severity in good faith based on reported impact, and will not unreasonably refuse a reclassification request. Response times run from our receipt of a properly submitted case. Restoration objectives are targets, not warranties, and are not subject to service credits. Please include affected accounts, timestamps, reproduction steps, error messages, and screenshots; the clock pauses while we wait on information we have reasonably requested.

7. What support does not cover

  • Issues arising from misuse, misconfiguration, or breach of the agreement.
  • Third-party services and your relationships with those providers.
  • Your networks, devices, or internet connectivity.
  • Training beyond what your onboarding statement of work includes.
  • Custom development, custom report building, and data migration, which are professional services.
  • Beta features.
  • Issues you decline to remediate after we identify a cause on your side.

8. Backup and recovery objectives

  • Automated daily backups, with the ability to restore to a point in time.
  • Backups retained for 30 days.
  • Documented recovery objectives, reviewed and tested as part of our operations.

These are operational objectives, not warranties. They are not subject to service credits, and they do not replace your responsibility to keep your own copies of anything operationally critical. This version is effective as of August 20, 2026. See also the Terms of Use and the Acceptable Use Policy.