Voice & Communications Terms

These Voice & Communications Terms (“Communications Terms”) supplement the agreement governing Customer’s use of Sloancode AI Services (the “Agreement”) with Sloancode Technology Group LLC (“Sloancode,” “we,” “us,” or “our”).

They apply whenever Customer uses the Services to initiate, receive, route, record, transcribe, synthesize, analyze, automate, or otherwise process telephone calls, voice interactions, SMS/MMS, email, web chat, WhatsApp, social messaging, or other electronic communications (“Communications Services”).

Customer is responsible for the legality of its communications campaigns, recipients, content, consent, notices, calling/messaging practices, and Customer-controlled configurations. Sloancode provides communications technology and AI functionality; it does not become the sender, seller, caller, telemarketer, merchant, or principal merely by providing the Services unless a signed agreement expressly states otherwise.

Capitalized terms not defined here have the meanings in the Agreement, DPA, or applicable Order Form.

1. Scope and Communications Channels

These Communications Terms apply to inbound and outbound voice calls; AI-generated or prerecorded voice; speech-to-text and text-to-speech; call routing; voicemail; SMS/MMS; email; web chat; WhatsApp and other messaging channels; social messaging; notifications; and communications-related integrations enabled through the Services.

Additional provider, carrier, platform, number-registration, campaign-registration, or product-specific terms may apply to a particular channel.

2. Customer as Communications Principal

Unless expressly agreed otherwise, Customer determines the recipients, purpose, timing, content, campaign classification, business identity, offers, and instructions for Customer Communications.

Customer is responsible for determining whether a communication is informational, transactional, relationship-based, marketing, telemarketing, advertising, debt-related, healthcare-related, emergency-related, or otherwise regulated.

Customer may not characterize a marketing or solicitation communication as transactional or informational merely to avoid consent, disclosure, registration, or opt-out requirements.

3. Compliance with Communications Laws

Customer must comply with all laws and regulations applicable to Customer Communications, including, where applicable, the Telephone Consumer Protection Act (“TCPA”), FCC rules, Telemarketing Sales Rule (“TSR”), National Do Not Call requirements, CAN-SPAM Act, state telemarketing and mini-TCPA laws, state recording/wiretapping laws, consumer-protection laws, privacy laws, and laws governing electronic signatures and consent.

Where communications cross jurisdictions, Customer is responsible for identifying and satisfying the requirements applicable to the caller/sender, recipient, content, purpose, and location.

Customer must possess a legally sufficient basis before initiating or causing Sloancode to initiate a regulated communication.

Where prior express consent, prior express written consent, signed written agreement, opt-in, or another specific authorization is required, Customer must obtain it before the communication and must ensure it covers the applicable sender/seller, telephone number or address, communication type, technology, and purpose.

Customer may not condition purchase of goods or services on consent to receive communications where applicable law prohibits such conditioning.

Customer bears responsibility for proving consent where the law places that burden on the sender, seller, caller, or telemarketer.

Customer must maintain records reasonably sufficient to demonstrate legally required consent and its scope.

identity or account associated with the consent;
telephone number, email address, messaging identifier, or other destination;
date and time of consent;
method and source through which consent was obtained;
language/disclosures presented at the time of consent;
identity of the specific seller/sender/caller where required;
applicable campaign, purpose, or communication category;
version of the consent disclosure or form;
revocation, opt-out, suppression, and re-consent history.

Sloancode may provide technical consent-recording functionality, but Customer remains responsible for determining whether the captured evidence is legally sufficient for Customer’s use case.

6. Revocation, Opt-Out, and Suppression

Customer must honor legally valid revocations of consent, do-not-call requests, unsubscribe requests, STOP requests, and other opt-outs within the time and manner required by applicable law.

Customer must not design scripts, agents, menus, or workflows to frustrate, obscure, delay, or condition a lawful revocation.

Where the Services provide suppression or opt-out functionality, Customer must not disable or circumvent it for regulated communications.

