Voice & Communications Policy

ALEBEX does not require a separate campaign form for ordinary communications. The account holder accepts a standing legal obligation, completes a short electronic outbound attestation, retains its evidence, and remains subject to automated controls and exception-based review.

This ALEBEX AI Voice and Customer Communications Policy (“Communications Policy”) applies to calls, voice interactions, SMS, MMS, email, chat, recordings, transcripts, summaries, CRM updates, routing, follow-up, and other communications initiated, configured, controlled, or enabled through the Services (“Customer Communications”). It forms part of the applicable ALEBEX agreement.

Customer is solely responsible for the purpose, recipients, contact sources, consent or other lawful basis, caller and sender identity, content, scripts, prompts, offers, products, recording and transcription, AI or automation disclosure where required, calling hours, opt-outs, suppression, do-not-call, anti-spam, privacy, consumer-protection, and recordkeeping obligations applicable to Customer Communications.

Customer must not initiate production outbound communications until Customer has accepted the applicable legal bundle, secured an approved payment source, completed the electronic communications attestation, verified required caller or sender identity information, selected intended countries and communication categories, and satisfied any Account controls.

After these steps, ALEBEX may automatically enable ordinary outbound uses, including sales outreach, lead follow-up, appointment setting, customer service, reactivation, surveys, notifications, reminders, business development, and similar communications. Customer does not need to submit a separate Schedule F or obtain ALEBEX approval for each campaign, list, script, End Client, or ordinary configuration.

ALEBEX may hold, limit, or review a Restricted Use, unsupported country, unusual traffic pattern, purchased or third-party list, disputed custom voice, material complaint pattern, invalid caller identity, payment concern, sanctions concern, security event, carrier or regulator request, or other elevated-risk circumstance.

Customer must determine and document the consent, permission, exemption, existing relationship, contractual right, legitimate interest, or other lawful basis required for each communication purpose, recipient category, country, channel, and technology. A business-to-business, existing-customer, informational, or other exemption from one rule does not create an exemption from all applicable rules.

Customer must not contact a Recipient outside the scope of the authorization or use a contact source for a materially different purpose without a lawful basis. Customer must not rely solely on a data broker or lead vendor’s assurance and must verify that the rights and evidence are sufficient for Customer’s use.

Scraped, stolen, deceptively obtained, or unauthorized lists are prohibited. Purchased or third-party lists may trigger enhanced review and must have traceable source, scope, date, seller, and permission information.

Customer must identify the actual calling or sending business and campaign sponsor accurately, use telephone numbers and sender identifiers it is authorized to use, and comply with carrier registration and identity requirements. Customer must not spoof, rotate, substitute, or obscure identity to mislead Recipients, evade blocks, or conceal complaint history.

Customer must not state or imply that ALEBEX, a government body, school, employer, bank, professional adviser, emergency service, or another party is the sponsor unless the statement is legally authorized and accurate.

Customer controls the opening message, system prompt, disclosure wording, and workflow subject to law, ALEBEX policy, carrier requirements, and account controls. Customer must provide an AI, automated-interaction, artificial or prerecorded voice, recording, monitoring, transcription, or commercial-purpose disclosure when required by applicable law, contract, country requirements, or an ALEBEX restriction applicable to the enabled use.

ALEBEX does not impose a universal opening AI disclosure for every Canada or United States interaction. Customer must configure the interaction for its specific country, recipient, purpose, and consent basis. Customer must not use configuration freedom to deceive. If a Recipient asks whether the agent is AI, automated, virtual, synthetic, or human, the interaction must answer truthfully.

Where recording or transcription is not permitted or consent is withheld or withdrawn, Customer must configure a no-recording path, human transfer, alternative channel, or termination of the recording or interaction as appropriate.

Customer must provide and honor legally required opt-out, unsubscribe, do-not-call, consent-withdrawal, and channel-preference mechanisms. Requests must be processed promptly and reflected in internal suppression systems and any applicable ALEBEX feature.

