Can the menu be signed electronically?

Yes. Under the ESIGN Act and UETA, electronic signatures are enforceable when intent, consent, attribution, and retention are demonstrable. Ensure consumer disclosures when required and preserve an audit trail showing signer identity and timestamp.

Who should sign the menu?

An authorized signer from both provider and client should sign; this is typically procurement, finance, or an operations executive. Confirm the signer has contracting authority to avoid challenges to enforceability.

Is notarization required?

Not generally for commercial service menus. If state law or specific contractual clauses require notarization or witness execution, follow those rules and note any RON requirements that vary by state.

How do I correct errors after signing?

Avoid unilateral edits to a signed copy. Prepare a signed amendment or addendum that references the original menu, states the correction, and is signed by the same authorized parties.

What supporting documents attach to the menu?

Attach rate schedules, scope exhibits, escalation contacts, and any required compliance addenda such as HIPAA BAAs so the menu and attachments form a complete operational reference.

How often must the menu be updated?

Review pricing, SLAs, and service availability at least annually or when material changes occur. Record effective dates and keep prior versions for recordkeeping and dispute resolution.

Support Services Menu

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

SUPPORT SERVICES MENU

This Support Services Menu (the "Menu") is entered into effective as of by and between:

Client Name Client Address Provider Name Provider Address

RECITALS

WHEREAS, Client requires certain technical and non-technical support services to maintain, operate and optimize Client systems and business operations; and

WHEREAS, Provider is qualified and able to provide professional support services, and agrees to provide such services according to the terms and pricing set forth in this Menu; and

WHEREAS, the parties intend this Menu to define the scope, schedule, fees and additional terms that shall be incorporated by reference into the underlying Services Agreement between the parties.

SCOPE OF WORK

Provider shall perform the support services selected in the services menu below and any ancillary tasks reasonably necessary to deliver those services. Services shall be performed in a professional manner consistent with industry standards and in accordance with the service levels set forth in this Menu.

Detailed Scope (describe deliverables, response times, exclusions)

SUPPORT SERVICES MENU / RATES

Select the services to be provided and record the agreed rate and frequency. Unless otherwise stated, rates are exclusive of applicable taxes and travel expenses.

Help Desk / Remote Support Description

Onsite Support / Break-Fix Description

Remote Monitoring & Maintenance Description

Custom Services / Projects Project Description

PAYMENT TERMS

Client shall pay Provider the fees specified in the selected items of this Menu. Payments shall be made in accordance with the billing schedule selected for each service. Unless otherwise agreed in writing, invoices are due within days of invoice date.

Primary Billing Contact

Late payments will incur a late fee of % per month on the outstanding balance, or the maximum allowable by law, whichever is less. Provider may suspend services for Client accounts that are more than days past due following written notice.

TERM AND TERMINATION

This Menu commences on and, unless earlier terminated, continues until (the "Term"). Either party may terminate this Menu for convenience upon days' prior written notice. Either party may terminate immediately for material breach if the breaching party fails to cure within 15 days of written notice of such breach.

CONFIDENTIALITY

"Confidential Information" means non-public information disclosed by one party to the other, whether oral, written or electronic, including business, technical and financial information. The receiving party shall (i) use Confidential Information solely to perform its obligations under this Menu, (ii) restrict disclosure to employees and contractors with a need to know, and (iii) exercise at least the same degree of care to protect Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care.

Confidential obligations do not apply to information that: (a) is or becomes publicly known through no breach by the receiving party, (b) is rightfully received from a third party without restriction, (c) is independently developed without use of Confidential Information, or (d) is required to be disclosed by law, provided the disclosing party is given prompt notice and a reasonable opportunity to seek protective measures.

Confidentiality Survival (years)

INDEMNIFICATION & LIMITATION OF LIABILITY

Each party shall indemnify and hold harmless the other party from third-party claims arising from its breach of this Menu or from its negligence or willful misconduct. EXCEPT FOR A PARTY'S INDEMNIFICATION OBLIGATIONS OR BREACH OF CONFIDENTIALITY, NEITHER PARTY SHALL BE LIABLE FOR CONSEQUENTIAL, INCIDENTAL, SPECIAL OR PUNITIVE DAMAGES. THE AGGREGATE LIABILITY OF EITHER PARTY FOR ANY CLAIM ARISING OUT OF OR RELATING TO THIS MENU SHALL NOT EXCEED THE AMOUNTS PAID OR PAYABLE BY CLIENT TO PROVIDER UNDER THIS MENU DURING THE 12 MONTHS PRECEDING THE CLAIM.

