Are electronic signatures enforceable?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA in most states, provided intent, consent, attribution, and record retention requirements are met.

When is notarization required?

Notarization is generally not required for private support contracts, but some states or third parties may ask for notarized signatures for specific filings or proof of execution.

Do I need a HIPAA addendum?

If the provider accesses protected health information, include a HIPAA Business Associate Agreement and require appropriate technical and administrative safeguards.

How can I limit vendor liability?

Use clear liability caps, exclude consequential damages, and define indemnity scope—ensure language is mutual where possible to balance risk.

What if a party changes the scope mid-term?

Include a written change-order procedure that defines approval, pricing adjustments, and effective dates to prevent scope creep and billing disputes.

How do I revoke or cancel signed agreements?

Follow the termination provisions in the agreement; revocation outside those terms may not be effective. For consumer-facing transactions, follow ESIGN disclosure and withdrawal procedures if required.

Electronic Signature
Templates
Miscellaneous
Support Services Agreement

Support Services Agreement

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

Support Services Agreement

This Support Services Agreement ("Agreement") is entered into as of by and between Service Provider: , with principal place of business at and Client Name: , with principal place of business at .

Recitals

WHEREAS, Service Provider has expertise and experience in providing technical support and maintenance services described below; and

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

WHEREAS, the parties wish to set forth their respective rights and obligations with respect to such support services.

Scope of Services

Service Provider will provide support services as described below. Service Provider shall perform the services with reasonable skill and care consistent with industry standards. The scope below may be amended only by written agreement of the parties.

Detailed Description of Services

Payment Terms

In consideration for the services provided under this Agreement, Client shall pay Service Provider in accordance with the rates, schedule and terms set forth below. Fees payable hereunder are exclusive of any taxes unless otherwise required by law.

Fee Amount (per month / per project) Billing Schedule and Payment Method Late Payment

Payments not received within days after the invoice due date shall incur a late fee of % per month on the overdue balance, or the maximum permitted by law, whichever is lower.

Term and Termination

This Agreement shall commence on and shall continue until unless earlier terminated in accordance with this Section.

Termination for Convenience

Either party may terminate this Agreement for any reason upon days' prior written notice to the other party.

Termination for Cause

Either party may terminate this Agreement immediately upon written notice if the other party materially breaches any obligation under this Agreement and fails to cure such breach within thirty (30) days after receipt of written notice specifying the breach.

Confidentiality

"Confidential Information" means any non-public information disclosed by one party ("Discloser") to the other ("Recipient") 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, including business plans, technical data, trade secrets, and customer information.

Recipient shall (a) hold Confidential Information in confidence using at least the same degree of care it uses to protect its own confidential information but not less than reasonable care; (b) not disclose Confidential Information to any third party except to employees and contractors who have a need to know and who are bound by written confidentiality obligations at least as protective as those herein; and (c) use Confidential Information solely for the performance of this Agreement.

The obligations in this Section shall survive termination or expiration of this Agreement for a period of from the date of disclosure, except that trade secrets shall be protected for as long as they remain trade secrets under applicable law. Confidential Information does not include information that (i) is or becomes generally available to the public other than as a result of a breach by Recipient, (ii) was known to Recipient without restriction prior to disclosure by Discloser, (iii) is received from a third party not subject to an obligation of confidentiality, or (iv) is independently developed by Recipient without use of Discloser's Confidential Information.

Independent Contractor; Liability

The parties are independent contractors. Nothing in this Agreement creates an employment, partnership, joint venture or agency relationship between the parties. Service Provider shall be solely responsible for withholding and paying all employment-related taxes for its personnel.

EXCEPT FOR LIABILITY ARISING FROM WILLFUL MISCONDUCT OR GROSS NEGLIGENCE, EACH PARTY'S AGGREGATE LIABILITY FOR CLAIMS ARISING OUT OF OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED THE TOTAL AMOUNTS PAID OR PAYABLE BY CLIENT TO SERVICE PROVIDER UNDER THIS AGREEMENT IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.

Notices

