ENTERPRISE SUPPORT POLICY
(Iowa Law)
[// GUIDANCE: This Support Policy is designed as an exhibit to a Master SaaS Agreement or Subscription Agreement. It defines the support services, SLAs, and response times the Provider commits to deliver. Ensure alignment with the commercial terms in the master agreement.]
TABLE OF CONTENTS
- Document Header and Definitions
- Support Services Overview
- Support Tiers and Entitlements
- Service Level Agreements (SLAs)
- Issue Classification and Response Times
- Escalation Procedures
- Maintenance Windows and Scheduled Downtime
- Customer Responsibilities
- Exclusions and Limitations
- Remedies and Service Credits
- General Terms
- Execution and Acknowledgment
1. DOCUMENT HEADER AND DEFINITIONS
1.1 Parties
This Enterprise Support Policy ("Support Policy" or "Policy") is entered into as of [EFFECTIVE DATE] and is incorporated by reference into the Master SaaS Agreement (the "Agreement") between:
PROVIDER: [PROVIDER LEGAL NAME], a [STATE] [ENTITY TYPE] ("Provider")
CUSTOMER: [CUSTOMER LEGAL NAME], a [STATE] [ENTITY TYPE] ("Customer")
1.2 Definitions
"Authorized Users" – Customer's employees, contractors, and agents authorized to access the Service under the Agreement.
"Business Hours" – Monday through Friday, [8:00 AM to 6:00 PM] Central Time, excluding Iowa state holidays and federal holidays.
"Critical Issue" – A Severity 1 issue as defined in Section 5.
"Customer Success Manager" – The Provider representative assigned to Customer's account for strategic support and relationship management.
"Downtime" – Any period during which the Service is unavailable or materially degraded, excluding Scheduled Maintenance and Force Majeure events.
"First Response Time" – The elapsed time between Customer's submission of a support request and Provider's initial acknowledgment.
"Resolution Time" – The elapsed time between Customer's submission of a support request and Provider's delivery of a fix, workaround, or resolution.
"Scheduled Maintenance" – Planned maintenance windows communicated in advance per Section 7.
"Service" – The software-as-a-service platform provided under the Agreement.
"Service Level Agreement" or "SLA" – The performance commitments set forth in Section 4.
"Support Portal" – Provider's online support system at [URL] for submitting and tracking support requests.
"Support Request" or "Ticket" – A formal request for technical assistance submitted through authorized channels.
"Uptime" – The percentage of time the Service is available, calculated as: ((Total Minutes in Month – Downtime Minutes) / Total Minutes in Month) × 100.
2. SUPPORT SERVICES OVERVIEW
2.1 Scope of Support
Provider shall provide the following support services to Customer:
| Support Component | Description |
|---|---|
| Technical Support | Assistance with Service functionality, configuration, and troubleshooting |
| Bug Resolution | Investigation and remediation of software defects |
| Service Monitoring | 24/7 monitoring of Service infrastructure and performance |
| Incident Management | Coordinated response to service disruptions |
| Account Management | Dedicated Customer Success Manager for Enterprise customers |
| Knowledge Base Access | Self-service documentation, FAQs, and tutorials |
| Release Management | Notification and support for new features and updates |
2.2 Support Channels
| Channel | Availability | Best For |
|---|---|---|
| Support Portal | 24/7 | All support requests (required for tracking) |
| 24/7 submission; Business Hours response | Non-urgent inquiries | |
| Phone Hotline | Business Hours (or 24/7 for Severity 1) | Urgent issues, escalations |
| Live Chat | Business Hours | Quick questions, status updates |
| Dedicated Slack/Teams Channel | Business Hours (Enterprise only) | Real-time collaboration |
Contact Information:
- Support Portal: [URL]
- Email: [[email protected]]
- Phone: [1-800-XXX-XXXX]
- Emergency Hotline (Severity 1): [1-800-XXX-XXXX]
3. SUPPORT TIERS AND ENTITLEMENTS
3.1 Support Tier Comparison
| Feature | Standard | Premium | Enterprise |
|---|---|---|---|
| Support Hours | Business Hours | Extended (6 AM–10 PM CT) | 24/7/365 |
| Severity 1 Response | 4 hours | 1 hour | 15 minutes |
| Severity 2 Response | 8 hours | 4 hours | 1 hour |
| Severity 3 Response | 24 hours | 8 hours | 4 hours |
| Severity 4 Response | 72 hours | 24 hours | 8 hours |
| Phone Support | Business Hours | Extended Hours | 24/7 |
| Dedicated CSM | No | Shared | Dedicated |
| Quarterly Business Reviews | No | Annual | Quarterly |
| Custom Training | No | 2 hours/year | 8 hours/year |
| Uptime SLA | 99.5% | 99.9% | 99.95% |
| Service Credits | No | Yes | Yes (enhanced) |
3.2 Customer's Support Tier
☐ Standard Support
☐ Premium Support
☐ Enterprise Support
Selected Tier: [TIER NAME]
[// GUIDANCE: Check the applicable box and specify the tier. Ensure pricing in the Agreement reflects the selected tier.]
4. SERVICE LEVEL AGREEMENTS (SLAs)
4.1 Uptime Commitment
Provider commits to the following monthly Uptime percentages:
| Support Tier | Uptime Commitment | Maximum Monthly Downtime |
|---|---|---|
| Standard | 99.5% | ~3 hours 39 minutes |
| Premium | 99.9% | ~43 minutes |
| Enterprise | 99.95% | ~22 minutes |
Customer's Uptime SLA: [XX.XX]%
4.2 Uptime Calculation
- Measurement Period: Calendar month
- Measurement Method: Provider's monitoring systems
- Exclusions from Downtime:
- Scheduled Maintenance (per Section 7)
- Customer-caused issues (misconfiguration, unauthorized modifications)
- Third-party service outages outside Provider's control
- Force Majeure events
- Connectivity issues on Customer's network
- Features designated as "Beta" or "Preview"
4.3 Uptime Reporting
Provider shall make uptime statistics available via:
- Real-time status page at [status.provider.com]
- Monthly uptime reports delivered within [5] Business Days after month-end
- Annual uptime summary in Quarterly Business Reviews
5. ISSUE CLASSIFICATION AND RESPONSE TIMES
5.1 Severity Definitions
| Severity | Definition | Examples |
|---|---|---|
| Severity 1 (Critical) | Service is completely unavailable or a critical business function is inoperable with no workaround | Complete outage; data loss; security breach; authentication failure for all users |
| Severity 2 (High) | Major functionality is impaired; significant business impact; workaround may exist but is inadequate | Core feature failure affecting multiple users; severe performance degradation; data integrity concerns |
| Severity 3 (Medium) | Moderate impact; non-critical functionality affected; reasonable workaround exists | Minor feature malfunction; intermittent issues; non-blocking errors |
| Severity 4 (Low) | Minimal impact; cosmetic issues; general questions; enhancement requests | UI display issues; documentation questions; feature requests |
5.2 Response Time Commitments
| Severity | Standard | Premium | Enterprise |
|---|---|---|---|
| Severity 1 | 4 Business Hours | 1 hour (24/7) | 15 minutes (24/7) |
| Severity 2 | 8 Business Hours | 4 Business Hours | 1 hour (24/7) |
| Severity 3 | 24 Business Hours | 8 Business Hours | 4 Business Hours |
| Severity 4 | 72 Business Hours | 24 Business Hours | 8 Business Hours |
5.3 Resolution Time Targets
| Severity | Target Resolution Time | Maximum Resolution Time |
|---|---|---|
| Severity 1 | 4 hours | 8 hours (or continuous effort until resolved) |
| Severity 2 | 24 hours | 72 hours |
| Severity 3 | 5 Business Days | 10 Business Days |
| Severity 4 | Best effort | Next scheduled release |
[// GUIDANCE: Resolution times are targets, not guarantees. Service credits are typically tied to response time SLAs, not resolution times.]
5.4 Severity Classification Authority
- Customer may propose initial severity classification
- Provider may reclassify after initial assessment with documented justification
- Disputes over classification shall be escalated per Section 6
6. ESCALATION PROCEDURES
6.1 Internal Escalation Matrix
| Escalation Level | Trigger | Provider Contact | Response |
|---|---|---|---|
| Level 1 | Initial contact | Support Engineer | Ticket acknowledgment and triage |
| Level 2 | Severity 1 or 2; or missed SLA | Senior Support Engineer | Active investigation; status updates every [1/2] hours |
| Level 3 | Unresolved after [4/8] hours | Support Manager | Management oversight; additional resources |
| Level 4 | Unresolved after [24] hours; or Customer request | Director of Support / VP Engineering | Executive involvement; priority allocation |
| Level 5 | Critical business impact; contractual escalation | C-Level Executive | Direct executive engagement |
6.2 Customer Escalation Contacts
Customer may initiate escalation by contacting:
| Level | Contact | Phone | |
|---|---|---|---|
| Support Manager | [NAME] | [PHONE] | [EMAIL] |
| Director of Support | [NAME] | [PHONE] | [EMAIL] |
| VP Customer Success | [NAME] | [PHONE] | [EMAIL] |
| Executive Sponsor | [NAME] | [PHONE] | [EMAIL] |
6.3 Escalation Best Practices
- Always reference the Ticket number when escalating
- Provide business impact context and urgency justification
- Include relevant stakeholders on communications
- Document all escalation interactions in the Support Portal
7. MAINTENANCE WINDOWS AND SCHEDULED DOWNTIME
7.1 Scheduled Maintenance
Standard Maintenance Window: [Sundays, 2:00 AM – 6:00 AM Central Time]
- Provider shall provide [72] hours' advance notice for standard maintenance
- Maintenance during this window does not count toward Downtime
7.2 Emergency Maintenance
Provider may perform emergency maintenance without advance notice when necessary to:
- Address security vulnerabilities
- Prevent imminent service degradation
- Comply with legal or regulatory requirements
Provider shall notify Customer as soon as reasonably practicable and provide a post-incident summary within [24] hours.
7.3 Major Upgrades
For major version upgrades or significant infrastructure changes:
- [14] days' advance notice minimum
- Release notes and migration documentation provided
- Optional sandbox/staging environment access for testing
- Rollback plan documented and available upon request
8. CUSTOMER RESPONSIBILITIES
8.1 Support Request Requirements
Customer shall:
- Submit all support requests through the Support Portal (required for SLA tracking)
- Provide complete information including: error messages, screenshots, steps to reproduce, affected users, business impact
- Designate [2-5] authorized support contacts ("Named Contacts")
- Respond to Provider requests for additional information within [1] Business Day
8.2 Named Support Contacts
| Contact | Name | Phone | Role | |
|---|---|---|---|---|
| Primary | [NAME] | [EMAIL] | [PHONE] | [ROLE] |
| Secondary | [NAME] | [EMAIL] | [PHONE] | [ROLE] |
| Technical | [NAME] | [EMAIL] | [PHONE] | [ROLE] |
8.3 Environment Requirements
Customer shall:
- Maintain supported browser versions and operating systems
- Ensure adequate internet connectivity
- Apply Customer-side updates and patches as recommended
- Maintain accurate user and configuration data
8.4 Security Cooperation
Customer shall:
- Promptly report suspected security incidents
- Cooperate with security investigations
- Maintain confidentiality of access credentials
- Follow Provider's security guidelines and recommendations
9. EXCLUSIONS AND LIMITATIONS
9.1 Excluded from Support
The following are not covered under this Support Policy:
- Issues caused by Customer's modification of the Service (unless authorized in writing)
- Issues arising from Customer's use of unsupported browsers, devices, or integrations
- Third-party software, hardware, or services not provided by Provider
- Customer's failure to implement recommended updates or configurations
- Issues arising from Customer's violation of the Agreement or Acceptable Use Policy
- Training on basic functionality (unless included in support tier)
- Custom development, integrations, or consulting services (separate engagement required)
- Data recovery due to Customer-caused deletion (unless backup services are included)
9.2 Out-of-Scope Requests
Requests outside the scope of this Policy may be addressed through:
- Professional Services engagement (separate SOW and fees)
- Training services
- Consulting services
- Custom development agreements
Provider will notify Customer when a request is out of scope and provide options for engagement.
10. REMEDIES AND SERVICE CREDITS
10.1 Service Credit Eligibility
If Provider fails to meet the Uptime SLA in any calendar month, Customer is entitled to Service Credits as follows:
| Monthly Uptime | Service Credit (% of Monthly Fees) |
|---|---|
| 99.0% – 99.9% (Premium/Enterprise) | 10% |
| 98.0% – 98.99% | 25% |
| 95.0% – 97.99% | 50% |
| Below 95.0% | 100% |
10.2 Service Credit Request Process
- Customer must submit a Service Credit request within [30] days after the end of the affected month
- Request must include: dates and times of Downtime, Ticket numbers, business impact
- Provider will validate the claim within [15] Business Days
- Approved credits will be applied to the next invoice (or refunded if no renewal)
10.3 Service Credit Limitations
- Maximum Service Credits per month: [100]% of monthly fees for the affected Service
- Service Credits are Customer's sole and exclusive remedy for Uptime SLA failures
- Service Credits do not apply to free tiers, trials, or beta features
- Service Credits are not transferable and have no cash value except upon termination
10.4 Termination for Chronic Failure
If Provider fails to meet the Uptime SLA for [3] consecutive months or [4] months in any [12]-month period, Customer may terminate the affected Services upon [30] days' written notice and receive a pro-rata refund of prepaid fees.
11. GENERAL TERMS
11.1 Governing Law and Venue
This Support Policy shall be governed by and construed in accordance with the laws of the State of Iowa, without regard to conflict of laws principles. Exclusive venue for any dispute shall be the state or federal courts located in Polk County (Des Moines), Iowa.
11.2 Jury Waiver
TO THE FULLEST EXTENT PERMITTED BY IOWA LAW, EACH PARTY HEREBY WAIVES ANY RIGHT TO TRIAL BY JURY IN ANY ACTION ARISING OUT OF OR RELATING TO THIS SUPPORT POLICY OR THE AGREEMENT.
Party Initials: Customer _______ Provider _______
11.3 Electronic Signatures
This Support Policy may be executed electronically in accordance with the Iowa Uniform Electronic Transactions Act (Iowa Code § 554D.101 et seq.).
11.4 Data Breach Notification
In the event of a security breach involving Customer's data, Provider shall comply with Iowa's data breach notification requirements under Iowa Code § 715C.1 et seq. and notify Customer within [48] hours of discovery.
11.5 Trade Secret Protection
Any trade secrets or confidential business information disclosed in connection with this Support Policy shall be protected in accordance with the Iowa Trade Secrets Act (Iowa Code § 550.1 et seq.).
11.6 Modifications
Provider may update this Support Policy upon [30] days' written notice. Material changes reducing support levels require Customer's consent for existing subscriptions.
11.7 Relationship to Agreement
This Support Policy is incorporated into and subject to the terms of the Agreement. In the event of conflict, the Agreement controls unless this Policy expressly states otherwise.
11.8 Entire Support Agreement
This Support Policy, together with the Agreement and any applicable Order Forms, constitutes the entire agreement regarding support services.
12. EXECUTION AND ACKNOWLEDGMENT
By signing below, the Parties acknowledge receipt and acceptance of this Enterprise Support Policy.
| CUSTOMER | PROVIDER |
|---|---|
| [CUSTOMER LEGAL NAME] | [PROVIDER LEGAL NAME] |
| By: __________________________ | By: __________________________ |
| Name: ________________________ | Name: ________________________ |
| Title: _______________________ | Title: _______________________ |
| Date: ________________________ | Date: ________________________ |
JURY WAIVER ACKNOWLEDGMENT:
| Customer Initials: _______ | Provider Initials: _______ |
EXHIBIT A – NAMED SUPPORT CONTACTS
| # | Name | Phone | Role | Authority Level | |
|---|---|---|---|---|---|
| 1 | [NAME] | [EMAIL] | [PHONE] | [ROLE] | Full |
| 2 | [NAME] | [EMAIL] | [PHONE] | [ROLE] | Full |
| 3 | [NAME] | [EMAIL] | [PHONE] | [ROLE] | Limited |
EXHIBIT B – SUPPORTED ENVIRONMENTS
Browsers
- Google Chrome (latest 2 major versions)
- Mozilla Firefox (latest 2 major versions)
- Microsoft Edge (Chromium-based, latest 2 major versions)
- Safari (latest 2 major versions)
Operating Systems
- Windows 10/11
- macOS 12+
- iOS 15+
- Android 12+
Integrations
- [LIST SUPPORTED INTEGRATIONS]
EXHIBIT C – HOLIDAY SCHEDULE
The following holidays are excluded from Business Hours calculations:
- New Year's Day
- Martin Luther King Jr. Day
- Presidents' Day
- Memorial Day
- Independence Day
- Labor Day
- Thanksgiving Day
- Day after Thanksgiving
- Christmas Eve
- Christmas Day
END OF SUPPORT POLICY
Do more with Ezel
This free template is just the beginning. See how Ezel helps legal teams draft, research, and collaborate faster.
AI that drafts while you watch
Tell the AI what you need and watch your document transform in real-time. No more copy-pasting between tools or manually formatting changes.
- Natural language commands: "Add a force majeure clause"
- Context-aware suggestions based on document type
- Real-time streaming shows edits as they happen
- Milestone tracking and version comparison
Research and draft in one conversation
Ask questions, attach documents, and get answers grounded in case law. Link chats to matters so the AI remembers your context.
- Pull statutes, case law, and secondary sources
- Attach and analyze contracts mid-conversation
- Link chats to matters for automatic context
- Your data never trains AI models
Search like you think
Describe your legal question in plain English. Filter by jurisdiction, date, and court level. Read full opinions without leaving Ezel.
- All 50 states plus federal courts
- Natural language queries - no boolean syntax
- Citation analysis and network exploration
- Copy quotes with automatic citation generation
Ready to transform your legal workflow?
Join legal teams using Ezel to draft documents, research case law, and organize matters — all in one workspace.