Establishing secure connection…Loading editor…Preparing document…

Software Support Agreement

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

SOFTWARE SUPPORT AGREEMENT

This Software Support Agreement (the "Agreement") is made effective as of by and between:

Provider Name:    Address:

Client Name:    Address:

WHEREAS

WHEREAS, Provider develops, maintains and supports certain software applications and related documentation (the "Software"); and

WHEREAS, Client desires to obtain support services for the Software and Provider is willing to provide such services under the terms set forth in this Agreement; and

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

Scope of Work

Provider shall perform support services for the Software as described below. Services may include incident response, troubleshooting, bug fixes, updates, upgrades, and reasonable assistance with configuration and operation of the Software. The specific tasks and deliverables are as set forth in the Scope of Work.

Support Services & Service Levels

Provider will provide support in accordance with the service levels selected below. Response times are measured from Provider's receipt of a support request as logged in Provider's support system.

Remote troubleshooting and support
On-site support (travel and expenses subject to separate approval)
24/7 emergency support

Payment Terms

Client shall pay Provider the fees for support as set forth below. All fees are exclusive of taxes unless otherwise required by law.

Late payments shall accrue interest at % per month (or the maximum rate permitted by law), and Provider may suspend support services if fees remain unpaid for more than days after invoice due date.

Term and Termination

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

Either party may terminate this Agreement for material breach if the breaching party fails to cure such breach within days after written notice. Either party may terminate without cause upon prior written notice to the other party.

On termination, Client shall pay Provider for all services performed and expenses incurred through the effective date of termination. Sections concerning confidentiality, payment of accrued fees, limitation of liability, and governing law shall survive termination.

Confidentiality

Each party (the "Recipient") shall hold in confidence all nonpublic, proprietary or confidential information disclosed by the other party (the "Discloser") that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). Recipient shall not disclose Confidential Information to any third party except to its employees, contractors and agents who have a need to know and who are bound by confidentiality obligations no less protective than those herein. Confidential Information does not include information that: (a) is or becomes publicly known through no wrongful act of Recipient; (b) is rightfully received from a third party without breach of an obligation of confidentiality; (c) was known to Recipient prior to disclosure; or (d) is independently developed by Recipient without use of Discloser's Confidential Information. Upon termination or request, Recipient shall promptly return or destroy Discloser's Confidential Information.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to conflict of laws rules. The parties submit to the exclusive jurisdiction of the state and federal courts located in that State for any disputes arising under this Agreement.

Entire Agreement

This Agreement, together with any exhibits or schedules attached hereto and any order forms executed by the parties referencing this Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or representations, whether written or oral. No amendment or modification of this Agreement will be effective unless in writing and signed by authorized representatives of both parties.

Miscellaneous

Neither party may assign this Agreement without the prior written consent of the other party, except that Provider may assign to an affiliate or successor in connection with a merger or sale of substantially all of Provider's assets. If any provision of this Agreement is held invalid or unenforceable, the remaining provisions will remain in full force and effect.

Provider (Printed Name):

By:

Date:

Client (Printed Name):

By:

Date:

Enter text✕

What a Software Support Agreement Covers

A Software Support Agreement is a contract that defines ongoing support, maintenance, and assistance for delivered software. It typically sets the scope of covered services, response and resolution times, ticketing and escalation procedures, uptime targets or service levels, pricing or retainer arrangements, exclusions and limitations, intellectual property boundaries, confidentiality obligations, and the agreement term and renewal mechanics. The contract clarifies responsibilities for both vendor and customer, establishes performance expectations, and provides remedies for service failures or breaches while documenting how changes, upgrades, and third‑party dependencies are handled.

Why a Dedicated Support Contract Matters

A clear Software Support Agreement reduces ambiguity about response times, fees, and responsibilities, helping avoid disputes and ensuring predictable operational support for production software.

Why a Dedicated Support Contract Matters

Who Typically Drafts and Signs This Agreement

Typical parties include software vendors, SaaS providers, managed service teams, and the customer’s IT or procurement group responsible for operational continuity.

  • Software vendors and MSPs — Vendors need clear liability and payment terms when supporting client environments.
  • IT/procurement teams — Buyers require defined SLAs, pricing, and escalation paths before accepting services.
  • Legal and compliance officers — Ensure contract terms align with regulatory requirements and internal risk tolerances.

The document is useful for corporate buyers, small businesses relying on third‑party apps, and internal IT departments that outsource maintenance tasks.

Common Signatory Roles

Vendor Authorized Signer

