Establishing secure connection…Loading editor…Preparing document…

Unlimited Support Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

UNLIMITED SUPPORT AGREEMENT

This Unlimited Support Agreement (the Agreement) is entered into as of by and between Service Provider Name: and Client Name: .

RECITALS

WHEREAS, Service Provider operates a business that provides technical support, maintenance, and related services as described herein; and

WHEREAS, Client desires to engage Service Provider to provide unlimited support services under the terms and conditions set forth in this Agreement; and

NOW, THEREFORE, in consideration of the mutual covenants and promises contained herein, the parties agree as follows:

1. SCOPE OF WORK

Service Provider will provide unlimited support services, including but not limited to remote troubleshooting, software updates, configuration assistance, monitoring, and advisory services as reasonably requested by Client and accepted by Service Provider within the technical and personnel capabilities of Service Provider. Services do not include major development, infrastructure procurement, or on-site labor unless expressly agreed in writing.

2. PAYMENT TERMS

In consideration for the Services, Client shall pay Service Provider the fees set forth below. Fees are exclusive of taxes unless otherwise stated.

All undisputed amounts not paid when due shall accrue interest at the rate set forth in the Late Fee field above and Client shall reimburse reasonable collection costs, including attorneys' fees, for collection of delinquent amounts.

3. TERM AND TERMINATION

This Agreement shall commence on and shall continue in effect until unless earlier terminated as provided herein.

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure such breach within thirty (30) days after receipt of written notice from the non-breaching party specifying the nature of the breach. Termination shall not relieve Client of the obligation to pay fees accrued through the effective date of termination.

4. CONFIDENTIALITY

Each party (Receiving Party) shall hold in confidence all non-public, proprietary or confidential information disclosed by the other party (Disclosing Party) and shall not use such information except as necessary to perform its obligations under this Agreement. Confidential information includes business, technical, and financial information, but does not include information that is: (a) publicly known through no breach by Receiving Party; (b) rightfully received from a third party without restriction; or (c) independently developed without use of Disclosing Party's confidential information.

The Receiving Party may disclose Confidential Information if required by law or regulation, provided that the Receiving Party provides prompt written notice to the Disclosing Party and cooperates reasonably in any effort to obtain confidential treatment or a protective order.

5. LIABILITY; INSURANCE

Except for liability arising from gross negligence, willful misconduct, or breach of confidentiality, neither party shall be liable to the other for consequential, incidental, special or punitive damages. Each party shall maintain commercial general liability insurance and professional liability insurance in amounts reasonably appropriate for the services provided.

6. GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws principles.

7. ENTIRE AGREEMENT; AMENDMENT

This Agreement, including any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior and contemporaneous agreements and understandings, whether written or oral. No amendment or modification of this Agreement will be effective unless in writing and signed by both parties.

8. MISCELLANEOUS

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions will remain in full force and effect. No waiver of any right or breach shall be effective except in a writing signed by the party to be charged. The parties are independent contractors and nothing in this Agreement creates an agency, partnership or joint venture.

Service Provider:

By:

Date:

Client:

By:

Date:

Enter text✕

What an Unlimited Support Agreement Is and when it's used

An Unlimited Support Agreement is a contractual arrangement where a vendor commits to providing support services to a client for a defined scope and period without a per-incident cap on assistance. Typical terms cover response and resolution SLAs, covered services, exclusions, escalation procedures, pricing or subscription mechanics, renewal and termination rights, and liability limitations. These agreements are used by software providers, managed service vendors, and professional services firms to simplify ongoing support, align expectations, and create predictable operational and financial commitments.

Why an Unlimited Support Agreement matters for operations and risk control

A clear Unlimited Support Agreement reduces ambiguity about coverage, response times, and fees while establishing governance for escalations, change requests, and termination. It protects both parties by defining measurable SLAs, exclusions (for example third-party defects), and dispute resolution paths under a chosen governing law.

Why an Unlimited Support Agreement matters for operations and risk control

Who commonly signs or prepares an Unlimited Support Agreement

Typical parties include software vendors, IT managed service providers, and client IT or procurement teams.

  • SaaS vendors and MSPs that deliver continuous technical support and maintenance.
  • Corporate IT or procurement teams that need predictable support for critical systems.
  • Legal and contract managers who need clear SLAs, indemnities, and termination clauses.

The agreement should be reviewed by legal and operational owners to confirm SLAs, exclusions, and service credits align with business needs.

Primary signatory roles and typical responsibilities

Vendor — Authorized Representative

The vendor signatory is typically a senior operations or account leader authorized to commit to SLAs, support scope, and pricing. Their responsibilities include honoring response and resolution targets, maintaining qualified personnel, and providing required documentation for escalations and audits.

Client — Authorized Representative

The client signatory is usually an IT, procurement, or legal officer empowered to accept terms, request services, and trigger support processes. They must provide required access, designate contacts, and comply with cooperation obligations to enable timely resolution.

Core sections to include in a professional Unlimited Support Agreement

A complete agreement clarifies scope, service levels, exclusions, pricing, term and renewal, and legal protections. Each section should be measurable where possible to reduce disputes and support enforceability.

Scope

Define covered systems, modules, and service types (incident troubleshooting, patching, monitoring), plus expressly excluded items such as third‑party products or custom development.

Service Levels

Specify response and resolution times by incident severity, measurement windows, uptime targets, and methods for calculating service credits for failures to meet SLAs.

Pricing

Detail subscription fees, billing cadence, any onboarding or ramp costs, change-order pricing, and how price adjustments or tax liabilities are handled.

Term and Renewal

State initial term, automatic renewal mechanics, notice periods for non‑renewal, and conditions for mid‑term termination or early exit fees.

Access and Cooperation