A person who revokes consent must not be re-enrolled merely because Customer later imports the same contact information, unless a legally valid new consent or other lawful basis exists.

7. Do Not Call Requirements

For telemarketing subject to Do Not Call rules, Customer is responsible for required National Do Not Call Registry access/scrubbing, entity-specific do-not-call lists, applicable state lists, exemptions, written-permission records, and calling-hour restrictions.

Customer must maintain and enforce entity-specific suppression requests and must not share or misuse Do Not Call information except as legally permitted.

Customer may not rely on an established business relationship, inquiry, or other exemption unless the facts and applicable law actually support it.

8. AI-Generated, Artificial, and Prerecorded Voice

Customer acknowledges that AI-generated or synthetic voice may be treated as artificial or prerecorded voice under applicable communications law.

Customer may use AI-generated or prerecorded voice for regulated outbound communications only where Customer has the consent and other authority required for that particular call and complies with applicable identification, disclosure, opt-out, calling-hour, and recordkeeping requirements.

Customer may not use AI voice to impersonate a person without authorization, conceal the caller’s identity, or mislead recipients about the source or purpose of a communication.

Where applicable law requires an automated interactive opt-out mechanism for prerecorded telemarketing, Customer must use channel functionality capable of providing the legally required opt-out experience.

9. Inbound Voice AI

Inbound calls initiated by an End User may be handled by conversational AI for ordering, scheduling, reservations, service intake, support, routing, information, or other authorized purposes.

If an inbound interaction changes into an upsell, solicitation, outbound follow-up, or other regulated activity, Customer is responsible for the additional legal requirements triggered by that activity.

Customer must ensure that the AI does not make materially deceptive claims about its identity, authority, capabilities, products, pricing, or legal status.

10. Outbound Voice AI

Outbound AI calling requires Customer to establish lawful campaign authority before activation.

campaign purpose and classification;
recipient eligibility and consent status;
applicable do-not-call screening;
calling-time restrictions;
required caller/seller identification;
required disclosures;
AI/artificial/prerecorded voice requirements;
opt-out/revocation handling;
recordkeeping and suppression.

Sloancode may require Customer to complete compliance configuration, campaign registration, or certification before outbound voice functionality is activated.

11. Call Recording, Monitoring, and Transcription

Customer is responsible for determining whether a call or other communication may lawfully be recorded, monitored, transcribed, analyzed, or retained.

Because recording-consent laws vary by jurisdiction, Customer must provide any legally required notice and obtain any legally required consent before recording or monitoring begins.

Customer may configure recording only for lawful purposes and may not use recording functionality to evade wiretap, eavesdropping, employee-monitoring, privacy, or sector-specific laws.

Where a transaction requires a legally compliant audio record of authorization, Customer is responsible for ensuring that the recording captures the legally required disclosures, agreement, and context.

12. Transcripts and Conversation Analytics

Transcripts, summaries, sentiment indicators, extracted fields, and conversation analytics may contain errors and must not be treated as verbatim or legally conclusive records unless independently verified.

Customer must use appropriate human review before relying on AI-derived communications analytics for consequential decisions.

Customer may not use conversation analytics to infer sensitive traits or make unlawful high-impact decisions.

13. Voice Cloning and Custom Voices

Customer may create or use a custom or cloned voice only where Customer possesses all rights, permissions, and consents required for the person whose voice is replicated or simulated.

Customer may not create a voice clone through deception, stolen recordings, unauthorized scraping, or other unlawful means.

Customer must discontinue use if authorization expires or is validly withdrawn and continued use would be unlawful.

Sloancode may require identity/authorization evidence before enabling custom voice capabilities.

14. Caller Identification and Number Use

Customer must use telephone numbers and caller-identification information lawfully and accurately.

Customer may not spoof, manipulate, rotate, or misrepresent caller ID for fraudulent, deceptive, harassing, or unlawful purposes.

Telephone numbers may be subject to carrier, provider, registration, portability, geographic, emergency-address, or identity-verification requirements.

