Communications Terms and Consent Notice

Effective date: March 1, 2026 · Last updated: March 1, 2026

Use this page for Twilio and carrier compliance reviews: OpsAVO’s own messaging program, consent standards, and how platform customers remain responsible for their campaigns.

This Communications Terms and Consent Notice explains how OPSAVO LLC ("OpsAVO") handles SMS, MMS, phone, voicemail, AI voice, email, and similar communications for its own business operations and through the OpsAVO platform.

1. Scope

This page applies to:

  1. communications sent by OpsAVO about OpsAVO's own services; and
  2. communications tools made available through the OpsAVO platform to business customers.

OpsAVO customers are independently responsible for their own communications programs, consent flows, message content, use cases, registrations, and legal compliance.

2. OpsAVO's Own Communications Program

Program Name: OpsAVO Account & Service Alerts

OpsAVO may send transactional or conversational communications relating to:

  • account alerts;
  • onboarding updates;
  • billing notices;
  • support updates;
  • security alerts;
  • demo or appointment reminders;
  • service notifications; and
  • other account or service-related communications you request or reasonably expect based on your interaction with OpsAVO.

OpsAVO does not use this program for general promotional or marketing SMS campaigns.

3. How You May Opt In to OpsAVO Communications

You may opt in to receive communications from OpsAVO through one or more of the following methods:

  • a website demo form;
  • account signup;
  • in-app notification settings;
  • a support form;
  • verbal consent that is documented by OpsAVO; or
  • another clear consent flow presented by OpsAVO.

Where a checkbox is used for SMS consent, it will be presented as a separate consent action and should not be preselected.

Consent to receive communications is not a condition of purchase.

4. Standard Disclosures

For recurring or ongoing communications, the following disclosures apply unless a more specific disclosure is shown at the point of collection:

  • message frequency varies;
  • message and data rates may apply;
  • reply STOP to opt out of SMS;
  • reply HELP for help where supported; and
  • consent is not a condition of purchase.

OpsAVO will make commercially reasonable efforts to honor opt-out requests, but you are responsible for ensuring your carrier and device can receive and send the relevant messages.

5. Email Communications

OpsAVO may also send service-related emails, including onboarding emails, billing notices, support responses, account notices, security notices, and other transactional or relationship messages. Marketing emails, if any, will include unsubscribe functionality where required by law.

6. Customer Messaging Through the OpsAVO Platform

OpsAVO may provide customers with messaging and communications tools, including support for toll-free numbers, local 10DLC numbers, and ported numbers.

Each customer is independently and solely responsible for:

  • obtaining and documenting all required consents;
  • maintaining compliant opt-in language, disclosures, and terms;
  • selecting lawful content and use cases;
  • maintaining records of consent and revocation;
  • honoring STOP, HELP, and other required responses where applicable;
  • ensuring message frequency and campaign scope match the consent obtained;
  • ensuring registration information, business information, and campaign details are accurate; and
  • complying with all carrier, provider, telecom, privacy, and marketing rules.

OpsAVO provides tools on a best-effort basis and may surface statuses, templates, prompts, or guidance, but Customer remains solely responsible for final verification, compliance, and use.

7. Provider and Delivery Limitations

OpsAVO is not a carrier and does not guarantee message delivery, routing, throughput, number approval, registration approval, number availability, sender reputation, inbox placement, or uninterrupted communications service.

Message blocking, filtering, latency, carrier rejection, registration rejection, or delivery failure may occur due to provider policies, carrier rules, registration requirements, recipient device issues, spam controls, legal restrictions, or other factors outside OpsAVO's control.

8. Privacy and Sharing

OpsAVO does not share mobile opt-in data or SMS consent status with third parties or affiliates for their own marketing or promotional purposes.

OpsAVO may share communications-related information with its service providers and subprocessors as needed to provide the Services, enforce policies, prevent fraud, and comply with legal or provider requirements.

9. Support Contact

For questions about OpsAVO's own communications program, contact [email protected], unless OpsAVO designates a different support contact in the applicable message, form, or workflow.

10. Sample SMS Checkbox / CTA Disclosure

Example checkbox label:

[ ] I agree to receive transactional text messages from OpsAVO about my account, onboarding, billing, support, security, and service updates. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help. Consent is not a condition of purchase.

Example short form disclosure for signup or demo forms:

By providing your mobile number and checking the SMS consent box, you agree to receive transactional text messages from OpsAVO related to your account, onboarding, billing, support, security, and service updates. Message frequency varies. Message and data rates may apply. Reply STOP to opt out and HELP for help. Consent is not a condition of purchase.

Example verbal consent script:

"We can send you text messages from OpsAVO about your account, onboarding, billing, support, security, and service updates. Message frequency varies, and message and data rates may apply. You can reply STOP to opt out or HELP for help. Consent is not required to purchase anything. Do you agree to receive these messages?"

If the recipient says yes, OpsAVO should document the date, time, phone number, and context of the consent. For how we handle personal information, see our Privacy Policy.