AWS sms-voice documentation change
Summary
Expanded RCS country launch documentation from US/Canada focus to 22 countries globally. Removed country-specific sections and replaced with links to individual country launch guides. Restructured content flow and updated approval timelines.
Security assessment
The changes involve documentation restructuring and geographic expansion without any mention of security vulnerabilities, patches, or security enhancements. Updates focus on administrative processes and country-specific requirements.
Diff
diff --git a/sms-voice/latest/userguide/rcs-country-launch.md b/sms-voice/latest/userguide/rcs-country-launch.md index 9ec03045f..f66d0d124 100644 --- a//sms-voice/latest/userguide/rcs-country-launch.md +++ b//sms-voice/latest/userguide/rcs-country-launch.md @@ -7 +7 @@ -Testing registrationTesting agent as a template for country launchesLaunching in the United StatesLaunching in CanadaUse case selectionRegistration state managementPer-carrier launch statusCarrier approval timelinesCommon registration issues and troubleshooting +Testing registrationTesting agent as a template for country launchesUse case selectionRegistration state managementPer-carrier launch statusCarrier approval timelinesCommon registration issues and troubleshooting @@ -11 +11 @@ Testing registrationTesting agent as a template for country launchesLaunching in -After you have tested your RCS messaging integration using a testing agent, the next step is to launch your AWS RCS Agent in one or more countries. Each country launch creates a separate RCS for Business ID that is approved for each carrier in that country. AWS End User Messaging supports RCS country launches in the United States and Canada. +After you have tested your RCS messaging integration using a testing agent, the next step is to launch your AWS RCS Agent in one or more countries. Each country launch creates a separate RCS for Business ID that is approved for each carrier in that country. AWS End User Messaging supports RCS country launches in 22 countries across North America, South America, Europe, and Asia Pacific. @@ -13 +13 @@ After you have tested your RCS messaging integration using a testing agent, the -The country launch process follows this path: you create an AWS RCS Agent, submit a testing registration to get a testing agent, and then submit one or more country launch registrations. Each country launch registration goes through a separate approval process for each carrier in that country. +The country launch process follows this path: you create an AWS RCS Agent, submit a testing registration to get a testing agent, and then submit one or more country launch registrations. Each country launch registration goes through a separate approval process for each carrier in that country. For the full list of supported countries, see [Supported countries for RCS](./rcs-supported-countries.html). @@ -27,4 +26,0 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W - * Launching in the United States - - * Launching in Canada - @@ -41 +37 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W - * [RCS country launch compliance guide](./rcs-country-launch-compliance.html) + * [Standard country launch registration](./rcs-country-launch-standard.html) @@ -42,0 +39 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W + * [Launching RCS in Austria](./rcs-country-launch-at.html) @@ -43,0 +41 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W + * [Launching RCS in Brazil](./rcs-country-launch-br.html) @@ -44,0 +43 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W + * [Launching RCS in Canada](./rcs-country-launch-ca.html) @@ -46 +45 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W -## Testing registration + * [Launching RCS in France](./rcs-country-launch-fr.html) @@ -48 +47 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W -Before you can submit a country launch registration, you must first complete a testing registration for your AWS RCS Agent. The testing registration creates a testing agent (an RCS for Business ID) that you can use to validate your integration before going to production. + * [Launching RCS in Germany](./rcs-country-launch-de.html) @@ -50 +49 @@ Before you can submit a country launch registration, you must first complete a t -For step-by-step instructions on creating an AWS RCS Agent and completing the testing registration, see [Getting started with RCS](./rcs-getting-started.html). For details on managing test devices and sending test messages, see [Testing RCS messages](./rcs-testing.html). + * [Launching RCS in Mexico](./rcs-country-launch-mx.html) @@ -52 +51 @@ For step-by-step instructions on creating an AWS RCS Agent and completing the te -###### Important + * [Launching RCS in the Netherlands](./rcs-country-launch-nl.html) @@ -54 +53 @@ For step-by-step instructions on creating an AWS RCS Agent and completing the te -Testing messages are charged at standard RCS rates. + * [Launching RCS in Peru](./rcs-country-launch-pe.html) @@ -56 +55 @@ Testing messages are charged at standard RCS rates. -## Testing agent as a template for country launches + * [Launching RCS in Singapore](./rcs-country-launch-sg.html) @@ -58 +57 @@ Testing messages are charged at standard RCS rates. -###### Important + * [Launching RCS in Spain](./rcs-country-launch-es.html) @@ -60,5 +59 @@ Testing messages are charged at standard RCS rates. -The testing agent serves as the template for all your country launch registrations. The brand configuration you set during testing registration is what gets pre-populated into each country launch form. Take time to get your testing agent configuration right before submitting country launches. - -When you submit a country launch registration, the AWS End User Messaging console auto-populates the registration form with the brand configuration from your testing agent. This includes your brand name, logo, banner image, brand color, description, and website URL. - -You can customize fields for each country launch. For example, you might adjust the consumer-facing agent name, logo, banner image, or contact information to match local requirements. Countries can have different brand assets. The testing agent provides the starting point, but each country launch can be customized independently. + * [Launching RCS in the United Kingdom](./rcs-country-launch-gb.html) @@ -66 +61 @@ You can customize fields for each country launch. For example, you might adjust -## Launching in the United States + * [Launching RCS in the United States](./rcs-country-launch-us.html) @@ -68,7 +63 @@ You can customize fields for each country launch. For example, you might adjust -To launch your AWS RCS Agent in the United States, submit a country launch registration using the `US_RCS_LAUNCH` registration type. The US launch registration requires additional information beyond what you provided for the testing registration. - -### US registration requirements - -The US launch registration requires the following information: - - * **Brand information** — Auto-populated from your testing agent configuration. You can review and adjust the brand name, description, website URL, and contact information. + * [RCS country launch compliance guide](./rcs-country-launch-compliance.html) @@ -76 +64,0 @@ The US launch registration requires the following information: - * **Use case selection** — Select the use case category for your RCS messaging. Available categories include OTP (one-time passwords), Transactional, Promotional, and Multi-use. @@ -78 +65,0 @@ The US launch registration requires the following information: - * **Screen recording** — You must provide a screen recording that demonstrates your RCS messaging experience. The recording should show the end-user experience of receiving and interacting with your RCS messages. For detailed video requirements, see [Launch video requirements](./rcs-compliance-video.html). @@ -80 +66,0 @@ The US launch registration requires the following information: - * **Privacy policy and terms of service** — URLs to your privacy policy and terms of service pages. @@ -81,0 +68 @@ The US launch registration requires the following information: +## Testing registration @@ -82,0 +70 @@ The US launch registration requires the following information: +Before you can submit a country launch registration, you must first complete a testing registration for your AWS RCS Agent. The testing registration creates a testing agent (an RCS for Business ID) that you can use to validate your integration before going to production. @@ -83,0 +72 @@ The US launch registration requires the following information: +For step-by-step instructions on creating an AWS RCS Agent and completing the testing registration, see [Getting started with RCS](./rcs-getting-started.html). For details on managing test devices and sending test messages, see [Testing RCS messages](./rcs-testing.html). @@ -87,17 +76 @@ The US launch registration requires the following information: -Both the US and Canada launch registrations require a screen recording. You must provide a recording that clearly demonstrates your RCS messaging use case. Registrations submitted without a valid screen recording are rejected. For detailed requirements, see [Launch video requirements](./rcs-compliance-video.html). - -## Launching in Canada - -To launch your AWS RCS Agent in Canada, submit a country launch registration using the `CA_RCS_LAUNCH` registration type. The Canada launch registration has different form field requirements than the US launch. - -### Canada registration requirements - -The Canada launch registration requires the following information: - - * **Brand information** — Auto-populated from your testing agent configuration. You can review and adjust the brand name, description, website URL, and contact information for the Canadian market. - - * **Use case selection** — Select the use case category for your RCS messaging. Available categories include OTP (one-time passwords), Transactional, Promotional, and Multi-use. - - * **Screen recording** — You must provide a screen recording that demonstrates your RCS messaging experience. For detailed video requirements, see [Launch video requirements](./rcs-compliance-video.html). - - * **Privacy policy and terms of service** — URLs to your privacy policy and terms of service pages. +Testing messages are charged at standard RCS rates. @@ -104,0 +78 @@ The Canada launch registration requires the following information: +## Testing agent as a template for country launches @@ -105,0 +80 @@ The Canada launch registration requires the following information: +###### Important @@ -106,0 +82 @@ The Canada launch registration requires the following information: +The testing agent serves as the template for all your country launch registrations. The brand configuration you set during testing registration is what gets pre-populated into each country launch form. Take time to get your testing agent configuration right before submitting country launches. @@ -108 +84 @@ The Canada launch registration requires the following information: -###### Note +When you submit a country launch registration, the AWS End User Messaging console auto-populates the registration form with the brand configuration from your testing agent. This includes your brand name, logo, banner image, brand color, description, and website URL. @@ -110 +86 @@ The Canada launch registration requires the following information: -The Canada launch registration form field requirements differ from the US launch registration. A screen recording is required for both countries. Review the registration form carefully to ensure all required fields are completed for the Canadian market. +You can customize fields for each country launch. For example, you might adjust the consumer-facing agent name, logo, banner image, or contact information to match local requirements. Countries can have different brand assets. The testing agent provides the starting point, but each country launch can be customized independently. @@ -290 +266 @@ Carrier approval for RCS country launches is a multi-step process that involves -For both the United States and Canada, expect the carrier approval process to take several months from the time you submit your country launch registration. The timeline includes the initial review, any required updates, and the per-carrier rollout. +Expect the carrier approval process to take several months from the time you submit your country launch registration. Timelines vary by country and carrier. The timeline includes the initial review, any required updates, the per-carrier rollout, and any out-of-band verification steps required by specific countries. @@ -343 +319 @@ Address the rejection feedback and submit a new registration version. Note that -Carrier approval timelines for the United States and Canada are typically several months. If your registration has been in the REVIEWING state for longer than expected: +Carrier approval timelines vary by country and can take several months. If your registration has been in the REVIEWING state for longer than expected: @@ -366 +342 @@ Receiving inbound RCS messages -RCS country launch compliance guide +Standard country launch registration