ISV and multi-brand registration
If you are an Independent Software Vendor (ISV) or platform that sends messages on behalf of other brands, additional requirements apply.
Brand contact email
The brand contact must represent the actual brand owner, not the ISV sending on its behalf. The brand contact email must use the end-brand's domain.
Priority order:
Preferred: End-brand's own domain (for example, name@yourbrand.com)
Acceptable for government brands: Official parent agency domain (for example, if the brand is a government program, the parent department's domain is acceptable)
Not sufficient: ISV/vendor domain — unless there is a publicly verifiable reference on the end-brand's website or privacy policy explicitly authorizing the ISV to act as brand contact
Important
The reviewer verifies the brand contact by checking whether the email domain connects to the brand in the registration. If you are an ISV, you must provide a contact at the end-brand's organization, not your own.
For government brands: If the brand is a government program or agency, use an official government domain email. If the program doesn't have its own domain, the parent department's domain is acceptable.
Affiliate marketing restriction
Each RCS agent must represent a single brand. If your campaign description suggests that multiple brands will send messages through one agent, the registration is denied as affiliate marketing.
Compliant (ISV pattern): "ExamplePlatform sends appointment reminders and service notifications on behalf of ExampleBrand."
Non-compliant: "Our platform enables multiple healthcare brands to send messages to their customers." — This describes affiliate marketing (multiple brands, one agent).
ISV checklist
Brand contact email uses the end-brand's domain (not your ISV domain)
Brand contact person is someone at the end-brand's organization
Registration clearly identifies the single brand this agent represents
Campaign description references a single brand, not multiple brands
If ISV domain must be used: publicly verifiable authorization exists on the end-brand's website or privacy policy