Customer is responsible for maintaining current business identity information required for number or campaign registration.

15. Telephone Number Ownership, Porting, and Forwarding

Rights in telephone numbers are subject to applicable telecommunications rules and provider terms; assignment of a number does not necessarily confer property ownership.

Customer is responsible for obtaining authorization to port or forward numbers and for ensuring that forwarding does not circumvent consent, identity, emergency, or regulatory requirements.

Sloancode may require letters of authorization, account records, or other evidence before processing a number port.

16. SMS and MMS

Customer must send SMS/MMS only to recipients for whom Customer has the legally required consent or other lawful basis and must comply with applicable carrier, messaging-provider, campaign-registration, content, throughput, and anti-spam requirements.

Customer must clearly identify itself where required and must implement required HELP, STOP, unsubscribe, and similar commands.

Customer may not use shared or multiple numbers, sender IDs, or campaign identities to evade registration, filtering, consent, or suppression controls.

Customer is responsible for message and data-rate disclosures where required and for maintaining required campaign disclosures and opt-in evidence.

17. A2P Messaging and Campaign Registration

Application-to-person messaging may require brand and campaign registration, vetting, use-case disclosure, sample messages, opt-in descriptions, privacy/terms links, or other carrier/provider requirements.

Customer must provide accurate registration information and must use an approved campaign only for the registered use case.

Approval by a carrier, registry, or provider does not constitute a legal determination that Customer’s campaign complies with all applicable law.

18. Email Communications

Customer must comply with laws applicable to commercial email, including CAN-SPAM where applicable.

use accurate header, routing, sender, and reply information;
avoid deceptive subject lines;
make required advertising disclosures;
include a valid physical postal address where required;
provide a clear and functioning opt-out method for commercial email;
honor opt-out requests within the legally required period;
not transfer suppressed addresses except as legally permitted for compliance.

Customer must distinguish transactional/relationship email from commercial email based on the actual primary purpose and content, not merely Customer’s label.

19. Web Chat and Website Communications

Customer is responsible for notices and consents applicable to website chat, AI chat, tracking technologies, session recording, transcript retention, lead capture, and cross-channel follow-up.

A website visitor’s initiation of a chat does not automatically authorize unrelated marketing calls, texts, or emails. Customer must establish any additional required consent.

Customer must comply with the applicable platform’s business, messaging, template, commerce, privacy, and acceptable-use rules in addition to applicable law.

Sloancode may enforce provider-required restrictions or disable functionality where necessary to preserve channel access or address abuse.

Third-party platform approval or delivery does not establish legal compliance.

21. Transactional vs. Marketing Communications

Customer must classify communications based on their actual content and purpose.

Order confirmations, appointment reminders, delivery/status updates, security alerts, and similar messages may be transactional or informational in appropriate circumstances, but adding promotional or solicitation content can alter the classification and applicable requirements.

Customer is responsible for reviewing mixed-purpose communications and obtaining marketing consent where required.

22. Quiet Hours, Frequency, and Contact Pressure

Customer must comply with federal, state, local, and other applicable restrictions on calling/messaging times, frequency, repeated contacts, harassment, and abandonment.

Customer must not configure AI agents or automation to repeatedly contact a person in a manner that is harassing, abusive, coercive, or designed to defeat a non-response or opt-out.

Sloancode may impose frequency/rate controls beyond legal minimums to protect recipients, carriers, and platform integrity.

23. Abandoned Calls, Predictive Dialing, and Answering Machines

If Customer uses dialing technology subject to abandoned-call restrictions or safe-harbor requirements, Customer is responsible for applicable live-answer connection rates, ring duration, recorded identification messages, campaign-level measurement, and required records.

Where prerecorded telemarketing may reach voicemail or answering machines, Customer is responsible for any required toll-free or automated opt-out mechanism and its required availability.

24. Disclosures During Calls and Messages

