The rules for sending on AgentMessage.

1. Scope

This Messaging Policy is incorporated into the Terms of Service and applies to every message sent through AgentMessage, including outbound SMS, outbound MMS, and any other channel we support, on every account type and plan tier. By using the Service you agree to this policy.

This policy is in addition to applicable law (including the Telephone Consumer Protection Act, the CAN-SPAM Act, state telecom statutes), the published rules of carriers (mobile network operators), the rules of registries (including The Campaign Registry), and the rules of our upstream providers. Where this policy is more permissive than applicable law or carrier rules, the stricter requirement controls.

Customers are also subject to the CTIA Messaging Principles and Best Practices and any successor industry guidelines published by CTIA, the Cellular Telecommunications Industry Association.

2. Consent

You may send messages only to recipients who have provided valid consent for the specific brand, use case, message type, and phone number being used. Consent must be affirmative, traceable, and appropriate for the message content and frequency.

2.1 Consent records

You are responsible for maintaining sufficient evidence of consent. Where the Service captures consent records, those records may include phone number, timestamp, IP address, source URL, consent language, campaign or use case, user agent, form identifier, and related metadata. AgentMessage consent records are intended to help evidence consent but do not replace your obligation to maintain any required source records.

2.2 Form-fill consent

For form-fill consent, the form must clearly disclose the brand sending messages, the types of messages, expected frequency where applicable, that message and data rates may apply, and how to opt out. Consent must not be hidden, bundled in unrelated terms, or obtained through deceptive interface design. Pre-checked boxes are not consent.

2.3 Inbound conversational consent

An inbound message from a recipient may authorize a reasonable conversational response related to the recipient's message. Inbound conversational consent is limited to the brand, phone number, topic, and context reasonably apparent from the recipient's inbound message.

Inbound consent does not authorize unrelated marketing, recurring campaigns, third-party offers, lead-reactivation outreach, abandoned-cart campaigns, promotional blasts, or materially different use cases unless the recipient separately provides valid consent for that use.

2.4 Consent capture surfaces

AgentMessage supports several consent-capture patterns: an API endpoint that records consent you have collected elsewhere, a hosted form that we operate behind a short-lived signed token, and a double-opt-in confirmation flow that asks the recipient to confirm from their handset before consent is recorded. Stronger evidence is always preferable; certain regulators and carriers require it. Choose the pattern that matches the strength of evidence your use case requires.

2.5 The consent gate

AgentMessage enforces consent at the API layer. A request to send a message will fail with a CONSENT_REQUIRED error if no consent record exists for the recipient and sender pair, or if the recipient has previously opted out. You should not retry such a request without first obtaining a fresh, valid consent; repeatedly attempting to send to opted-out recipients is a violation of this policy and can trigger suspension.

3. AI agents and automated systems

If you use AI agents or automated systems with the Service, you are responsible for configuring, supervising, testing, and monitoring those systems. AI-generated content must comply with this Messaging Policy, applicable law, carrier rules, and recipient consent. You may not use an AI agent to evade consent requirements, opt-out requests, rate limits, quiet hours, prohibited-content rules, or enforcement controls.

