Can the addendum be signed electronically?

Yes. Electronic signatures are legally enforceable in interstate transactions under the ESIGN Act (15 U.S.C. ch. 96) and under UETA where adopted; confirm identity and intent to sign.

Do consumer disclosures apply?

If the addendum governs consumer‑facing services or payments, provide ESIGN consumer disclosures, obtain consent to electronic records, and confirm the consumer can access the format.

Is notarization required for validity?

Typically not for commercial service addenda. Notarization is only required when state law or a specific transaction (e.g., real property transfer) mandates it.

What if a signer lacks authority?

If a signer lacked delegated authority, the addendum may be voidable; verify corporate delegations or obtain ratification or re‑execution by an authorized party.

How long must records be kept?

Retain executed addenda according to applicable rules: generally at least the contract term plus three years, and longer if federal or industry rules require it.

How to handle updates or amendments?

Amend by written addendum signed by authorized parties. For electronic amendments, ensure proper authentication, audit trail capture, and version control for the contract record.

Electronic Signature
Templates
Miscellaneous
Support Service Addendum

Support Service Addendum

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

SUPPORT SERVICE ADDENDUM

This Support Service Addendum (the "Addendum") forms part of and amends the agreement titled dated between the parties set forth below.

Client Name: Provider Name:

WHEREAS, Client and Provider entered into the Original Agreement to establish the terms for certain goods and services;

WHEREAS, the parties desire to define and provide discrete support services and service levels for the products and services described in the Original Agreement; and

WHEREAS, the parties agree that the terms of this Addendum will govern the provision of support services as set forth herein effective as of .

Scope of Support Services

Provider shall provide the following support services to Client during the Term described below. Services shall include routine maintenance, troubleshooting, updates, and technical assistance as reasonably necessary to maintain operability of the covered systems.

Detailed Scope (describe supported systems, components, exclusions)

Service Levels and Response Times

Support shall be provided in accordance with the following service levels. Response times are measured from Provider's receipt of a complete support request.

Standard Support Hours Initial Response Time by Priority

Critical: High: Normal:

Target Resolution Time

Payment Terms

In consideration for the support services rendered by Provider, Client shall pay Provider in accordance with the fees and schedule set forth below.

Support Fee Amount (per term or per month) Billing Schedule Payment Due and Late Fees

Payment due within days of invoice. Late payments shall incur interest at or the maximum rate permitted by law, whichever is less.

Term and Termination

This Addendum commences on and shall continue until unless earlier terminated in accordance with this Addendum or the Original Agreement.

Either party may terminate this Addendum for convenience upon days' prior written notice to the other party. Either party may terminate immediately for material breach by the other if such breach is not cured within thirty (30) days after written notice specifying the breach.

Confidentiality

Each party (the "Receiving Party") shall hold in confidence all non-public information disclosed by the other party (the "Disclosing Party") that is designated confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). The Receiving Party shall not disclose Confidential Information to any third party except to employees and contractors who have a need to know and who are bound by confidentiality obligations at least as protective as those set forth herein. Confidential Information shall not include information that: (a) is or becomes generally available to the public other than as a result of a breach of this Addendum; (b) was lawfully in the Receiving Party's possession prior to receipt from the Disclosing Party; (c) is rightfully received from a third party without restriction; or (d) is independently developed without use of the Disclosing Party's Confidential Information.

Upon termination or expiration of this Addendum, the Receiving Party shall return or destroy, at the Disclosing Party's election, all Confidential Information and certify destruction upon request. The parties acknowledge that monetary damages may be insufficient to remedy breach of confidentiality and that injunctive relief may be an appropriate remedy in addition to other available remedies.

Limitation of Liability

Except for liability arising from a party's gross negligence, willful misconduct, or breach of confidentiality, neither party shall be liable to the other for lost profits, loss of business, or consequential, incidental or punitive damages. The aggregate liability of each party for claims arising out of or in connection with this Addendum shall not exceed the fees paid by Client to Provider under this Addendum in the twelve (12) months preceding the claim.

Governing Law

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

Entire Agreement; Amendments

This Addendum, together with the Original Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings. Any amendment to this Addendum must be in writing and signed by authorized representatives of both parties.

Notices

Client Address for Notices Provider Address for Notices

CLIENT

Printed Name:

By:

Date:

PROVIDER

Printed Name:

By:

Date:

What the Support Service Addendum Is and When It Applies

A Support Service Addendum is a contractual attachment that defines post‑sale support obligations between a provider and a customer. It typically specifies service levels, response and resolution times, escalation paths, excluded services, fees for out‑of‑scope work, and notice procedures. The addendum modifies or supplements a primary service agreement and clarifies operational expectations to reduce disputes. When signed electronically it is enforceable under federal and state e‑signature laws, including the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted.

Why a Clear Addendum Matters for Service Relationships

A precise Support Service Addendum reduces operational ambiguity, limits billing disputes, and documents remedies for missed SLAs. It protects both parties by setting measurable expectations and an agreed dispute resolution path.

Who Typically Prepares and Signs a Support Service Addendum

Use this addendum where support terms are material to pricing, compliance, or service continuity.

Customer procurement and legal teams who need defined remedies and billing clarity.
Vendor account or professional services managers who will accept operational responsibilities and escalate support.
IT and operations staff who must map SLAs to monitoring and incident workflows.

Who Has Authority to Sign the Addendum

Authorized Officer

A corporate officer or contract signatory with delegated authority must sign when the agreement changes material commercial or legal terms. Confirm internal signature thresholds before routing to avoid invalid execution.

Operations Lead

A senior operations or IT director may sign for operational amendments when authorized by a board resolution or written delegation, especially for technical annexes or service level adjustments.