Typically an officer, VP of operations, or authorized contracting manager who can bind the vendor to indemnity, confidentiality, and SLA commitments. The signer should have authority to accept SLA metrics and pricing obligations on behalf of the vendor organization.

Customer Executive

Often the CIO, IT director, or procurement lead authorized to accept service levels, approve recurring fees, and agree to liability limitations. This signer must be able to coordinate internal change control and acceptance procedures tied to the agreement.

Core Clauses to Include in a Professional Agreement

A robust Software Support Agreement combines service definitions, measurable SLAs, and clear commercial terms to reduce disputes and operational downtime.

Service Scope

Define supported modules, versions, environments, and excluded items so parties share a common understanding of what support covers and what requires change orders.

Service Levels

Specify response and resolution times by severity level, uptime targets, measurement windows, and credits or remedies for SLA failures.

Support Process

Describe ticketing channels, escalation paths, working hours, on‑call procedures, and support languages or time zones.

Fees and Billing

Detail recurring fees, hourly rates for out‑of‑scope work, invoicing frequency, late fees, and payment terms.

Security & Compliance

Include data protection obligations, breach notification timelines, and industry addenda (for example HIPAA) when handling regulated data.

Term & Termination

State contract length, auto‑renewal rules, termination for convenience or breach, and post‑termination transition responsibilities.

How to Complete the Agreement Step by Step

Complete the agreement in order to avoid missing critical commercial or legal obligations.

  • 01
    Gather Documents: Collect prior contracts, SOWs, and system inventories.
  • 02
    Define Scope: List supported software, versions, and exclusions.
  • 03
    Set SLAs: Agree on severity definitions and response times.
  • 04
    Review & Sign: Obtain authorized signatures and distribute executed copies.

Typical Support Workflow from Ticket to Resolution

A predictable workflow ensures tickets are triaged, escalated, and resolved with clear ownership at each stage.

  • User Report: End user opens a ticket via portal or email.
  • Triage: Support assigns severity and initial owner.
  • Diagnosis: Engineer investigates root cause and workaround.
  • Resolution: Fix deployed, ticket closed, and post‑mortem recorded if needed.

Common Configuration Settings for Online Support Workflows

Configure your support workflow to match SLA targets and minimize manual handoffs.

Field Configuration
Authentication SAML SSO for staff; MFA for privileged accounts.
Notifications Email and SMS alerts for P1 incidents.
Templates Predefined response templates for common issues.
Bulk Routing Automated assignment by product and severity.

Digital Signing and Submission Considerations

Ensure the chosen provider can produce a reproducible audit trail and meets any industry compliance requirements such as HIPAA or 21 CFR Part 11 when applicable.

  • Document Formats: PDF and DOCX supported
  • Authentication Methods: Email links, SMS codes, KBA options
  • Integrations: CRMs and ticketing platforms

How a Software Support Agreement Differs from Related Contracts

Compare common contract types so you use the correct document for support, service levels, and maintenance obligations.

Criteria Software Support Agreement Service Level Agreement
Primary Purpose ongoing support and maintenance guarantees for uptime and response
Scope product and version specificity metrics and remediation only
Commercial Terms fees, retainer, and out‑of‑scope rates typically remedies and credits
Attachment often annexed to msa may be standalone or annex

eSignature Vendor Comparison for Executing Support Agreements

Common eSignature providers vary on price model, bulk send, audit capabilities, and HIPAA suitability. signNow is listed first for direct comparison across these criteria.

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 Varies Varies Varies
Bulk Send Yes Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Common Mistakes to Avoid When Preparing the Agreement

  • Unclear scope: failing to list supported modules or versions leads to frequent disputes over whether an issue is covered.
  • Vague SLAs: non‑specific response times and severity examples result in differing expectations and inconsistent responses.
  • Missing escalation: absence of escalation paths delays resolution and obscures who is accountable for critical incidents.
  • No change control: omitting a formal change order process causes scope creep and unpriced work during upgrades.

Key Risks and Contractual Consequences

Service Credits: Reduced fees
Indemnity Exposure: Third‑party claims
Data Breach: Regulatory fines
Termination Risk: Early contract exit
Reputational Harm: Client loss
Invalid Signature: Enforceability issues

Security and Compliance Controls to Include

Transport Encryption: TLS 1.2/1.3 in transit
Data at Rest: AES-256 encryption at rest
Certifications: SOC 2 Type II available
Healthcare: HIPAA BAA required
Regulated Records: 21 CFR Part 11 support
Information Policy: ISO 27001 and access controls

Frequently Asked Questions About Software Support Agreements

Answers to common questions about execution, enforceability, digital signing, and compliance for support agreements.


Need help? Contact support

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