# AI, Automation, and Communications Addendum

**Version AUT-AI-2026-09-15.1. Applies when validly accepted.** This Addendum requires the completed Authority Schedule and separate activation controls. It supplements the Business Terms, without creating a second liability or dispute regime.

## 1. Acknowledgment of AI risks

Customer understands that Anna uses artificial intelligence and automated tools. It can invent facts, misinterpret a conversation, choose an incorrect action, disclose information improperly, miss an instruction, or fail to escalate. It can misstate prices, discounts, warranties, refunds, deadlines, availability, account balances, or legal rights. It can make booking, messaging, recordkeeping, or payment-related mistakes even when the output sounds confident.

A successful test does not ensure the same outcome in every later interaction. Voice recognition, translations, third-party data, and integrations introduce additional uncertainty. A setting labelled autonomous describes an approved operating mode; it is not a promise of perfect performance or elimination of Customer's oversight responsibilities.

Customer acknowledges these risks and will use proportionate controls. This acknowledgment is subject to the Business Terms' carve-outs and does not release nonwaivable claims, claims belonging to other people, or Autonomized's express responsibilities.

## 2. Authority must be specific

Customer authorizes only the workflows and limits in the completed schedule and later authenticated changes approved by a properly authorized representative. Permissions are scoped by business, workspace, channel, recipient group, action, and spending authority. A permission for one client, number, or account does not extend to another.

**Draft mode:** Anna may prepare content or proposed actions for review; external effects require approval. **Supervised mode:** only individually approved external actions may run. **Autonomous mode:** only the expressly enabled routine categories may run without individual approval, subject to documented caps, exclusions, and escalation rules. A user cannot use chat, a caller statement, a retrieved document, or an email to expand these permissions.

The signature on this Addendum is an acknowledgment of the framework. Activation requires a separate recorded choice showing the actual enabled permissions. Empty or ambiguous schedule entries authorize no additional external action. Existing manual CRM functions do not automatically authorize Anna to perform the same actions.

## 3. Price, quote, contract, and payment boundaries

Customer must provide approved, current prices, discount limits, quote conditions, taxes where relevant, refund rules, and delivery commitments. Customer must identify which quotes are binding offers and which require later human confirmation. Anna may not invent special pricing, guarantee eligibility, modify a contract, forgive debt, approve a refund, or make a commitment outside approved terms.

Customer must reserve a human approval step for material commitments outside a verified catalog or policy. Payment-related work must use approved providers and exact authorized amounts and payees. Sending a payment link, initiating a charge, issuing a refund, changing a subscription, and paying a third party are distinct permissions. One does not imply another. Autonomized's own subscription billing is distinct from Customer's collection of money from its clients.

An acknowledgment or system status does not establish that money moved or a counterparty accepted an offer. The authoritative transaction or signed acceptance record must be checked. Customer must maintain a process to investigate and correct errors. The parties' allocation of responsibility cannot determine a recipient's independent rights arising from apparent authority or misleading statements.

## 4. Communications authorization

Customer warrants that it has a lawful basis and all required permissions for each contact, message purpose, recording, and channel. For automated marketing calls and promotional messages, the default service policy requires documented, affirmative, business-specific written permission appropriate to the technology, subject to any stricter rule. Any proposed exception requires an approved, documented legal and provider basis before use.

Customer must record the recipient, number or address, named communicating business, precise disclosure, purpose, channels and technology covered, collection method, date and time, source, and later changes or revocation. Third-party lead vendors' assurances do not replace valid evidence. Consent cannot be purchased, fabricated, transferred beyond its valid scope, or inferred from accepting the Autonomized contract.

Customer must comply with applicable U.S. TCPA, state calling and recording rules, do-not-call requirements, CAN-SPAM, UK PECR, EU national electronic-marketing rules, and provider requirements as applicable. The list identifies relevant categories, not a representation that every program is compliant. A business recipient is not automatically exempt, and a sole trader can receive individual-subscriber protections.

## 5. Objections, recording, and identity

Customer must maintain a reliable suppression process for STOP, unsubscribe, do-not-call, equivalent verbal requests, wrong-number reports, and other recognized objections. Queued campaigns, retries, scheduled follow-ups, imports, and integrations must consult the applicable suppression record before the next external effect. A request for deletion must preserve any minimal record lawfully needed to keep a suppression effective.