Customer must ensure required disclosures are made clearly, conspicuously, and at the legally required point in the interaction.

identity of the seller, caller, sender, or business where required;
commercial or solicitation purpose where required;
AI/artificial/prerecorded nature where disclosure is required;
recording/transcription notice where required;
material terms of an offer or transaction;
recurring/subscription terms where applicable;
opt-out/revocation method;
charges, fees, message/data rates, or other disclosures where required.

Customer may not intentionally place mandatory disclosures after a point where a recipient has already been induced to act.

25. Payments and Oral Authorizations

Where Customer uses voice or communications to obtain payment authorization, Customer is responsible for complying with laws and payment-provider requirements governing authorization, disclosures, records, and restricted payment methods.

Customer must not collect complete card credentials through channels not expressly designed and approved for secure payment data.

If applicable law requires recorded oral authorization, Customer is responsible for ensuring the recording captures all required information and is retained/made available as legally required.

26. Emergency Communications and 911

Unless expressly stated in an Order Form, Sloancode AI is not an emergency communications service, public-safety answering point, 911/E911 provider, alarm-monitoring service, or guaranteed emergency-dispatch service.

Customer must not represent the Services as a substitute for 911, emergency services, life-safety dispatch, or legally required emergency communications.

Where a Customer workflow may receive urgent or emergency content, Customer must implement appropriate human escalation and instructions directing individuals to emergency services where appropriate.

27. Healthcare, Financial, Housing, Employment, and Other Regulated Communications

Customer is responsible for additional communications, privacy, confidentiality, consent, recordkeeping, and content restrictions applicable to regulated sectors.

Customer may not use a general-purpose communications configuration for specially regulated data or high-impact workflows unless the Service is approved for that use and required supplemental agreements/controls are in place.

28. Restaurant AI Communications

Restaurant AI may use voice and messaging for ordering, reservations, waitlists, catering, delivery updates, customer service, and other approved workflows.

A transactional restaurant interaction does not automatically authorize unrelated promotional calling/texting. Marketing follow-up requires the consent or other lawful basis applicable to that channel and purpose.

Customer remains responsible for menu, pricing, allergen, alcohol, delivery, fulfillment, refund, and consumer disclosures communicated through the Services.

29. Field Services, Facilities, Construction, and Property Management Communications

Operational communications may include scheduling, dispatch, work-order updates, access coordination, maintenance notices, resident/tenant communications, vendor communications, and project updates.

Customer is responsible for legally required tenancy, entry, employment, safety, contractual, accessibility, emergency, and other notices; AI-generated communications do not replace formal statutory notice where a specific form, delivery method, timing, or human authorization is legally required.

Customer must distinguish service/operational communications from marketing campaigns.

30. AI Accuracy in Communications

AI-generated speech, messages, summaries, translations, and responses may be inaccurate. Customer must configure authoritative sources, escalation, confirmation, and human review appropriate to the risk.

Customer may not knowingly allow AI to fabricate prices, legal rights, contractual terms, safety instructions, appointment commitments, product availability, refund commitments, or other material facts.

Where a communication creates or modifies a transaction, Customer should implement confirmation appropriate to the consequences of error.

31. Human Escalation and Transfer

Customer must provide reasonable escalation to a human or alternate channel where legally required or appropriate to the risk, including for disputes, complaints, consent revocation, accessibility needs, safety issues, high-impact decisions, or situations the AI cannot reliably resolve.

Sloancode may require escalation rules for designated high-risk workflows.

32. Accessibility and Language

Customer is responsible for accessibility and language obligations applicable to Customer Communications.

Machine translation and multilingual AI may contain errors. Customer must use qualified human translation or review where law or risk requires precise language.

Customer may not intentionally use language selection or accessibility barriers to obscure material terms, consent, or opt-out rights.

33. Communications Data and Privacy

Communications data may include telephone numbers, email addresses, message content, recordings, transcripts, metadata, timestamps, consent records, routing data, and AI-derived information.

