Voice AI Terms of Service
Review draft · not effective. Professional review and factual verification pending.
Contents
- Status, parties and agreement
- Service scope and authorized users
- Accounts and access
- Permitted and prohibited use
- Customer content and configuration
- AI limitations and human review
- Obligations toward callers
- Providers, maintenance and availability
- Data rights, intellectual property and license
- Confidentiality and security
- Commercial terms and changes
- Suspension and termination
- Export, deletion and end of service
- Liability allocation
- Proposed proportionate indemnities
- Governing law, disputes and contact
1. Status, parties and agreement
These proposed B2B terms require legal review, identification of both contracting entities and express incorporation into a signed service agreement. Browsing this page does not accept or execute them. The signed agreement must set precedence among the order form, service terms and DPA; mandatory law prevails.
2. Service scope and authorized users
Voice AI provides configured voice automation and related management functions specified in the order form. Features, integrations, languages, capacity and support are deployment-specific. The customer must be a business acting through authorized representatives and must identify permitted account users. No consumer subscription or emergency-response service is offered by these draft terms.
3. Accounts and access
The customer must provide accurate account details, protect credentials, assign suitable permissions, promptly revoke departing users and notify the provider of suspected misuse. Morganext’s access and security duties must be set out in the service agreement and DPA. Customers must not share credentials or access another customer’s data.
4. Permitted and prohibited use
Use is limited to agreed lawful business workflows. Prohibited uses include fraud, impersonation, harassment, unlawful surveillance or recording, unauthorized marketing, infringement of rights, unauthorized security testing and bypassing access controls. Voice cloning, biometric identification and high-risk regulated decisions require separate assessment and express authorization; they are not included by default.
5. Customer content and configuration
The customer is responsible for the authority to supply business content and for validating catalogs, prices, hours, availability, workflow rules, permissions and integrations. It must approve representative test calls before launch and review changes. Morganext may use that content only as necessary to provide the agreed service and as otherwise lawfully authorized; wider reuse needs a separate basis.
6. AI limitations and human review
AI can misunderstand speech, generate inaccurate statements, miss context or fail to complete actions. No perfect accuracy, successful order, uninterrupted call or business outcome is guaranteed. Customers must define confirmation steps, human review for consequential actions and fallback routes. Human escalation depends on configuration, telephony and staff availability.
7. Obligations toward callers
The customer must establish lawful purposes, supply appropriate AI/privacy/recording notices and obtain any required permissions before the relevant processing. It must provide a rights channel and an appropriate alternative where required. A sample announcement is not a universal consent mechanism. Each party remains responsible for its own statutory duties; these terms do not shift all privacy obligations to the customer.
8. Providers, maintenance and availability
Telephony, AI, speech, networks and customer systems can affect service quality and continuity. Maintenance and failures may interrupt calls or integrations. Any uptime targets, support hours, response times, service credits and maintenance notices must be expressly agreed. Marketing references to 24/7 handling describe possible configured operation, not an availability warranty.
9. Data rights, intellectual property and license
As between the parties, the customer retains its rights in its business content and customer data, subject to individuals’ rights and applicable law. Morganext retains rights in its software and service materials. The proposed license is non-exclusive, limited to the agreed business use during the contract, and subject to the order form. No ownership of personal data overrides statutory rights; rights in AI outputs require separate assessment.
10. Confidentiality and security
Each party must protect non-public information, restrict access to those with an authorized need and apply agreed safeguards. Exceptions require evidence of lawful public availability, independent development or lawful receipt. Compelled disclosure must be limited and notified where permitted. The DPA must address caller processing, personnel, incidents, providers and retention. Do not submit secrets or sensitive information outside the agreed scope.
11. Commercial terms and changes
Fees, usage limits, provider charges, taxes, billing, renewal and refunds belong in the separate commercial agreement. No price or automatic renewal is established here. Material changes to scope or processing require the agreed change process and any legally required notice or consent; posting a new draft alone does not amend a signed contract.
12. Suspension and termination
The signed agreement should permit proportionate suspension for material breach, unlawful use, non-payment or an immediate security risk, with notice and opportunity to remedy where practicable and lawful. It must specify termination rights, cure periods and transition arrangements. Emergency restrictions should be limited to what is necessary and reviewed promptly.
13. Export, deletion and end of service
Before termination, agree an authorized export format, delivery channel, assistance costs and deadline. Return or delete service data according to the DPA and retention schedule, including subprocessors and restricted backups. Lawful retention exceptions must be documented and protected. No indefinite export availability or immediate deletion from every backup is promised.
14. Liability allocation
Each party is responsible for its breaches and acts attributable to it under applicable law. The signed agreement should allocate foreseeable direct loss proportionately and specify any monetary cap, exclusions and carve-outs after negotiation. No liability cap or blanket exclusion is established by this draft. Nothing excludes non-excludable statutory liability, mandatory remedies or regulator powers. Counsel must review treatment of intentional misconduct, confidentiality, privacy, security and intellectual-property breaches.
15. Proposed proportionate indemnities
Subject to the signed allocation and applicable law, a party causing a third-party claim through its unlawful content, infringement or material contractual breach would indemnify the other only to the extent attributable to that conduct. Require prompt notice, reasonable defense control, cooperation and no settlement imposing obligations without consent. Exclude losses caused by the indemnified party; statutory penalties must not be shifted where prohibited. Scope and caps require counsel approval.
16. Governing law, disputes and contact
Applicable law, forum, escalation steps and the controlling language must be selected in the signed agreement after confirming the contracting entity and mandatory Israeli privacy obligations. No exclusive court, arbitration clause or waiver is chosen here. Draft date: 12 November 2026; no effective date. Commercial inquiries: info@morganext.com.