TCPA / A2P Compliance Policy

Last updated: May 7, 2026

Plain-English summary

CloudGreet is a voice-first AI receptionist. The only automated text message we send today is a single booking-confirmation SMS to a caller after they schedule an appointment with one of our customers. We do not send marketing texts, broadcast campaigns, or proactive reminder / follow-up messages. STOP / HELP / UNSTOP keywords are honored. This page describes that program in detail.

1. What this policy covers

The Telephone Consumer Protection Act (TCPA) and the carrier-driven Application-to-Person (A2P) framework regulate automated calls and text messages to consumers in the United States. CloudGreet operates a narrow text-message program in support of voice calls, described below. This policy explains what we send, on whose behalf, and how a recipient can opt out.

2. Messages we send today

The only automated message CloudGreet sends in the current product is:

Booking confirmation

Triggered when our customer's AI agent books an appointment during a phone call. The SMS contains the appointment date, time, and service requested, plus the line “Reply STOP to opt out; HELP for help.” Sent from the customer's assigned outbound number, not a generic CloudGreet number.

We do not send marketing messages, broadcast campaigns, surveys, drip sequences, reminder messages, follow-up messages, or any other text traffic without an explicit policy update. If we add new message categories in the future this page will be updated and existing recipients will be notified before the new traffic begins.

3. Consent

The booking-confirmation SMS is sent only to a phone number that the recipient provided directly to our customer's AI agent during a live inbound call for the express purpose of receiving that confirmation. This is the kind of transactional, single-message confirmation that carriers and regulators treat as having implied consent given the call context. We do not import contact lists, buy phone numbers, or send messages to numbers obtained outside the active call that triggered the message.

4. Opt-out (STOP / HELP / UNSTOP)

Every outbound message ends with the line “Reply STOP to opt out; HELP for help.” Inbound messages on those numbers are routed to our SMS webhook which handles the standard keywords:

  • STOP — future messages to that number are blocked. We reply once with confirmation: “You have been opted out. Reply UNSTOP to rejoin.”
  • UNSTOP — reverses an opt-out. We reply once with “You have been opted in again. Reply STOP to opt out; HELP for help.”
  • HELP — we reply with our identity line and instructions: “CloudGreet: Reply STOP to opt out; HELP for help.”

Opt-out status is stored against the phone number; the same number cannot be re-messaged until UNSTOP is received. You can also opt out by replying to any message with the words cancel, end, quit,or unsubscribe; we treat all of these the same as STOP.

5. Identity and disclosures in every message

Every SMS we send includes:

  • The sending business's name (our customer's name — e.g. “ABC Plumbing”), so the recipient knows who is texting.
  • The purpose of the message (the booked appointment).
  • The opt-out instruction (Reply STOP to opt out).

6. Carrier registration

A2P 10DLC registration is the carrier-mandated process for application-originated messaging in the US. Where required by our messaging provider for the volume and content of traffic above, we register our brand and use cases through Telnyx's 10DLC portal. We do not send messages on a use case for which the carrier registration is incomplete or pending.

7. Customer responsibilities

If you are a CloudGreet customer (a business using our service):

  • You may only use CloudGreet to receive calls from people who chose to call you. You may not import outbound campaigns or contact lists into our service.
  • You must be the actual owner of the business name and phone numbers configured on your account.
  • You may not configure the AI agent to deceive callers about the sending business's identity.
  • You acknowledge that the booking-confirmation SMS is sent under your business's name, and you are responsible for honoring the appointment that triggered it.

8. Recordkeeping

Every outbound message and inbound reply is logged with timestamp, phone numbers, and full message text in our sms_messages table. Opt-out events are durable. We retain these records for at least four years to support carrier audits and consumer complaints.

9. Reporting violations

If you believe you received an SMS from CloudGreet or one of our customers that does not comply with this policy, write to anthony@cloudgreet.com with the message in question (screenshot or forwarded text). We investigate every report and respond within 5 business days.

10. Changes to this policy

We may update this page when we change what messages we send, add a new use case, or in response to changes in TCPA / A2P rules. The “Last updated” date at the top reflects the most recent change. Material changes will be communicated to active customers in advance.

11. Contact

Questions, opt-out problems, or compliance reports go to anthony@cloudgreet.com or through our contact page. CloudGreet is operated from Austin, Texas.

Legal disclaimer

This page is provided for informational purposes and does not constitute legal advice. It is intended to describe CloudGreet's current SMS practices accurately so consumers and customers can make informed decisions; it is not a substitute for advice from qualified counsel about your specific situation.