Carrier rules in plain English.

1. Terminology

The terms used in this notice carry the following meanings:

• Campaign Service Provider (CSP). The role Y3 Labs LLC, doing business as AgentMessage, holds with The Campaign Registry for 10DLC purposes. AgentMessage submits and manages brand and campaign registrations on behalf of customers in this role.
• Upstream provider or upstream carrier. The licensed messaging providers that originate and terminate SMS and MMS traffic on AgentMessage's behalf. Bandwidth is the current upstream provider.
• Mobile carriers (MNOs).The mobile network operators that deliver messages to recipient handsets, such as AT&T, T-Mobile, and Verizon.
• The Campaign Registry (TCR). The central registry for U.S. 10DLC brand and campaign registration.

The phrase “CSP” in this notice always refers to the Campaign Service Provider role with TCR. We do not use CSP to mean the upstream messaging carrier. Bandwidth and similar providers are referred to as upstream providers or upstream carriers.

2. Overview

In the United States, application-to-person (A2P) SMS and MMS traffic to mobile numbers is filtered, vetted, and rate-limited by mobile carriers under a framework commonly called 10DLC (10-digit long codes). The framework is administered through The Campaign Registry. Carrier and registry rules apply on top of federal law (most notably the TCPA and CAN-SPAM Act) and state telecommunications law. The Service currently supports messaging to mobile numbers in the United States only.

The CTIA Messaging Principles and Best Practices apply alongside the TCPA, CAN-SPAM, state law, and the carrier and registry rules described in this notice.

3. AgentMessage's Campaign Service Provider role

Y3 Labs LLC, doing business as AgentMessage, acts as a Campaign Service Provider for certain 10DLC workflows. As part of this role, AgentMessage may collect, prepare, review, submit, update, and manage brand and campaign information through The Campaign Registry and related carrier or provider systems.

Our CSP role does not transfer compliance responsibility to AgentMessage. You remain the originator of every message you send and the entity legally responsible for the content, recipient relationship, and consent posture behind that message.

4. Upstream providers

AgentMessage routes messaging through upstream providers, including Bandwidth. We may be required to share brand, campaign, customer, number, traffic, and compliance information with upstream providers and carriers for registration, routing, vetting, billing, deliverability, support, fraud prevention, and compliance.

Upstream providers and carriers may filter, throttle, suspend, or reject traffic according to their own rules. AgentMessage does not have authority to override carrier filtering decisions or aggregator-side enforcement actions.

5. Brand registration and vetting

A “Brand” is the legal entity that originates messages. To send to U.S. mobile recipients, your Brand must be registered with TCR and pass identity vetting. Vetting checks the legal name, business identifier (EIN or equivalent), country of registration, address, website, and other identity signals against external sources.

Vetting outcomes drive throughput, content latitude, and eligibility for certain campaign types. A higher vetting score produces higher throughput and access to a broader set of campaign types; a low score restricts both. Sole proprietors are subject to additional restrictions and lower default throughput.

You are responsible for providing accurate Brand information. Misrepresenting identity is a basis for immediate suspension, and TCR or carriers may impose non-refundable penalties or permanent disqualification. Updates to your Brand identity (name change, address change, EIN change, change of control) must be reflected in your AgentMessage account so we can update the registration.

6. Campaign registration and use cases

A “Campaign” is a specific messaging program tied to a Brand and a use case (for example, account notifications, two-factor authentication, marketing, customer care). Each Campaign declares the use case, sample messages, opt-in language, opt-out instructions, message frequency, and the types of recipients it targets. Carriers approve, throttle, or reject Campaigns based on the use case and the quality of the registration.

You may not run traffic on a Campaign that does not match the registered use case. If your use case changes, register a new Campaign or update the existing one before changing your traffic mix. Some use cases are prohibited or restricted; see the Messaging Policy for the prohibited and restricted lists.

7. No approval or deliverability guarantee

10DLC registration, brand vetting, campaign approval, number assignment, throughput, and message deliverability are controlled in part by The Campaign Registry, carriers, upstream providers, and other third parties. AgentMessage does not guarantee approval, deliverability, throughput, carrier acceptance, or avoidance of filtering. We use commercially reasonable efforts to support your registration and traffic; outcomes are not guaranteed.

8. Customer registration responsibility

You are responsible for ensuring that all brand, campaign, consent, website, privacy policy, terms, sample message, and business information is accurate, complete, current, and not misleading. Inaccurate or outdated registration information may cause carrier filtering, brand or campaign suspension, or pass-through fines.

9. Opt-in, opt-out, and HELP

Federal law and carrier rules require valid prior consent before you send any A2P message that is not a transactional message in the carrier-approved sense, and even transactional messaging is subject to opt-out rights. The Messaging Policy describes the consent patterns AgentMessage supports.