List client responsibilities for access, credentials, test environments, and timely cooperation necessary for troubleshooting and root cause analysis.

Liability & Indemnity

Limitations on liability, indemnity scope, and any insurance requirements to allocate financial risk between parties.

Security, compliance, and technical assurances to document

Encryption: TLS 1.2/1.3 in transit; AES‑256 at rest.
Audit Trail: Record timestamps, user IDs, and activity logs.
BAA Availability: Business Associate Agreement required for HIPAA data.
Certifications: SOC 2 Type II and ISO 27001 supported.
Access Controls: Role-based access and multi-factor authentication.
Regulatory Scope: ESIGN/UETA and 21 CFR Part 11 compliance options.

Step-by-step: how to prepare and execute an Unlimited Support Agreement

Follow these steps to complete the document accurately and reduce negotiation cycles.

  • 01
    Gather details: Compile system inventory, expected coverage, contacts, and billing information.
  • 02
    Draft SLA terms: Define severity levels, response/resolution times, and service credit calculations.
  • 03
    Review legal clauses: Confirm indemnity, limitation of liability, termination, and governing law.
  • 04
    Sign and onboard: Execute signatures, enable access, and schedule initial onboarding activities.

How to configure an online workflow for this agreement

Set up a digital signing workflow that captures signatures, audit data, and conditional fields before distribution.

Field Configuration
Signature Field Require signer name, signature, and date for each party.
Conditional SLA Fields Show advanced SLAs only if premium tier selected.
Authentication Use email plus SMS OTP or ID verification for higher assurance.
Attachments Include onboarding checklist and contact matrix as exhibits.

Typical routing and submission steps for signed agreements

A simple routing path ensures records and notifications reach the right teams and systems.

  • Upload: Sender uploads final agreement to the signing platform.
  • Place Fields: Add signature, initial, date, and conditional fields.
  • Send to Signers: Initiate signing order or generate a secure signing link.
  • Archive: Store executed PDF with audit trail in document repository.

Distribution channels and platform integration points

Choose delivery and storage options that meet your compliance and integration needs.

  • Email and Link: Send signer emails or public signing links.
  • API Integration: Automate workflows via CRM or ERP integrations.
  • Cloud Storage: Save executed files to enterprise repositories.

Integrations with CRM, document management, and ticketing systems reduce manual handoffs and preserve the audit trail.

Key timing rules and notice periods to include

Document explicit timelines for notice, SLA measurement, and renewal to prevent disputes.

Effective Date and Term:

State the start date and initial term length clearly.

Renewal Notice:

Require written notice 30–90 days before automatic renewal.

SLA Measurement Window:

Define the time window used to measure uptime and response metrics.

Termination Notice:

Set required notice for termination without cause, often 30–60 days.

Dispute Period:

Specify any cure period before termination or withholding of payments.

Typical milestone timeline from negotiation to steady-state support

Map milestones to owners and dates so onboarding and SLA enforcement proceed without gaps.

01

Negotiation Complete

Signed master agreement executed and countersigned by both parties.

02

Onboarding Start

Vendor begins access provisioning and knowledge transfer activities.

03

SLA Go-Live

Measured SLAs and monitoring go into effect for production support.

04

Quarterly Review

Regular performance review and report delivery to stakeholders.

Common mistakes to avoid when preparing an Unlimited Support Agreement

  • Ambiguous severity definitions that lead to different interpretations and SLA disputes between support teams and business users.
  • Omnibus language about 'all services' without exclusions for third‑party products or scope beyond ordinary maintenance.
  • Missing or weak change-order and request-for-service processes, causing unpaid development to be treated as support.
  • Failing to align billing cadence and termination notice with procurement cycles, leading to surprise renewals or chargebacks.

Risks and potential contractual consequences of poor agreement drafting

Breach Damages: Monetary exposure for missed SLAs or service failures.
Regulatory Risk: HIPAA or privacy breaches can trigger fines and corrective actions.
Termination Costs: Early termination fees or transition expenses may apply.
Indemnity Claims: Third‑party claims can trigger costly defense obligations.
Vendor Lock‑In: Poor exit provisions can impede migration and raise costs.
Tax Consequences: Incorrect supplier classification may affect withholding or sales tax.

Comparing eSignature pricing and capabilities for executing Unlimited Support Agreements

Vendor pricing models and compliance capabilities affect total cost and legal readiness for executing support agreements.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes Yes
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year Varies Varies Varies

Real-world examples of how organizations use Unlimited Support Agreements

Two brief examples show how different organizations operationalize unlimited support commitments.

Optica Ventures (COO)

The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

  • Contracted unlimited support to centralize incident handling and reduce vendor churn.
  • As a result, Optica standardized SLAs across portfolios and shortened resolution cycles while keeping predictable budgeting for support services.

Martin Properties (Founder)

I can process and execute all of these documents online with 100% compliance and built-in security.

  • Adopted unlimited support for property management systems and tenant portals.
  • This allowed the team to deliver consistent maintenance responses and reduced administrative overhead associated with multiple ad‑hoc support agreements.

Practical tips to speed up negotiation and reduce operational friction

Implement these practices to make the agreement clearer, easier to manage, and less costly over time.

Use measurable SLAs
Define severity tiers, response windows, and exact calculation methods for service credits to avoid disputes and simplify reporting.
Limit exclusions
State precise exclusions for third‑party software, customer misconfiguration, and catastrophic events to set clear operational boundaries.
Standardize templates
Create a template with prefilled legal and operational language to reduce legal review cycles for renewals and extensions.
Automate renewals
Integrate contract lifecycle management with billing systems and calendar reminders to prevent lapses or surprise charges.

Frequently asked questions about Unlimited Support Agreements

Answers to common questions about enforceability, signing, and operational implementation.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users