Establishing secure connection…Loading editor…Preparing document…

Emergency Services E911 Disclaimer

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

Emergency Services E911 Disclaimer

Recitals

WHEREAS, Service Provider: provides communications, voice, data and related services (the Services) that may be used to place emergency calls to public safety answering points ("PSAPs");

WHEREAS, Customer: requests such Services and acknowledges the technical and operational limitations of emergency calling features, including E911 location delivery;

WHEREAS, the parties intend that Customer expressly acknowledge, accept, and document the limitations and responsibilities associated with using the Services for emergency calls.

Scope of Work

Emergency Services (E911) Acknowledgement and Disclaimer

Customer acknowledges that certain Services deliver emergency calls to PSAPs using E911 protocols that rely on the Customer's registered service address and may also rely on network-based or device-based location information. The accuracy, availability, and delivery of location information to emergency responders are subject to technical limitations, third-party network constraints and PSAP capabilities.

Registered Service Address:

By checking the box below, Customer expressly acknowledges and agrees to the following statements and releases Service Provider from liability as set forth herein.

Customer acknowledges that emergency calling capability may be impaired or unavailable during power outages, network outages, or if the registered service address is not current or cannot be validated.

Customer acknowledges that using VoIP, wireless, softphone, remote-worker or similar services can result in inaccurate or unavailable automatic location information and that PSAPs may receive limited data.

Customer understands that it is solely responsible for keeping the Registered Service Address and any device location information up to date and must notify Service Provider immediately in writing of any change.

Customer consents to Service Provider transmitting Registered Service Address and available location data to PSAPs, law enforcement, and emergency responders as necessary to facilitate emergency response.

Customer hereby releases and agrees to indemnify, defend and hold Service Provider harmless from and against any claim, loss, liability or expense arising out of: (a) inaccurate or incomplete location information provided by Customer; (b) any delay in the routing of emergency calls; (c) PSAP inability to receive or use location information; and (d) any loss or damage resulting from reliance on emergency services provided through third parties.

Payment Terms

All fees are due according to the Payment Schedule. Late payments shall incur the Late Fee as specified above and Service Provider may suspend Services for nonpayment after providing written notice in accordance with the Termination section.

Term and Termination

Term Start Date:

Term End Date:

Either party may terminate this Agreement for material breach if the breaching party fails to cure the breach within the notice period specified above, or immediately for cause where required by law. Termination shall not relieve Customer of payment obligations incurred prior to termination. Provisions intended to survive termination, including the E911 Acknowledgement, Indemnity and Confidentiality clauses, shall survive termination.

Confidentiality

Each party shall protect the other's Confidential Information with the same degree of care it uses to protect its own confidential information, but no less than reasonable care. Confidential Information shall not include information that is publicly known through no fault of the receiving party, independently developed without use of Confidential Information, or required to be disclosed by law, provided the disclosing party is given prompt notice and an opportunity to seek protective measures.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to choice of law principles. Exclusive jurisdiction for disputes arising under this Agreement shall be vested in the state and federal courts located in that State.

Entire Agreement

This Agreement, including any attachments and written exhibits executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes all prior or contemporaneous communications, proposals, and agreements, whether oral or written. No amendment or modification shall be effective unless in writing and signed by duly authorized representatives of both parties.

Acknowledgement

By signing below, the undersigned represent and warrant that they are authorized to execute this Agreement on behalf of the party for which they sign, that they have read and understand the E911 Disclaimer and related clauses, and that they accept and agree to be bound by all terms and conditions set forth herein.

Service Provider:

By:

Date:

Customer:

By:

Date:

Enter text✕

What the Emergency Services E911 Disclaimer Is

An Emergency Services E911 Disclaimer is a short, written acknowledgment that explains limitations and requirements when calling or routing emergency services via electronic systems. It clarifies caller location accuracy, device routing behavior, and whether an automated or third-party service may be involved. The disclaimer is used by service providers, IT administrators, and end users to document expectations about emergency call handling and to reduce confusion about liability, response time, and technical constraints when traditional 911 routing is altered or augmented by internet-based or hosted voice services.

Why including a clear E911 Disclaimer matters

A concise E911 Disclaimer sets clear expectations for callers about how location and routing are handled, reduces legal ambiguity, and supports compliance with public safety and consumer disclosure obligations under federal and state frameworks. It helps organizations document warnings and operational limits that impact emergency response.

Why including a clear E911 Disclaimer matters

Who typically issues or accepts an E911 Disclaimer

Organizations and individuals that modify or provide telephony, hosted voice, or location-based services commonly use an E911 Disclaimer to document emergency-routing limitations and user responsibilities.

  • Telecommunications providers and VoIP vendors that route calls via managed IP networks and need to inform subscribers of location accuracy limits.
  • IT administrators and managed service providers configuring softphones, remote desktop voice, or distributed office solutions where caller location may not be precise.
  • End users and employees signing up for hosted voice services, temporary hot spots, or remote desk setups requiring acknowledgment of emergency call constraints.