Required Addendum Data Elements

Parties: Full legal names

Effective Date: MM/DD/YYYY

SLA Metrics: Response / resolution times

Support Hours: Time zones and coverage

Fees: Rates and billing cycle

Termination: Notice period

Step‑by‑Step: Completing the Addendum

Follow this sequence to prepare, review, and execute the Support Service Addendum efficiently.

01

Draft: Populate parties, effective date, and SLA metrics.
02

Review: Legal and finance confirm liability and billing language.
03

Approve: Authorized signers confirm delegation and signatory authority.
04

Execute: Apply signatures and distribute final executed copies.

How to Configure an Online Signing Workflow

Set up a signing flow that enforces order, captures audit data, and verifies signer identity.

Field	Configuration
Signer Order	Sequential or parallel as needed
Authentication	Email link, SMS code, or KBA
Required Fields	Make SLA and signature fields mandatory
Notifications	Email reminders and completion receipts

Where to Send the Addendum After Signing

Route executed copies to stakeholders who will operate, audit, and bill under the addendum.

Customer: Retain a signed copy for contract management
Vendor Accounts: Update billing and contract records
Operations: Provide SLA details to support teams
Legal/Finance: Store for compliance and audit

Technical and Platform Considerations for eSigning

Choose a solution that supports your authentication needs, audit trails, and retention policies without compromising data security.

Formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Security: TLS in transit; AES-256 at rest

Key Elements to Include in a Professional Addendum

A well‑crafted Support Service Addendum addresses obligations, limits, remedies, and operational details that affect daily support delivery.

Scope of Support

Define covered systems, supported features, and specific exclusions to avoid disputes about what constitutes supported work and billable out‑of‑scope tasks.

Service Levels

Quantify response and resolution times by incident severity, with measurement windows, credit or remediation mechanisms, and reporting frequency.

Escalation Path

List escalation tiers, contact points, and expected handoff times so critical incidents move promptly to higher technical resources.

Reporting

Specify incident reporting format, regular SLA reports, and data required for dispute resolution and performance reviews.

Fees & Billing

State pricing for included support, hourly or per‑incident rates for work outside scope, and invoice/payment terms to prevent billing disagreements.

Term & Termination

Set the addendum term, renewal mechanism, notice periods, and post‑termination obligations such as data return or transition assistance.

Attachments and Technical Appendices to Include

Attach operational details and exhibits that make SLAs actionable for support teams and auditors.

Definitions

Include precise definitions of severity levels, business hours, uptime calculations, and incident categories to reduce interpretive disputes.

Contact Matrix

List primary and secondary contacts, time zone, escalation phone numbers, and email addresses for each party to ensure rapid incident handling.

Acceptance Criteria

If the addendum modifies deliverables, include measurable acceptance tests and timelines for verification and signoff.

Change Log

Track addendum revisions, amendment dates, and the authorized approver for each change to preserve contract history.

Typical Timelines and Notice Requirements

Common timing elements determine when obligations start, how notices are calculated, and when renewals or terminations must be provided.

Effective Date:

When SLAs and fees begin

Termination Notice:

Often 30–90 days written notice

SLA Measurement Window:

Monthly or quarterly reporting periods

Billing Cycle:

Net 30 typical for invoices

Renewal Notice:

60–90 days prior to renewal

Key Milestones from Draft to Support Start

A sequential milestone plan helps ensure timely approvals, signing, and operational readiness.

01

Drafting

Prepare addendum text and exhibits for internal review.

02

Internal Approval

Legal and finance approve commercial and liability terms.

03

Execution

Authorized parties sign and exchange executed copies.

04

Go‑Live

Operations onboard teams and begin monitoring to meet SLAs.

Common Mistakes When Preparing the Addendum

Vague SLA wording that lacks measurable metrics causes persistent performance disputes and inconsistent enforcement.
Omitting escalation contacts and procedures leads to delayed response on critical incidents and missed remediation targets.
Failing to align billing language with out‑of‑scope definitions produces surprise charges and payer pushback.
Neglecting signature authority verification can render the addendum unenforceable or require re‑execution.

Penalties and Risks of an Incorrect or Missing Addendum

Service Disputes: Increased litigation risk

Billing Errors: Invoice disputes and delayed payments

Regulatory Risk: Data/privacy noncompliance

Contract Voidability: Improper signatures risk invalidity

Operational Drift: Unclear responsibilities persist

Escalation Delays: Longer outage durations

eSignature Pricing Snapshot for Executing the Addendum

Compare basic pricing and feature availability when selecting an eSignature provider for routine addendum execution. Confirm current plan details with each vendor.

	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	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About Using a Support Service Addendum

Answers to common questions about enforceability, signatures, retention, and integration with core contracts.

Need help? Contact support

Can the addendum be signed electronically?
Yes. Electronic signatures are legally enforceable in interstate transactions under the ESIGN Act (15 U.S.C. ch. 96) and under UETA where adopted; confirm identity and intent to sign.
Do consumer disclosures apply?
If the addendum governs consumer‑facing services or payments, provide ESIGN consumer disclosures, obtain consent to electronic records, and confirm the consumer can access the format.
Is notarization required for validity?
Typically not for commercial service addenda. Notarization is only required when state law or a specific transaction (e.g., real property transfer) mandates it.
What if a signer lacks authority?
If a signer lacked delegated authority, the addendum may be voidable; verify corporate delegations or obtain ratification or re‑execution by an authorized party.
How long must records be kept?
Retain executed addenda according to applicable rules: generally at least the contract term plus three years, and longer if federal or industry rules require it.
How to handle updates or amendments?
Amend by written addendum signed by authorized parties. For electronic amendments, ensure proper authentication, audit trail capture, and version control for the contract record.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now