GOVERNING LAW

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

ENTIRE AGREEMENT; AMENDMENTS

This Menu, together with the underlying Services Agreement between the parties, constitutes the entire agreement with respect to the subject matter contained herein and supersedes all prior and contemporaneous agreements, proposals and communications. Any amendment or modification to this Menu must be made in writing and signed by authorized representatives of both parties.

NOTICES

All notices required or permitted under this Menu shall be in writing and delivered to the addresses provided above or to any updated address provided in writing. Notices shall be deemed given when delivered in person, by certified mail, or by nationally recognized overnight courier.

CHANGE ORDERS

Any change to the scope, fees, or schedule set forth in this Menu shall be implemented only by a written change order signed by authorized representatives of both parties. Unless a change order expressly states otherwise, Provider shall not be obligated to perform additional services for which fees have not been agreed in writing.

Client:

By:

Date:

Provider:

By:

Date:

What the Support Services Menu Is

A Support Services Menu is a formal, itemized schedule that lists available support services, deliverables, response levels, and associated fees. It organizes service categories, standard tasks, service level targets, exclusions, and pricing so internal teams and external clients can compare options and confirm expectations before work begins. The menu can be attached to contracts, statements of work, or procurement documents and serves as the authoritative reference for ordering, invoicing, and performance measurement across support engagements.

Why a Clear Support Services Menu Matters

A well‑structured menu reduces ambiguity about scope, pricing, and response times, improves billing accuracy, and supports consistent service delivery across teams. It makes approvals and procurement more efficient and helps manage client expectations without altering the underlying contract terms.

Who Typically Completes or Uses a Support Services Menu

Teams that prepare or approve a Support Services Menu often include procurement, IT or service operations, account management, and client legal or finance staff.

Procurement and sourcing teams who compare options and set purchase orders.
Service operations managers who implement SLAs and assign resources.
Client account or finance contacts who review fees and billing terms.

Use the menu as a single source of truth for service offerings, approval routing, and invoice validation between provider and customer.

Who Signs or Authorizes the Menu

Operations Manager

The operations manager or head of service delivery typically reviews content for accuracy and confirms operational commitments, including staffing and response targets, before routing for financial or executive signoff.

Client Authorized Signer

An authorized signatory from the client side—often procurement, legal, or finance—must accept the menu when it binds billing or service level commitments; their signature confirms acceptance of fees and terms.

Required Data Elements on the Menu

Service Code: Alphanumeric code for billing and tracking

Service Description: Concise task and deliverable summary

Rate or Fee: Hourly, monthly, or fixed amount

SLA / Response: Response and resolution timeframes

Billing Terms: Billing frequency and invoice rules

Signatory Block: Name, title, date, and contact

Penalties and Risks of an Incorrect Menu

Billing Disputes: Delayed payment or credits

Contract Misinterpretation: Scope creep and scope disputes

Compliance Failure: HIPAA or privacy exposure

Regulatory Fines: Potential penalties for recordkeeping lapses

Operational Delays: Resource misallocation and missed SLAs

Reputational Harm: Client relationship degradation

Common Mistakes to Avoid

Using vague descriptions such as reasonable support without measurable response or resolution targets.
Failing to specify billing increments and rounding rules, which leads to inconsistent invoices.
Listing services without required dependencies or prerequisites, causing scope disputes during delivery.
Neglecting to align signatory authority with contract signature blocks, creating enforceability gaps.

Step-by-Step: Preparing and Finalizing the Support Services Menu

Use this sequence to create, review, and publish a menu so it aligns with contract terms and billing systems.

01

Draft services: List each service, deliverable, and exclusion clearly
02

Set pricing: Specify rates, billing increments, and minimums
03

Define SLAs: Attach measurable response and resolution targets
04

Approve and sign: Collect required signatures and record the approved version

How to Configure the Menu for Online Completion

Configure fields and approval routing so the menu can be completed, signed, and archived electronically while preserving an audit trail.

