Outbound Calling Addendum
Version and effective date: stated in the page header and in the release record for this document.
This Addendum applies before Customer enables outbound calling. It supplements the Terms and DPA; an authorized owner must accept the approved version. It does not bind recipients or replace their required consent.
1. Approved campaigns and countries
Outbound AI voice marketing is an intended Everaide use, subject to supported activation and this Addendum. The account owner selects contacts, campaign content and schedule, and approves the campaign; the service then automatically initiates calls. This workflow does not itself establish recipient consent or remove obligations applicable to Provider.
Customer will identify the organization, campaign purpose, intended recipient countries, recipient relationship and data source accurately. Each campaign must fit a supported use and jurisdiction. Customer's country of registration does not determine the law for every recipient. Telephone prefixes and an uploaded timezone are not conclusive evidence of residence or location.
Standard self-service approval is not available for unsupported countries, political persuasion, debt collection, emergency calls, sensitive-data collection or consequential automated decisions. UK/EU outbound activation requires country-specific review and supported permissions, identification, recording, revocation and time-window controls. Do not describe general account availability as worldwide calling approval.
2. Recipient permission and evidence
Customer must establish and retain the permission required for each call type and recipient. Where required, consent must specifically cover artificial/AI or prerecorded voice calls, the named calling organization and the relevant purpose. For the standard marketing workflow, require documented prior express written consent covering the named business and artificial/AI voice marketing at the designated number. This is a conservative platform eligibility condition, not a statement that every possible call has identical legal requirements. Any claimed exception needs separate review and supported controls. General marketing permission, a public business phone listing, an imported list or an existing relationship is not automatically sufficient. Consent must not be made a purchase condition where prohibited.
Evidence must identify the recipient/number, who obtained consent, when and how, the actual disclosure/version, covered organization/purpose/channel and any subsequent withdrawal. Customer must provide reasonably requested evidence promptly. An upload attestation confirms Customer's responsibility; it is not proof that every number's owner consented.
Customer must stop calling after revocation or an applicable do-not-call request, keep lists accurate, address wrong/reassigned numbers, and apply required national/state or local suppression checks. A business-related number may be wireless or answered by a consumer; a B2B label alone does not establish an exemption. School/nonprofit status alone is not sufficient to choose a legal exemption. Provider may refuse activation or pause activity where evidence or controls are inadequate.
3. Identification, recording and opt-out
Customer must satisfy any applicable seller/telemarketer registration, bonding, state-specific calling restrictions and do-not-call obligations before campaign approval. The country/use check is not a representation that all 50 states have been cleared.
Customer will use truthful caller identification and a usable callback/contact route. AI disclosure and recording information must be accurate, understandable and provided at the appropriate time. Where recording consent is required, Customer and Provider must use a technically supported process rather than rely on a misleading notice. Customer must not suppress or contradict disclosures through a greeting, prompt or document.
Recipients must have the required working opt-out during applicable calls and any approved voicemail. Provider will maintain and test supported opt-out handling; Customer must also act on requests received outside the platform. A recipient who refuses future marketing must not be put back on a list through reimport or a new campaign.
4. Limits and voicemail
Customer must respect per-recipient calling windows, campaign limits and legal caps. Platform limits are additional safeguards, not a warranty that a campaign is lawful. Customer must not use multiple accounts/numbers to bypass limits.
Voicemail mode defaults to hanging up without leaving a message. leave_message remains disabled unless the applicable legal, consent, script and technical requirements are separately approved and implemented. A commercial prerecorded message may require callback/automated opt-out infrastructure; an acceptance of risk does not replace it.
5. Records, complaints and responsibility
Keep consent and calling-compliance evidence for the period required by applicable law and applicable vendor contracts, with a defined trigger and legal-hold process. The applicable schedule must account for any supplier evidence requirements and applicable telemarketing recordkeeping rules. Specify the record categories, clock triggers, responsible party and access process; do not substitute the owner SMS retention schedule for campaign records. Do not keep all call audio for that period merely because consent evidence is retained.
Notify Provider promptly of material complaints or regulator correspondence affecting calls through Everaide. Cooperate in locating relevant evidence without exposing unrelated individuals' information. Provider may suspend affected campaigns to prevent further harm while investigating. Each party remains responsible for its own conduct; customer warranties do not absolve Provider from laws applicable to it.
Liability and any indemnity follow the Terms and negotiated public-sector schedule. No unlimited stored-card authorization or universal TCPA-insurance warranty is created here.
6. Activation record
The activation record identifies the customer/entity and authorized owner, the approved countries and use, and the Addendum version/hash, server timestamp and evidence references. It is generated by the service when an owner accepts this Addendum.