Use the disclaimer as part of onboarding, account settings, or device configuration so callers receive the information before relying on the service for emergency calls.

Step-by-step: Add and present an E911 Disclaimer

Follow these steps to create, attach, and present an Emergency Services E911 Disclaimer so users see it before relying on a communications service.

  • 01
    Draft text: Create a plain-language disclaimer stating location limits and routing behavior.
  • 02
    Placement: Add to account signup, device setup, and service terms where callers will see it.
  • 03
    Acknowledgment: Require explicit consent or checkbox before enabling voice/911 features.
  • 04
    Recordkeeping: Retain signed or stored acknowledgments for compliance and audits.

How to configure online delivery and capture

Typical configuration settings for presenting and capturing an E911 Disclaimer during account provisioning or device setup.

Field Configuration
Display Location Account signup page or device onboarding
Required Action Mandatory checkbox with timestamp
Authentication Email + IP capture; optional SMS code
Storage Encrypted record retention with audit trail

Technical and integration considerations

Ensure your platform can display the disclaimer consistently, capture signer metadata, and store records securely for retention and audits.

  • Signature capture: Support typed or click-to-accept methods
  • Audit data: Record timestamp, IP, and account ID
  • Storage security: Encrypt records at rest and in transit

Verify integrations with CRM, identity providers, or ticketing systems so acknowledgments are linked to user accounts and available for compliance reviews and incident response.

The typical lifecycle of an E911 Disclaimer record

A simple lifecycle shows how a disclaimer is shown, accepted, stored, and used during an emergency support event.

  • Presentation: Shown during signup or device activation
  • Consent: User checks acknowledgment and signs
  • Storage: Saved to encrypted logs with metadata
  • Use: Referenced by support or PSAP during incidents

Core elements to include in a professional E911 Disclaimer

Design the disclaimer to be concise, readable, and actionable so users understand limits and responsibilities without legalese.

Scope

State clearly which services or devices the disclaimer covers and whether it applies to mobile, desk, or remote setups.

Location accuracy

Explain that location may be approximate, user-provided, or determined by network data and may not match PSAP expectations.

Routing behavior

Describe how emergency calls are routed, whether via native PSTN, VoIP, third-party gateways, or PSAP gateways.

User obligations

List steps users should take, such as updating declared address and informing emergency services if location is uncertain.

Limitations and liability

Provide a neutral statement of service limits and where the provider’s responsibilities end regarding call delivery and location accuracy.

Retention and contact

Note how the acknowledgment is stored, who to contact for corrections, and how to revoke consent if allowed.

Essential metadata and security fields

Signer Name: Full legal name
Account ID: Internal unique ID
Device Identifier: MAC or device ID
Timestamp: ISO 8601 timestamp
IP Address: Originating IP for attribution
Storage Flag: Encrypted at rest

Risks of missing or incorrect E911 disclaimers

Regulatory exposure: State fines or PSAP complaints
Operational delays: Slower emergency response
Liability disputes: Increased litigation risk
Service interruptions: Blocked or limited 911 access
Reputational harm: Customer trust erosion
Audit failures: Noncompliance findings

Common mistakes to avoid when preparing a disclaimer

  • Using vague or legalistic language that users do not understand increases the chance they will ignore key safety instructions and misreport locations.
  • Failing to capture signer metadata (timestamp, IP, account) makes it difficult to attribute consent or defend compliance in audits or incidents.
  • Presenting the disclaimer after enabling voice features instead of before consenting undermines the legal basis for consumer notice and may violate ESIGN requirements.
  • Not updating the disclaimer when routing or location technology changes can leave records inconsistent and expose the provider to regulatory or contractual claims.

When to present and renew the disclaimer

Timing matters: disclose during setup, capture at first use, and refresh when location or routing configuration changes.

Initial presentation:

Show at signup or first activation before enabling emergency call features

Re-presentation trigger:

Required when declared address or routing method changes

Periodic review:

Review wording annually or when regulations change

Incident-driven update:

Update after any PSAP or regulatory complaint

Retention start:

Retention begins on the effective date captured

Pricing and feature comparison for eSignature options used with disclaimers

Typical vendor pricing and feature availability for platforms that capture and retain signed acknowledgments. signNow appears first for consistency.

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 Yes, trial available Yes, trial available Yes, trial available Yes, trial available
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Common questions about Emergency Services E911 Disclaimers

Answers to frequently raised issues about legal validity, electronic capture, and practical steps for presenting and storing E911 disclaimers.


Need help? Contact support

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