Legal - Effective May 17, 2026

CallOrbit TCPA Compliance Language

This TCPA Compliance Language gives CallOrbit customers practical rules for U.S. calling and texting, including consent, Do Not Call, robocalls, robotexts, business SMS, prerecorded messages, autodialing, AI-assisted outreach, opt-outs, caller ID, and recordkeeping.

Effective date: May 17, 2026. Review cadence: Reviewed with U.S. calling, texting, consent, FCC, carrier, and campaign registration changes. Contact: compliance@callorbit.tech.

  • 1. Customer Responsibility
  • 2. Consent Standards
  • 3. Opt-Out And Revocation
  • 4. Do Not Call And Quiet Hours
  • Does TCPA apply to business SMS?
  • Can I use purchased lead lists?

Policy snapshot

  • Effective date: May 17, 2026
  • Review cadence: Reviewed with U.S. calling, texting, consent, FCC, carrier, and campaign registration changes
  • Contact: compliance@callorbit.tech

1. Customer Responsibility

If you use CallOrbit to contact U.S. consumers or U.S. phone numbers, you are responsible for complying with the Telephone Consumer Protection Act, FCC rules, state mini-TCPA laws, Do Not Call rules, consent rules, carrier rules, industry messaging rules, and all other applicable laws.

CallOrbit provides communication tools. CallOrbit does not determine whether your contact list, campaign, script, consent language, dialing method, AI-assisted outreach, SMS campaign, WhatsApp workflow, or prerecorded message is lawful for your specific use case.

2. Consent Standards

  • Obtain prior express written consent before sending marketing robocalls, robotexts, prerecorded telemarketing messages, autodialed marketing calls, or marketing texts where required.
  • Consent must be clear, conspicuous, specific to the seller where required, and tied to the type of communication being sent.
  • Consent should identify the business, authorized phone number, communication type, and that consent is not a condition of purchase where required.
  • Keep records of consent source, timestamp, form text, IP address where available, phone number, person consenting, seller named, and campaign purpose.
  • Do not rely on purchased leads, scraped lists, affiliate lists, aged leads, or broad consent unless you can prove the consent satisfies current law and applies to your specific outreach.

3. Opt-Out And Revocation

  • Honor opt-outs, revocations of consent, unsubscribe requests, STOP messages, Do Not Call requests, and internal suppression requests promptly.
  • Make opt-out simple and available through reasonable channels.
  • Do not require a user to create an account, pay a fee, talk to a sales representative, or use an unreasonable process to revoke consent.
  • Keep suppression lists and do not re-upload or re-contact opted-out numbers unless a lawful new consent record exists.

4. Do Not Call And Quiet Hours

  • Scrub campaigns against applicable National Do Not Call, state Do Not Call, company-specific Do Not Call, and suppression lists before contacting recipients.
  • Observe permitted calling hours and stricter state rules where applicable.
  • Train agents and vendors to record and honor Do Not Call requests during live calls.
  • Monitor complaint rates, carrier blocking, spam labels, and opt-out rates.

5. Caller ID And Identification

  • Use accurate caller ID and do not spoof, rotate, or misrepresent numbers to deceive recipients or evade blocking.
  • Identify the business clearly at the beginning of calls and in message content where required.
  • Include required disclosures in SMS, WhatsApp, prerecorded messages, and AI-assisted outreach.
  • Use numbers that you are authorized to use and that match the purpose, geography, and campaign registration where applicable.

6. AI, Prerecorded, And Automated Outreach

AI-generated or AI-assisted calling and messaging may still be regulated as telemarketing, prerecorded voice, artificial voice, autodialed communications, or robotexting depending on the facts. Customers must evaluate whether AI voice, AI summaries, power dialing, preview dialing, click-to-call, APIs, programmable voice, and campaign automation require consent, disclosures, or restrictions.

7. Required Customer Records

  • Consent records and form language.
  • Opt-out and suppression logs.
  • Campaign content, scripts, message templates, and call recordings where lawfully retained.
  • Dialing method, vendor, lead source, and contact list provenance.
  • Do Not Call scrub records.
  • Complaints, carrier notices, remediation steps, and training records.

8. Enforcement

CallOrbit may require proof of consent, campaign details, scripts, message templates, lead sources, and suppression records. CallOrbit may block, throttle, suspend, or terminate campaigns, numbers, users, or accounts that present TCPA, carrier, recipient, legal, or reputational risk.

9. Sample Consent Language

Example language for a U.S. marketing SMS or call form: By submitting this form, I authorize [your business name] to contact me at the phone number provided with calls and text messages, including marketing messages sent using automated technology or prerecorded/artificial voice. Consent is not a condition of purchase. Message and data rates may apply. Message frequency varies. Reply STOP to opt out and HELP for help.

Customers must adapt consent language to their business, campaign, audience, state law, industry rules, and legal review. Do not use this sample unless it accurately describes your actual outreach and legal obligations.

Quick answers

  • Does TCPA apply to business SMS? - Yes, TCPA and related FCC rules can apply to texts, including marketing texts and robotexts to U.S. numbers.
  • Can I use purchased lead lists? - Only if you can prove valid, specific, current, legally sufficient consent for your business and campaign. Purchased lists are high risk.
  • Does AI calling avoid TCPA rules? - No. AI-assisted or AI-generated outreach may still trigger TCPA, state, carrier, and disclosure rules depending on how it is used.