Field	Configuration
Service line items	Use repeatable table fields for multiple services
Conditional fields	Show pricing or SLA fields only when applicable
Approval routing	Sequential or parallel signer order with reminders
Audit and storage	Capture timestamp, signer identity, and PDF output

Where to Send or File the Completed Menu

A finalized menu should be saved with the contract, distributed to finance and operations, and retained in the document management system for auditability.

Contract folder: Attach signed menu to the master contract record
Billing system: Import service codes and rates into invoicing
Operations: Share SLAs and delivery notes with support teams
Client delivery: Provide the signed menu copy to client contacts

Digital Signing and eSubmission Requirements

When completing a Support Services Menu electronically, ensure the signing platform supports required authentication, audit logs, and export formats.

Authentication: Email, SMS code, or higher assurance methods
Audit Trail: Timestamp, IP address, and signer actions
File Formats: Support for PDF and DOCX archival

Timelines, Deadlines, and Typical Processing Expectations

Establish clear internal deadlines for drafting, review cycles, signoff, and incorporation into billing systems; typical times vary by organizational process and complexity.

Drafting window:

1–5 business days depending on complexity

Internal review:

2–7 business days for legal and finance review

Client approval:

Varies; allow 5–10 business days for external signoff

Billing onboarding:

1–3 billing cycles to fully integrate new codes

Annual updates:

Review and refresh pricing and SLAs at least yearly

Support Services Menu Versus a Service Level Agreement

Compare the menu and an SLA to determine which document governs pricing, which handles legal terms, and how they should reference each other.

Criteria	Support Services Menu	Service Level Agreement
Purpose	price list and options	legal commitments and remedies
Detail level	line items and rates	performance metrics and penalties
Signature needed	yes, for billing effect	yes, for binding obligations
Amendment	easily updated by addendum	often requires contract amendment

eSignature Vendor Pricing Comparison for Menu Signing

Common eSignature plans differ by starting price, available features for bulk sending, audit capabilities, HIPAA support, and envelope or usage caps.

	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 vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes (Business Premium+)	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Key Milestones and Processing Stages

Track milestones from draft to archival so stakeholders know when the menu becomes effective and when updates are required.

01

Draft and Review

Create initial draft and route for legal and finance review

02

Client Approval

Collect client acceptance and authorized signature

03

Integration

Load service codes and rates into billing systems

04

Periodic Review

Annual or contractually required updates to pricing and SLAs

Best Practices for Accurate and Efficient Menus

Follow these practices to reduce disputes, speed approvals, and keep billing aligned with delivery.

Use clear measurable SLAs

Define response and resolution times by priority level and describe measurement methods, time zone conventions, and business hours so expectations are unambiguous and auditable.

Standardize service codes

Adopt a consistent code format and maintain a master list in the billing system to prevent mismatches between invoices and signed menus.

Version control

Stamp menus with version numbers and effective dates and preserve prior signed versions to document historical pricing and commitments for audits or disputes.

Align signatures with authority

Confirm signers have contractually delegated authority and capture signing dates and titles to ensure enforceability against corporations and public entities.

FAQs About the Support Services Menu

Answers to common questions about signing, updating, and enforcing a Support Services Menu.

Need help? Contact support

Can the menu be signed electronically?
Yes. Under the ESIGN Act and UETA, electronic signatures are enforceable when intent, consent, attribution, and retention are demonstrable. Ensure consumer disclosures when required and preserve an audit trail showing signer identity and timestamp.
Who should sign the menu?
An authorized signer from both provider and client should sign; this is typically procurement, finance, or an operations executive. Confirm the signer has contracting authority to avoid challenges to enforceability.
Is notarization required?
Not generally for commercial service menus. If state law or specific contractual clauses require notarization or witness execution, follow those rules and note any RON requirements that vary by state.
How do I correct errors after signing?
Avoid unilateral edits to a signed copy. Prepare a signed amendment or addendum that references the original menu, states the correction, and is signed by the same authorized parties.
What supporting documents attach to the menu?
Attach rate schedules, scope exhibits, escalation contacts, and any required compliance addenda such as HIPAA BAAs so the menu and attachments form a complete operational reference.
How often must the menu be updated?
Review pricing, SLAs, and service availability at least annually or when material changes occur. Record effective dates and keep prior versions for recordkeeping and dispute resolution.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now