Customer must not re-contact a Recipient after an applicable opt-out unless lawfully permitted and documented. Customer must not bypass suppression by changing accounts, numbers, domains, identities, spellings, or channels. Customer must comply with calling-hour, time-zone, frequency, abandoned-call, caller-identification, message-length, and other channel rules in the Country Requirements.

Before creating or using a custom or likeness-based voice, the Account holder must electronically certify that it has all rights, permissions, releases, and consents required to upload the recording; create the voice; use the person’s name, voice, likeness, persona, or institutional role; and authorize ALEBEX and its service providers to process the material for the requested purpose.

Customer must preserve the authorization and its scope for at least five years after last use. Customer must not use a custom voice for impersonation, false authority, false endorsement, fraud, social engineering, authentication circumvention, political synthetic impersonation, or a purpose outside the permission granted. ALEBEX may disable the voice immediately after a complaint, dispute, or credible risk signal.

Customer must retain, for at least five years or longer where required, contact and lead source; consent or other lawful basis; opt-outs and suppression; caller and sender identity; campaign purpose; applicable script or message version; required disclosure settings; custom-voice authorization; complaint and remediation records; End-Client authorization; and any legal or compliance approval Customer relied upon.

Ordinary application, user, configuration, and acceptance audit logs controlled by Customer or Developer must be retained for at least twenty-four months. Records must be sufficiently detailed to identify the organization, actor, time, action, affected workflow or communication, and relevant terms or attestation version.

Customer must investigate complaints, preserve relevant audio, transcripts, logs, scripts, lists, and settings, honor valid requests, and notify ALEBEX promptly of fraud, carrier blocks, regulator inquiries, widespread disclosure failure, voice-rights disputes, or significant Recipient harm.

ALEBEX may request reasonable records, screenshots, exports, certifications, samples, scripts, or other evidence. Customer stores the evidence and submits it only when requested, not for each ordinary campaign.

Customer must maintain appropriate human review, escalation, correction, and supervision for complaints, opt-outs, sensitive questions, regulated topics, data-subject requests, and any interaction the AI cannot answer accurately or lawfully. AI must not be the sole channel for emergencies or urgent safety situations.

Political or election communications, debt collection, regulated financial or investment services, healthcare or clinical functions, insurance decisions or regulated sales, government or law-enforcement use, high-risk use involving minors, high-impact automated decisions, Restricted Data, sub-resellers, and unsupported countries require ALEBEX approval or an expressly enabled Account setting.

A Developer or Platform Partner is responsible for implementing the required communication controls in its own interface and workflows. It must not remove required ALEBEX gates or misstate that ALEBEX has approved a campaign’s legality. It must bind End Clients, preserve acceptance and organization records, implement suppression and complaint controls, and promptly disable activity when directed.

A Platform Partner may create and manage ordinary business organizations without ALEBEX pre-approving each organization, provided the required organization information, downstream acceptance, payment allocation, country and use declarations, and risk controls are complete. A sub-reseller or another partner tier requires ALEBEX approval.

ALEBEX operational enablement, non-objection, monitoring, support, or review is not legal advice, a compliance certification, or a representation that a communication is lawful. Customer remains solely responsible for legal compliance and for its End Clients and Recipients.

ALEBEX may monitor traffic and complaints; request evidence; impose country, destination, volume, rate, recording, voice, or feature limits; require reverification or recertification; disable a number, voice, campaign, organization, integration, credential, or Account; or suspend or terminate service where ALEBEX reasonably identifies legal, fraud, security, carrier, provider, payment, recipient-harm, or service-integrity risk.

ALEBEX may update this Communications Policy under the Platform Terms. Questions may be sent to legal@alebex.ai. Recipient complaints, fraud, prohibited use, and abuse reports may be sent to abuse@alebex.ai.