All notices required or permitted under this Agreement shall be in writing and delivered by hand, courier, or certified mail to the addresses set forth below or to such other address as either party may designate by notice.

Service Provider Contact for Notices Client Contact for Notices

Governing Law; Dispute Resolution

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. Any dispute arising out of or relating to this Agreement shall be resolved in the state or federal courts located in that State, and each party hereby consents to the exclusive jurisdiction and venue of such courts.

Entire Agreement; Amendments

This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. No modification, amendment or waiver of any provision of this Agreement shall be effective unless made in a written instrument signed by authorized representatives of both parties.

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall continue in full force and effect to the extent permitted by law.

Service Provider:

By:

Date:

Client Name:

By:

Date:

What a Support Services Agreement Covers

A Support Services Agreement is a contract that defines ongoing technical, operational, or maintenance services a provider will deliver to a customer. It typically identifies the parties, scope of covered services, service level objectives (response and resolution times), fees and invoicing, change-control procedures, term and renewal mechanics, liability and indemnity limits, confidentiality, and termination rights. The agreement establishes expectations for performance, outlines remedies for breaches, and allocates risk between the contracting parties so both provider and customer understand obligations across the lifecycle of support delivery.

Why a Clear Support Services Agreement Matters

A well-drafted Support Services Agreement reduces dispute risk, sets measurable service levels, protects confidential data, and clarifies financial obligations. It also helps align expectations and provides contractual remedies when support levels are not met.

Who Typically Uses a Support Services Agreement

Common users include technology vendors, managed service providers, corporate procurement teams, and in-house IT departments drafting or accepting support terms.

Managed service providers and VARs who deliver recurring maintenance and incident support to customers.
Enterprise IT teams procuring third-party maintenance for software, cloud, or hardware platforms.
Software vendors licensing products with optional or required paid support plans.

The agreement is relevant to any organization buying or selling ongoing technical, application, or infrastructure support and those that need formal SLA commitments.

Core Elements to Include in the Agreement

A professional Support Services Agreement is organized around service scope, measurable SLAs, responsibilities, pricing, data protections, and termination/renewal terms to make obligations clear and enforceable.

Scope of Services

Describe covered systems, in-scope tasks, exclusions, maintenance windows, and any deliverables so both parties share a precise understanding of responsibilities.

Service Levels

Define response and resolution targets, priority levels, escalation paths, metrics, and remedies such as credits for missed SLAs to measure performance objectively.

Pricing & Billing

State fees, billing frequency, payment terms, invoicing procedures, expense reimbursement, and how change orders are priced to avoid payment disputes.

Data Protection

Include confidentiality, permitted data uses, security controls, breach notification timelines, and HIPAA or other regulatory addenda when applicable.

Liability and Indemnity

Allocate risk with liability caps, disclaimers for indirect damages, and mutual indemnities for third-party claims tied to negligence or IP infringement.

Term, Renewal, Termination

Set initial term, renewal mechanics (automatic or manual), termination for cause/ convenience, notice periods, and post-termination transition obligations.

Essential Data Fields to Capture in the Agreement

Party Names: Full legal entity names

Effective Date: MM/DD/YYYY format

Scope Reference: Exhibit or schedule ID

Payment Terms: Net days and currency

SLA Metrics: Response/resolution targets

Signature Blocks: Authorized signer and date

Step-by-Step: Completing a Support Services Agreement

Follow a clear sequence to reduce negotiation cycles and ensure operational readiness before service begins.

01

Identify Parties: Enter full legal names and contact details for each party.
02

Define Scope: Attach a detailed schedule describing covered systems and exclusions.
03

Set SLAs: Specify priorities, response/resolution times, and escalation contacts.
04

Sign and Record: Obtain authorized signatures and store executed copy in a secure system.

How to Configure an Online Workflow for Execution

Use a predictable digital workflow to collect signatures, apply authentication, and retain an audit trail for the executed agreement.

Field	Configuration
Upload Document	Add the final PDF or DOCX version to the platform
Place Signature Fields	Assign signer roles, date, initial, and optional checkbox fields
Set Authentication	Choose email, SMS code, or advanced signer methods
Notifications	Enable reminders, completion emails, and recipient copies