You are also responsible for: (a) clear and conspicuous disclosure to recipients that they are interacting with an AI system, in accordance with applicable state law (including but not limited to California's Bolstering Online Transparency Act, California SB 243, the Utah Artificial Intelligence Policy Act, the Colorado Artificial Intelligence Act, Washington HB 2225, Oregon SB 1546, Tennessee SB 1580, Nebraska LB 525, and New York General Business Law Article 47), as those laws apply to your use case, vertical, and recipient base; (b) any third-party-processing disclosures required by applicable privacy or wiretap law (including but not limited to the California Invasion of Privacy Act and analogous all-party-consent statutes in Massachusetts, Illinois, Florida, Pennsylvania, Maryland, Washington, Connecticut, Delaware, Michigan, Montana, Nevada, New Hampshire, Oregon, and Vermont); and (c) accurate disclosure of your use of any large language model, content-generation service, or other third-party AI processor in connection with messages sent through the Service.

AgentMessage may provide optional platform features that prepend AI disclosure language to outbound messages, vary disclosure cadence based on recipient state, or capture consent acknowledgments at opt-in. These features are provided for convenience and reflect AgentMessage's good-faith reading of the relevant state laws as of the effective date of this policy. They do not constitute legal advice, are not a guarantee of compliance with any specific statute, and do not relieve you of your obligation to evaluate whether the disclosure language and cadence applied to your traffic satisfies your obligations.

4. STOP, opt-out, and HELP handling

Recipients have the right to opt out at any time. You must honor opt-out requests immediately, regardless of the channel through which the request is received.

Opt-out by any reasonable means.Under the FCC's February 2024 amendments to the TCPA implementing rules (with a compliance date in April 2025), a recipient may revoke prior express consent through any reasonable means. You must honor opt-out requests received through any reasonable channel, including SMS reply, email reply, dashboard request, customer-support contact, written request, telephone call, in-app form, voicemail, or any other channel where the recipient's intent to opt out is clear. The SMS keyword set automatically detected by the Service is a baseline, not the limit. When you receive an opt-out through any other channel, you are responsible for promptly recording the opt-out in the Service so that future send attempts are blocked.

STOP and equivalents. AgentMessage may process standard opt-out keywords including STOP, END, CANCEL, QUIT, and UNSUBSCRIBE, and may suppress future messages to opted-out recipients. You may not attempt to bypass, override, re-import, or message around suppression records.

START and resubscribe.Where supported, recipients may resubscribe using START, UNSTOP, or similar keywords. Resubscription applies only where legally valid and technically supported, and only on the recipient's initiative. You may not direct a previously-opted-out recipient to send a re-subscribe keyword as a workaround for a missing opt-in.

HELP. You must provide accurate HELP or support information where required, including brand identity and a reasonable method for recipients to obtain assistance.

Carriers may require additional keywords or behaviors from time to time. We update keyword detection in lockstep with those changes; you are responsible for staying current.

5. Quiet hours

AgentMessage may provide quiet-hour controls or restrictions, but you remain responsible for complying with all federal, state, local, carrier, and industry-specific calling and messaging time restrictions. You are responsible for correctly configuring recipient time zones, campaign settings, and automation behavior.

6. Prohibited content and use cases

You may not use the Service for messages involving any of the following, regardless of consent:

• Healthcare or protected health information (PHI), including any use case requiring HIPAA compliance or a Business Associate Agreement.
• Schools, educational institutions, or messaging to or about minors.
• Political campaigns, electioneering, political fundraising, or political persuasion.
• Cannabis, CBD, marijuana, or related products, regardless of state-level legality.
• Alcohol.
• Tobacco, vape, e-cigarette, nicotine, and related products.
• Adult sexual content or services.
• Gambling, betting, casinos, sweepstakes, or games of chance.
• Firearms, weapons, ammunition, or regulated weapon accessories.
• Illegal products, services, or activities.
• Deceptive, fraudulent, phishing, impersonation, or scam content.
• Hate, harassment, threats, or abusive content.
• Content prohibited by law, carrier rules, The Campaign Registry requirements, CTIA guidelines, or our upstream providers.

7. Restricted categories

The following categories require prior written approval from AgentMessage and may be subject to enhanced review, lower throughput, additional consent requirements, or additional documentation: financial services, lending, credit, insurance, real estate, legal services, employment and recruiting, high-volume lead generation, affiliate marketing, debt-related communications, and other categories we designate as higher risk. If you intend to operate a program in a restricted category, tell us during onboarding so we can guide you through the additional vetting carriers require.

8. Program conduct

• One program per consent. Do not use consent obtained for one program to send for a different program. Capture and track consent separately when you operate multiple programs.
• Sender identification. Identify your brand in each message in a way that the recipient can recognize. Do not impersonate another brand or pretend the message is from a person who did not author it.
• URL practices. Carriers filter generic URL shorteners aggressively. Use branded short links or full URLs. We may reject or filter traffic that uses certain shorteners.
• Frequency. Do not exceed the message frequency you disclosed at opt-in. If your frequency materially changes, capture fresh consent.
• Reasonable retry behavior. Do not retry a send that returned a permanent failure (including CONSENT_REQUIRED, recipient opt-out, and carrier-permanent rejections). Respect rate limits and Retry-After headers.

9. Brand and campaign registration (10DLC)

U.S. SMS and MMS traffic to mobile numbers must be sent from a registered Brand and an approved Campaign under the 10DLC framework administered by The Campaign Registry. Y3 Labs LLC acts as the Campaign Service Provider for these registrations on your behalf. You are responsible for providing accurate brand identity information and an honest description of every campaign. False or misleading registration data is a basis for immediate suspension. Carriers and registries may impose non-refundable penalties.

You may not send messages that differ materially from the approved campaign, use case, sample messages, brand, consent flow, or recipient expectations. We may block or suspend messaging that appears inconsistent with approved registration materials.

Lead generation one-to-one consent. Lead generation, lead reactivation, and lead resale are subject to the FCC's January 2025 amendments to the TCPA implementing rules requiring one-to-one consent for prerecorded and autodialed messaging in the lead generation context. You are responsible for obtaining one-to-one consent where the FCC's amended rules apply to your traffic. Consent obtained for a list of “marketing partners” without per-seller consent is not valid one-to-one consent.

10. Enforcement controls

AgentMessage may use automated and manual controls to detect, prevent, limit, or respond to suspected violations, including opt-out suppression, HELP and STOP handling, daily outbound limits, contact caps, ratio limits, quiet-hour controls, prohibited-content detection, repeated-message detection, complaint monitoring, high-risk keyword review, campaign mismatch detection, account review, throttling, blocking, suspension, or termination.

These controls do not relieve you of responsibility for your messaging activity. Failure by AgentMessage to detect, block, or suspend a message, campaign, number, or account does not mean that the activity is compliant.

11. Rate limits and operational limits

AgentMessage may impose sending limits, contact limits, inbound-to-outbound ratio requirements, throughput limits, number limits, campaign limits, or other operational limits by plan, account, number, campaign, or use case. Limits may be changed to manage risk, carrier requirements, system health, or compliance obligations. Send-attempts above your current limit are rejected with a 429 RATE_LIMITED response and a Retry-After header.

12. Data you process through the Service

You may only process data through the Service for which you have lawful authority. You may not send messages that contain another person's sensitive personal information without their authorization. The Privacy Policy describes how we handle data; the Data Processing Addendum describes processor obligations for customers who require one.

13. Enforcement ladder and consequences

When we detect a likely violation we may, depending on severity:

• Send a written warning and require remediation.
• Reduce throughput tier for the affected account.
• Suspend the affected campaign, account, or message category.
• Terminate the account under the Terms of Service and report the conduct to the relevant carrier or registry.
• Pass through fines or penalties imposed by carriers, registries, or regulators that are attributable to your traffic, and recover those amounts from the wallet balance, refunds, or invoices.

Repeat or willful violations result in termination without refund. We may report fraud or illegal activity to law enforcement.

14. Reporting abuse

If you receive an unwanted message that you believe was sent through AgentMessage, or you suspect abuse of the Service, email abuse@agentmessage.io with the sender phone number, the recipient phone number, and a screenshot of the message if possible. We review abuse reports and may investigate, prioritize, or take action based on severity, credibility, and available information.

15. Changes to this policy

We may update this policy as carrier rules, regulator guidance, and the Service evolve. Material changes will be communicated to the billing contact on file by email. We aim to provide reasonable advance notice, but, while AgentMessage is in startup mode, we may apply changes with as little as 24 hours' notice. Changes required by law, carrier directive, or to address a security or compliance issue may take effect immediately.

16. Contact

For questions about this policy, contact legal@agentmessage.io. For abuse reports, contact abuse@agentmessage.io.