Processing of Customer Personal Data is governed by the DPA where applicable. Customer is responsible for privacy notices and lawful bases applicable to Customer’s collection and use.

Customer must not expose communications data to unauthorized users or integrations.

34. Recording and Transcript Retention

Retention of recordings and transcripts must be configured and managed according to Customer’s legal, operational, contractual, and records-management requirements.

Customer should not retain recordings or transcripts longer than reasonably necessary unless required by law or legitimate business need.

Deletion may be subject to backup lifecycle, legal holds, provider retention, and technical limitations described in the DPA or applicable Documentation.

35. Model Training and Communications Content

The Customer Content/model-training rules in the Agreement and DPA apply to voice recordings, transcripts, messages, prompts, and other Communications Content.

Unless Customer affirmatively opts in, separately authorizes such use, or enters an agreement expressly permitting it, Sloancode will not use Customer Communications Content to train generalized Sloancode AI models across unrelated Customers.

36. Carrier and Provider Rules

Communications Services depend on telecommunications carriers, messaging registries, email providers, social platforms, cloud providers, and other Third-Party Services.

Customer must comply with applicable provider terms that lawfully flow through to Customer’s use.

Providers may filter, block, throttle, suspend, reject, reclassify, or charge for traffic. Sloancode does not guarantee delivery, answer rates, carrier acceptance, inbox placement, or continued third-party channel availability.

37. Messaging and Telephony Fees

Customer is responsible for applicable usage charges described in the Order Form, including telephony, messaging, carrier, registration, number, recording, transcription, AI/model, storage, or other communications charges.

Third-party surcharges, carrier fees, regulatory fees, taxes, or provider price changes may be passed through where permitted by the Agreement.

A blocked, filtered, unanswered, failed, or recipient-rejected communication may still incur provider usage charges.

38. Number and Sender Reputation

Customer is responsible for conduct that affects number, domain, IP, sender, campaign, or brand reputation.

Sloancode may impose controls, suspend campaigns, rotate infrastructure where appropriate, or require remediation to protect shared communications infrastructure.

Customer may not intentionally burn, churn, or rotate numbers/domains/senders to evade reputation controls or filtering.

39. Prohibited Communications

Customer may not use Communications Services for fraud, phishing, impersonation, unlawful harassment, threats, illegal discrimination, malicious cyber activity, child exploitation, deceptive lead generation, unlawful surveillance, sanctions evasion, or other activity prohibited by the AUP.

Customer may not send content prohibited by applicable carriers/platforms where such restrictions lawfully apply to the channel.

40. Customer Lists and Lead Sources

Customer may upload or use contact lists only where Customer has lawful authority and the list may lawfully be used for the intended communication.

Customer is responsible for due diligence on purchased, rented, affiliate, referral, lead-generator, or third-party lists.

Possession of a telephone number or email address does not itself establish consent to market through that channel.

Where law requires consent directly from the recipient for a specific seller or caller, Customer may not rely on a lead generator or third party unless the consent mechanism legally satisfies that requirement.

Customer must be able to substantiate the chain of consent and the disclosure presented to the recipient.

Sloancode may reject campaigns based on opaque, unverifiable, or legally insufficient lead-source practices.

Customer must determine the legally required scope of a revocation. An opt-out from one channel or campaign may, depending on law and context, affect other communications.

Customer must not assume that consent to one channel, purpose, seller, affiliate, or campaign authorizes another.

Sloancode may provide cross-channel suppression functionality, but Customer is responsible for configuring it to meet Customer’s legal obligations.

43. Records and Compliance Evidence

Customer must retain legally required communications compliance records for the required period.

Customer may not fabricate, backdate, silently overwrite, or destroy consent, opt-out, campaign, recording, or communication evidence to conceal noncompliance.

Corrections to compliance records should preserve appropriate history and auditability.

44. Testing and Non-Production Communications

Customer must use test destinations, sandbox capabilities, or controlled recipients where reasonably available during development.