STOP keyword.A recipient who replies STOP, END, QUIT, CANCEL, or UNSUBSCRIBE (and reasonable casing variants) must be unsubscribed from the affected program immediately. AgentMessage automatically detects these keywords on inbound traffic, flips the recipient's consent state to opted-out, and rejects subsequent send attempts to that recipient. You will not delay, suppress, or attempt to recover opt-outs.

Lead generation one-to-one consent. The FCC's January 2025 amendments to the TCPA require one-to-one consent for prerecorded and autodialed messaging in the lead generation context. If your traffic involves lead generation, lead reactivation, or lead resale, you are responsible for obtaining the per-seller consent the amended rules require. The Messaging Policy describes this in more detail.

HELP keyword. A recipient who replies HELP or INFO must receive an informational reply identifying the program operator and providing a contact channel. We send this automatically; you may customize the response per program but you may not disable it.

START / UNSTOP. A recipient who has opted out may resubscribe themselves by replying START or UNSTOP. The recipient must initiate this; you may not direct a previously-opted-out recipient to send a re-subscribe keyword.

10. Throughput and rate limits

Carriers limit the maximum sustained message rate per Campaign and per Brand. AgentMessage exposes this through a per-account throughput tier that controls the rate we accept from your API. Throughput tiers are based on cumulative spend, compliance posture, and Brand vetting outcome. Tiers can move up and down over time. Send attempts above your current tier are rejected with a 429 RATE_LIMITED response and a Retry-After header.

11. Fees

SMS and MMS traffic incurs carrier and registry fees on messages and on Brand and Campaign registrations. Carrier, TCR, vetting, registration, surcharge, and similar third-party pass-through fees are passed through at cost unless expressly stated otherwise. AgentMessage separately charges platform, subscription, number, usage, and service fees as published on the pricing page or in your Order Form. Failed, blocked, filtered, or undelivered messages may still incur fees depending on the provider, carrier, and failure type.

Carrier and registry fees change outside our control. We update pass-through rates when our upstream rates change.

12. Carrier filtering

Carriers run their own message-content filters that operate independently of AgentMessage. A message that complies with this notice and the Messaging Policy can still be filtered by a carrier. Common filtering signals include URL shorteners, prohibited keywords, high opt-out rates, high complaint rates, sudden volume changes, suspicious sending patterns, and recipient-specific blocks. We surface the carrier's response on the message's delivery receipt. We do not have authority to override or appeal a carrier filtering decision. Repeated filtering events on a Campaign can trigger carrier-side throttling or suspension that we cannot override.

13. Number types

• Local 10DLC numbers. The default for most A2P traffic to U.S. mobile recipients. Subject to TCR Brand and Campaign registration, tiered throughput, and standard 10DLC rules.
• Toll-free messaging. Available with separate registration, separate vetting, separate pass-through fees, and separate routing. Treated as a future or limited channel under the Terms of Service.
• Short codes. 5- or 6-digit numbers provisioned through carrier-approved aggregator workflows. Long lead time, higher cost, highest throughput, strictest content rules. Available by special arrangement.

14. Future and limited channels

Toll-free messaging, RCS, iMessage, inbound voice, and other channels may have separate registration, consent, routing, compliance, carrier, provider, pricing, and policy requirements. These channels are treated as future or limited channels and may not be available on every plan. The Terms of Service govern their use; this notice will be updated when each channel is generally available.

15. United States scope

AgentMessage currently supports messaging to supported United States mobile numbers (+1 country code, U.S. mobile carriers). International messaging, including to Canadian numbers, is not currently supported. Operating outside that scope is a basis for suspension. We may add additional countries in the future; this notice will be updated when we do.

16. Customer obligations summary

The compliance burden is shared. The list below is the customer-side obligation set; AgentMessage cannot perform these on your behalf:

• Provide accurate Brand identity information and keep it current.
• Register every Campaign with an honest description and accurate sample messages.
• Capture and retain valid consent before sending. The Messaging Policy details the consent surfaces and the inbound conversational consent doctrine.
• Honor opt-outs immediately and do not retry sends to opted-out recipients.
• Comply with the prohibited and restricted content rules in the Messaging Policy.
• Stay current on TCPA and state law, including quiet-hours rules.
• Pay carrier and registry pass-through fees as billed.
• Cooperate promptly with our requests for information when we are responding to a carrier or regulator inquiry.

17. Consequences of non-compliance

Non-compliance can result in any combination of the following outcomes, from least to most severe: educational warning, throughput reduction, Campaign suspension, account suspension, account termination, pass-through of carrier or registry fines, and reporting to regulators. Repeat or willful violations result in termination without refund. The Terms of Service contains the suspension and termination framework.

18. Changes to this notice

Carrier and registry rules change frequently. We update this notice when rules change in ways that affect customers. The “Last updated” date at the top of the page reflects the most recent change. Material changes are 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 carrier directive or law may take effect immediately.

19. Contact

For questions about carrier compliance, contact legal@agentmessage.io or your AgentMessage account team. For abuse reports, contact abuse@agentmessage.io.