Where to Send or File the Executed Agreement

Decide destination and custody rules in advance to streamline acceptance and recordkeeping.

Primary Custodian: Corporate legal or contracts repository holds the master executed copy
Operational Copy: Ops/Service Delivery team receives an accessible copy for SLA management
Finance: Billing receives invoice and payment terms for accounts payable
Client Distribution: Each contracting party retains a signed copy for its records

Distribution Channels and Digital Formats

Support Services Agreements are normally distributed as PDF or DOCX and routed by email or secure signing link.

File Formats: PDF, DOCX, or image
Delivery Methods: Email links, bulk send, or API
Integrations: CRM, ERP, cloud storage

Choose a delivery method that preserves the audit trail, supports your preferred authentication level, and integrates with contract repository systems.

Key Timing Expectations and Notice Periods

Establish explicit timelines in the agreement for responses, renewals, termination notices, and invoicing to avoid ambiguity.

SLA Response Time:

Hours to respond based on priority (e.g., 1–4 hours)

Resolution Targets:

Target windows such as 24, 48, or 72 hours

Renewal Notice:

Provide 30–90 days written notice before renewal

Invoice Due Date:

Standard net 30 or net 45 payment terms

Termination Notice:

30 days for convenience; shorter for material breach

Common Mistakes to Avoid

Vague scope language that creates disputes about whether a specific task is covered under support.
Missing SLA definitions for priority levels, response times, or remedies for missed targets.
Failure to tie pricing and change-order procedures to a defined process, leading to billing disagreements.
Not addressing data access, security controls, or regulatory addenda such as HIPAA where applicable.

Consequences of an Incorrect or Incomplete Agreement

Service Disruption: Unclear duties can delay remediation

Financial Exposure: Uncapped liability or missed invoicing

Regulatory Risk: Noncompliance with HIPAA or industry rules

Contract Disputes: Leads to arbitration or litigation

Termination Costs: Early exit fees or transition expenses

Reputational Harm: Customer trust and retention suffer

eSignature Pricing and Feature Snapshot for Agreement Execution

Common pricing and capability differences affect per-user costs, bulk sending, HIPAA support, and envelope or invite limits; signNow is shown first for direct comparison.

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

Real-World Examples of Digital Agreement Execution

Organizations use eSignature platforms to speed execution, centralize records, and maintain compliance when applying support contracts at scale.

Optica Ventures — COO

Their team needed fast contract turnaround for client engagements

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

Martin Properties — Founder

Property managers moved maintenance agreements online to avoid in-person signings

Mobile signing enabled faster renewals
I can process and execute all of these documents online with 100% compliance and built-in security.

Typical Signatories and Their Authority

IT Manager

An IT Manager may draft the technical scope and approve operational details, but signature authority usually requires an officer or delegated contract signatory named in corporate resolutions.

Chief Financial Officer

A CFO or delegated finance approver typically signs pricing and payment terms; confirm delegated authority thresholds to ensure the signature binds the organization.

Frequently Asked Questions About Support Services Agreements

Answers to common legal and operational questions about drafting, signing, and enforcing Support Services Agreements.

Need help? Contact support

Are electronic signatures enforceable?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96, 2000) and UETA in most states, provided intent, consent, attribution, and record retention requirements are met.
When is notarization required?
Notarization is generally not required for private support contracts, but some states or third parties may ask for notarized signatures for specific filings or proof of execution.
Do I need a HIPAA addendum?
If the provider accesses protected health information, include a HIPAA Business Associate Agreement and require appropriate technical and administrative safeguards.
How can I limit vendor liability?
Use clear liability caps, exclude consequential damages, and define indemnity scope—ensure language is mutual where possible to balance risk.
What if a party changes the scope mid-term?
Include a written change-order procedure that defines approval, pricing adjustments, and effective dates to prevent scope creep and billing disputes.
How do I revoke or cancel signed agreements?
Follow the termination provisions in the agreement; revocation outside those terms may not be effective. For consumer-facing transactions, follow ESIGN disclosure and withdrawal procedures if required.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now