Customer may not conduct live test campaigns against real recipients without the authority required for the resulting communications.

Production credentials, numbers, contact lists, and communications data should remain separated from development/test environments consistent with applicable security requirements.

45. Customer Configuration and Certification

Sloancode may require a communications compliance checklist or certification before enabling production calling/messaging.

business identity verified;
campaign/use case classified;
consent source documented;
opt-in language reviewed;
STOP/unsubscribe handling enabled;
do-not-call/suppression process established;
recording notice/consent configured where applicable;
required registrations completed;
sample messages/scripts consistent with approved use;
escalation and complaint process identified.

46. Monitoring and Enforcement

Sloancode may monitor operational signals reasonably necessary to detect abuse, carrier complaints, excessive opt-outs, spam indicators, fraud, security threats, or violations of these Communications Terms, consistent with the Agreement, Privacy Policy, and DPA.

Sloancode may warn, rate-limit, block a campaign, disable a number/sender/channel, revoke credentials, suspend Communications Services, or terminate use where reasonably necessary to address material risk or violation.

Urgent action may occur without advance notice where required by law, a carrier/provider, security risk, or imminent harm.

47. Complaints, Investigations, and Cooperation

Customer will reasonably cooperate with complaints, carrier/provider inquiries, regulatory investigations, consent challenges, and abuse reviews involving Customer Communications.

Customer will provide relevant consent evidence, scripts, campaign information, list-source information, and other records reasonably necessary to investigate.

Sloancode may preserve or disclose information where required by valid legal process or applicable law.

48. Suspension for Communications Risk

Sloancode may suspend affected Communications Services for suspected unlawful traffic, material consent deficiencies, high complaint rates, fraudulent identity, prohibited content, registration mismatch, carrier/provider direction, security threats, sanctions concerns, or material AUP violations.

Where practicable, suspension will be limited to the affected channel/campaign and restored after satisfactory remediation.

49. No Guarantee of Regulatory Approval or Delivery

Sloancode does not warrant that a carrier, registry, regulator, platform, or provider will approve Customer’s number, brand, campaign, message, template, or use case.

Technical acceptance, registration, or successful delivery does not mean a communication is legally compliant.

Customer remains responsible for legal review appropriate to its use case.

50. Allocation of Responsibility

Sloancode is responsible for operating the Services in accordance with its contractual obligations. Customer is responsible for Customer’s communications strategy, legal basis, recipients, content, lists, offers, campaign classification, Customer-configured retention, and Customer instructions.

Nothing in these Communications Terms shifts a statutory obligation that applicable law independently imposes on Sloancode in its own capacity.

51. Indemnity and Liability

Claims arising from Customer’s unlawful communications, missing consent, illegal recording, deceptive content, unlawful lead sources, or Customer’s violation of communications law are subject to the Customer indemnification provisions of the Agreement to the extent stated there.

Liability under these Communications Terms is subject to the Agreement’s limitations of liability except where applicable law prohibits limitation.

52. Order of Precedence

For voice and communications matters, these Communications Terms supplement the Agreement and AUP. The DPA governs processing of Customer Personal Data. A signed Order Form or negotiated agreement may expressly modify these Communications Terms.

Mandatory communications law and provider requirements control to the extent they cannot lawfully be varied by contract.

53. Changes to Communications Terms

Sloancode may update these Communications Terms prospectively to reflect changes in law, FCC/FTC requirements, carrier/provider rules, messaging registration, product functionality, abuse patterns, or safety requirements.

Material changes will be communicated in accordance with the Agreement. Where a change materially affects a committed enterprise use case, the Agreement’s change provisions apply.

54. Contact

Sloancode Technology Group LLC
Attn: Sloancode AI Communications / Legal
99 Wall Street
Suite 3772
New York, NY 10005
United States

Communications Compliance:

Contact:

Legal: legal@sloancode.com

Support: support@sloancode.com

Privacy: privacy@sloancode.com
Compliance: Compliance@sloancode.com