AI interaction and business identity must be disclosed clearly in the relevant channel. Customer may not present Anna as a human, licensed professional, or independently authorized representative beyond the documented role. Recording and transcription require separate lawful handling, including consent before capture where required, and an appropriate alternative where available or required.

Caller ID, sending domains, brand and campaign registration, geographic permissions, recipient local hours, frequency limits, and carrier policies must be accurately configured. Approval by a carrier is not proof of lawful consent. Autonomized may stop affected traffic to address legal or provider risk, under the Business Terms.

## 6. Review, fallback, and incidents

Customer must appoint a responsible business owner and a reachable backup for escalations. It must regularly review suitable samples and all material exceptions, verify changes to critical rules, and investigate unusual behavior. High-impact decisions require meaningful human judgment rather than merely clicking through an AI recommendation.

Customer must maintain an alternative contact and operating process for outages. Anna is not an emergency service. Where urgent safety content is encountered, the appropriate safety response and human route must be configured without representing emergency dispatch capability that does not exist.

On discovering a material problem, Customer must pause the affected workflow if appropriate, preserve relevant records, notify Autonomized promptly, and cooperate on correction. Autonomized remains responsible for its express controls, incident duties, and remediation obligations. A pause may not recall an action already dispatched; the system must show the known state and avoid treating an ambiguous outcome as permission to repeat a charge or communication.

## 7. Customer clients and agencies

Where Customer acts for a separate client, it must have written authority covering access to that client's data and systems, approved communications, instructions, and the particular automation. Each client business must accept the applicable service documents itself or through an agent whose actual authority is documented. Merely paying for a subaccount does not establish authority to sign away a client's rights.

Customer must provide accurate downstream terms, privacy disclosures, AI notices, and channel-specific consent mechanisms. It must not promise that Autonomized makes its business compliant or accepts all liability for its services. Downstream terms cannot bind recipients who have not accepted them or waive mandatory consumer and privacy rights.

## 8. Records and changes

Maintain the approved schedule, relevant consent evidence, rules and prompt versions, review decisions, action records, and material changes for the documented proportionate retention period. Do not preserve unnecessary raw personal information merely because a litigation possibility exists. Apply a proper legal hold when a dispute or incident requires it.

Material expansions of authority, a new channel or country, a new client, a sensitive-data use, or a different consequential decision requires a new review and recorded authorization before activation. Legal acceptance, recipient consent, workflow authority, spending authorization, and payment confirmation are separate records.

## Authority Schedule — required before activation

| Field | Required entry |
|---|---|
| Customer and workspace | Verified legal entity and workspace identifier |
| Signer and operational owner | Name, title, authority, monitored contact; backup contact |
| Business purpose | Specific workflow and intended outcome |
| Countries and recipient categories | Actual service and recipient locations; approved country restrictions |
| Mode | Draft, supervised, or autonomous; default draft until affirmative activation |
| Channels | Separate selections for chat, inbound/outbound voice, SMS, email, and other channels |
| Knowledge and data sources | Approved authoritative records; restricted data and trusted-source limits |
| Permitted actions | Enumerated actions and permitted objects; no implied permission |
| Recipient scope and consent | Allowed lists/categories, evidence source, suppression owner and checks |
| Prices and commitments | Approved catalog/version, discount maximums, quote validity, review requirements |
| Money permissions | Separate permissions for links, charges, refunds, subscriptions, and payments; currency, per-action and period caps |
| Human approval | Actions, amounts, and circumstances requiring approval; approver roles |
| Recording and AI notices | Approved channel copy, consent timing, alternative contact route |
| Escalation | Triggers, human contact, availability, timeout disposition |
| Continuity | Manual fallback, pause method, irreversible-action warning |
| Retention | Recording, transcript, consent, and action-evidence periods |
| Verification | Controlled acceptance evidence for the authorized deployment; unresolved restrictions |
| Activation record | Separate authenticated authorization after agreements and checks, with version and timestamp |

## Signer's acknowledgment

“I am authorized to act for the named business. I understand that Anna can make mistakes and that our business must maintain accurate rules, appropriate consent, oversight, and human escalation. I accept this Addendum and the recorded Authority Schedule. My signature does not activate unspecified workflows, authorize unlimited spending, or waive rights the law protects from waiver.”

Customer legal name, signer name/title, signature, date, Order, and immutable schedule version: **complete in the signature record**.