# Past releases (2019-2025)

## December 11, 2025

### New

**New field in `users.batchGet` response to group reachable users by carrier.
This field is only populated for US phone numbers.**

The [`users.batchGet`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/users/batchGet)
method in the RCS Business Messaging API now includes the `reachableUsersMap`
field in the response body to provide more detailed information on user
reachability.

`reachableUsersMap` is a map using carrier IDs as keys, with the values being
[`ReachableUsers`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/users/batchGet#reachableusers)
objects. This structure provides a list of US phone numbers for users reachable
on a specific carrier, helping you better understand potential reach on a
per-carrier basis.

## November 20, 2025

### New

**Billing update: unified Non-conversational billing category**

We simplified the billing structure by combining the two legacy billing
categories, **Basic Message** and **Single Message** , into one
**Non-conversational** category. Since the legacy categories had identical
billing logic, this change just simplifies your agent configuration.

From now on, every agent will be classified as either **Conversational** or
**Non-conversational**.

This change impacts the `RcsBusinessMessagingAgentBillingConfig` and applies to
all developers using the [Developer Console](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents#create)
or [Management API](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents#agent_creation_and_definition),
and all carriers using the
[Operations API](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api).

API users have a 90-day transition period (until February 18, 2026) to integrate
the new category across your systems.

For complete details about the transition plan, including API backward
compatibility and recommended code changes, refer to the [Billing FAQ](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq#non-conversational-category).
Here are the key points:

- **New agent creation (Developer Console)** : You can only create new agents as **Conversational** or **Non-conversational** in the [Developer Console](https://business-communications.cloud.google.com/console/partner-console).
- **New agent creation ([Management API](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/overview))** : You can still create agents using the legacy **Basic Message** and **Single Message** categories until February 18, 2026. However, we strongly recommend creating all new non-conversational agents using the new **Non-conversational** category starting now.
- **Existing agent migration (no action required)** : All agents classified as **Basic Message** or **Single Message** will be automatically moved to the **Non-conversational** category after February 18, 2026. You will receive a 30-day notice prior to this migration.
- **[Management API](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/overview) field update (for developers)** :
  - For backwards compatibility, the Management API will support both legacy (`BASIC_MESSAGE` and`SINGLE_MESSAGE`) and the new (`NON_CONVERSATIONAL`) values until February 18, 2026.
  - **Required action** : Update your agent logic to use the new `NON_CONVERSATIONAL` value **before** February 18, 2026. We recommend updating your agent logic now.
- **[Operations API](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/overview) field update (for carriers)** :
  - For backwards compatibility, the Operations API will return the deprecated `SINGLE_MESSAGE` value for agents marked as `NON_CONVERSATIONAL` until February 18, 2026.
  - **Required action** : Update your systems to handle the new `NON_CONVERSATIONAL` value **before** February 18, 2026.
  - **Opt-in** : Carriers may opt-in to receive the new `NON_CONVERSATIONAL` value before February 18, 2026. [Contact Support](https://developers.google.com/business-communications/rcs-business-messaging/support/overview#get-support) to request this change.

### New

We've updated our documentation to provide full details on the US billing
model for RCS for Business traffic on US carriers.

The US billing model uses content-based message classifications
(Rich Message, Rich Media Message, and Suggested Action Click) that differ from
the classifications used for non-US traffic.

To help you understand these changes, we've created the following resources:

- The [US billing model](https://developers.google.com/business-communications/rcs-business-messaging/carriers/billing/us-billing-model) guide details the classification logic and API/webhook structures for US traffic.
- The [Billing FAQ](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq) has been updated with a [new section](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq#billing-models) that summarizes the key differences between the US and standard billing models.

**For US carriers and partners launching agents on US carriers**: Please
review these documents to ensure your reporting and message classification
logic are correctly configured for US traffic.

## November 13, 2025

### Changed

**Site navigation and organization**

We've made several updates to the navigation of the site to improve
organization. To make information easier to find:

- We've added a new **What's new** section. This section now includes information about the [latest releases](https://developers.google.com/business-communications/rcs-business-messaging/whats-new/latest-releases), updates that are [coming soon](https://developers.google.com/business-communications/rcs-business-messaging/whats-new/coming-soon), as well as all [past release notes](https://developers.google.com/business-communications/rcs-business-messaging/whats-new/past-releases).
- We've renamed the **Early access** navigation link to [Early Access Programs](https://developers.google.com/business-communications/rcs-business-messaging/early-access).
- We've removed the **Sample conversations** page. Similar examples and showcases are now available on our new [marketing site](https://rcsforbusiness.google/) dedicated to RCS for Business.

## October 28, 2025

### New

The [Business Communications Developer Console](https://business-communications.cloud.google.com/console/partner-console)
now includes Unsubscribe Reason and Spam Trend data on the [Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview).

## October 23, 2025

### Changed

**Accurate engagement tracking for link previews**

We've updated the
[Send messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#basic_message_content_and_link_previews)
guide to clarify the use of link previews in text messages (including but not
limited to Basic Messages) and provide an example.

We've also added this important note for developers:

- To accurately measure user engagement by counting HTTP requests to a given URL, you must filter-out requests made by the link preview generation service. Exclude requests with user agent strings containing either "GoogleMessages" or "Google-PageRenderer".

## October 3, 2025

### Changed

We've updated the
[Acceptable Use Policy](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/aup)
to improve clarity and address new types of misuse. Here's a summary of the key
changes:

- Expanded the **Abuse of the product** section to include more examples of prohibited behavior, such as account hijacking, fraud, scams, and malware.
- Updated the **Misrepresentation and impersonation** section with new examples of content obfuscation.
- Added a new requirement to the **Consent requirements** section, which now requires brand-level compliance for consent revocation.
- Broadened the **Prohibited content** section to ban more types of harmful content, including child sexual abuse, non-consensual intimate imagery (NCII), and content related to violent organizations.
- Replaced specific restricted content categories (alcohol, gambling, and healthcare) with a broader **Regulated goods and services** topic.
- Clarified our policy that only one agent from a brand may deliver a specific content type to the same user.

## September 30, 2025

### Documentation enhancement

We've reorganized our terms and policies documentation to make it easier to
find.

- We've created a new [Terms and policies](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies) tab for the RCS for Business terms, policies, and data security documentation.
- We've also moved the [Carrier Terms of Service for RCS for Business](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/carriers/tos) to this new tab.

## September 26, 2025

### New

**Fix for truncation issues: New full-screen view for rich card carousels has
exited
[Google Messages Open Beta](https://support.google.com/messages/thread/9499609/join-the-messages-open-beta-program_)
and are now generally available in Google Messages**

This fix addresses a key pain point where text or suggestions on a rich card
carousel could be cut off due to height limitations. To make it clear when more
content is available, a **More** button now appears on truncated carousel cards.
A tap anywhere in the text area expands the card into a swipeable, full-screen
view, so users can always see the complete message.
Your browser does not support the video tag.

**Why we're making this change**

- **Improved user experience:** Eliminates user confusion from truncated content.
- **Enhanced message reliability:** Gives you greater confidence that your entire message---including critical details and calls-to-action---is delivered and viewable.
- **No developer action required:** This feature is enabled automatically for all rich card carousels without any changes to your agent.

For complete technical details on specifications, user interactions, and
suggestion behavior, refer to the updated
[Rich cards documentation](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards#full-screen-carousels).

## September 18, 2025

### Changed

To better align with the growing consumer recognition of RCS and to simplify
the platform's identity, RCS Business Messaging (RBM) is now officially named
**RCS for Business**.

#### Ensuring a smooth transition

This is a change in name, not in function. It brings no technical changes to
the platform and no material changes to our terms, policies, or your existing
contracts.

Here's a summary of where you'll see the new platform name:

| **Where the name is changing** ✅ | **Where the name is NOT changing** ❌ |
|---|---|
| **Marketing** : New [marketing site](https://rcsforbusiness.google/) and other marketing assets | **Support email** : The address will remain `rbm-support@google.com` |
| **Documentation** : The [developer site](https://developers.google.com/business-communications/rcs-business-messaging) (non-API sections) | **APIs \& endpoints**: No changes to API names or endpoints |
| **Legal**: Terms of Service, Acceptable Use Policy, new and renewed contracts | **Existing contracts**: We won't amend existing contracts to reflect the name change |

#### What do you need to do?

1. **No immediate action is required**. This is a flexible, gradual transition.
2. **Do not change your code**. Since the API names and endpoints are not changing, no technical work is needed on your end. Your integrations won't be affected.
3. **Use the new name in new materials**. We recommend using "RCS for Business" for any new marketing materials or contracts you create.
4. **Look out for a branding kit**. We will provide a new logo and brand usage guidelines later in Q4 to support your transition.
5. **A note on acronyms**: Use "RCS for Business" externally. While "RBM" remains a familiar shorthand, please avoid creating new acronyms (for example, R4B, RCSB).

## September 15, 2025

### Coming soon

**Restriction on supported schemes for `OpenUrlAction`**

To enhance platform reliability and create a more consistent user experience,
we're standardizing the URI schemes supported by the [OpenUrlAction](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#openurlaction)
suggestion. Effective **November 1, 2025** , only URLs using `http:/`/ or
`https:/`/ schemes will be permitted.

**What's changing?**

Currently, the `url` field in an [OpenUrlAction](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#openurlaction)
accepts a wide range of URI schemes. After November 1, any API request
containing an `OpenUrlAction` with an unsupported scheme
(e.g.,`tel:`,`mailto:`, `geo:`) will be rejected and return a
`400 Bad Request` error.

**Supported schemes**

- `http://`
- `https://`

**Action required**

Review your existing integrations and update any implementations of
[OpenUrlAction](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#openurlaction)
to ensure they exclusively use the supported schemes. All necessary changes must
be completed by November 1, 2025 to avoid service disruptions.

If you have any questions, please contact [RCS for Business Support](https://developers.google.com/business-communications/rcs-business-messaging/support/overview#get-support).

## September 9, 2025

### New

We've launched a more powerful way to
[manage your test devices](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/test)
in the RBM Management API.

With the new
[`testers`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers)
API, you can:

- Send and resend tester invites to devices.
- View invite status: `PENDING`, `ACCEPTED`, and `DECLINED`.
- Get a list of all test devices and their status.
- Remove test devices.

Access to the old
[`phones.testers`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.testers/create)
API will be removed on January 31, 2026. We encourage partners to migrate to the
new
[`testers`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers)
API now.

## August 28, 2025

### Documentation enhancement

**Localized Unsubscribe/Subscribe keywords** : We've updated our documentation
with the specific, country-based keywords (such as STOP, BAJA, parar) that are
automatically sent to your agent when a user unsubscribes or subscribes. This
list will help you better identify and handle these events. For the complete
reference, see the
[Unsubscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe)
and [Subscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#resubscribe)
documentation.

## August 25, 2025

### Documentation enhancement

We've updated the [Verify and launch your agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch)
documentation. To help you find relevant information more quickly:

- We've created individual pages for [Brand verification](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification) and [Launch approval](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval).
- We've grouped the agent creation and launch documentation together in the left-side navigation.

## August 19, 2025

### Changed

- For Google-managed launches: In your [agent information](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information#edit_your_agents_information), you must add at least one contact method: a phone number, website, or email. While only one is required, providing all is encouraged.

## August 13, 2025

### Documentation enhancement

- We've updated the [Rich cards](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards) documentation with a new [Thumbnail](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards#thumbnail) section to clarify the behavior and size limits of thumbnails in rich cards.

## August 4, 2025

### New

- For RBM traffic on India carriers: RBM agents can now send PDF files in [rich cards](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards) in the Google Messages client.

### Documentation enhancement

We've updated the [RBM Billing FAQ](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq)
to explain how different messaging scenarios and user responses contribute to
[billing events](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq#billing-events)
for conversational and non-conversational agents.

The following sections have been added:

- [What billing events are generated if the agent sends several messages before a user replies?](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq#events-generated-after-agent-sends-several-messages-before-user-replies)
- [Which user responses contribute to billing events?](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq#which-user-responses-contribute-to-billing-events)

## July 31, 2025

### Changed

[100 MiB combined file attachment limit per message](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#message_size_limits)

- To improve the user experience and prevent unexpected data consumption, a 100 MiB size limit has been implemented for the total combined size of all media and PDF attachments within a single RBM message. The limit now applies to RBM traffic on all carriers.

## July 30, 2025

### New

**Fix for truncation issues: New full-screen view for rich card carousels in
Google Messages**

This fix addresses a key pain point where text or suggestions on a rich card
carousel could be cut off due to height limitations. To make it clear when more
content is available, a **More** button now appears on truncated carousel cards.
A tap anywhere in the text area expands the card into a swipeable, full-screen
view, so users can always see the complete message.
Your browser does not support the video tag.

**Why we're making this change**

- **Improved user experience:** Eliminates user confusion from truncated content.
- **Enhanced message reliability:** Gives you greater confidence that your entire message---including critical details and calls-to-action---is delivered and viewable.
- **No developer action required:** This feature is enabled automatically for all rich card carousels without any changes to your agent.

**Availability**

- The full-screen view is currently in [**Google Messages Open Beta**](https://support.google.com/messages/thread/9499609/join-the-messages-open-beta-program_), with global availability expected by the **end of Q3 2025.**

For complete technical details on specifications, user interactions, and
suggestion behavior, refer to the updated
[Rich cards documentation](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards#full-screen-carousels).

## July 28, 2025

### New

- The data on the [Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview), including agent reputation and traffic limits (if applicable) is now available through the [Management API](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/analytics.agentPerformances/list).

## July 17, 2025

### Documentation enhancement

We've made several improvements to the
[Manage agents](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents)
documentation.

- New sections have been added to clarify the process for launching and unlaunching an agent:
  - [Launch an agent to one or more regions](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents#launch-agent-to-one-or-more-regions)
  - [Unlaunch an agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents#unlaunch-an-agent)
- The following documentation has been revised to provide greater detail:
  - [Look up an agent's launch status](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents#unlaunch-an-agent)

## July 9, 2025

### New

**Flexible launch option for multi-use agents**

> [!NOTE]
> **Note:** Multi-use agents are not available in India. See the applicable [Use cases and business rules](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#businessrules) for more details.

- To help you get to market faster, you can now request to launch a [multi-use agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#multiuse) with only one of its use cases implemented (either promotional or transactional).
- You are then required to implement and submit the second use case for review within six months of the initial launch to maintain your agent's multi-use status.
- For details, see [Submit a launch request](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval#submit-launch-request).

## July 1, 2025

### Changed

**Reports**

- RBM [billing report and activity log](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports) retention has increased to **63 days**.

## June 23, 2025

### New

**Real-time agent launch state notifications**

- For RBM partners: The RBM platform now sends real-time updates on your agents' launch status directly to your webhook. This eliminates the need for manual monitoring through email or the Developer Console, giving you immediate insights into your agent's lifecycle.

**How it works**

- You'll now receive an `AgentLaunchEvent` for every change to your agent's
  launch status (e.g., from `PENDING` to `LAUNCHED` or `REJECTED`). You can
  use your existing messaging webhook or configure a dedicated notification
  webhook to receive these events.

- To learn more about how to configure your webhook, understand the event
  payload, and interpret agent launch states, see
  [Agent launch state has changed](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#agent_launch_state_has_changed).

## June 16, 2025

### Changed

As we continue to optimize the user experience, we've updated the availability
of the Unsubscribe feature in two markets:

**United States:**

- For RBM and A2P xMS messages from short codes and alphanumeric senders:
  - The Unsubscribe option is no longer visible at the bottom of the chat.
  - The Unsubscribe option in the menu remains available.
- **Developer note:** You will continue to receive Unsubscribe events from users who select the Unsubscribe option at the bottom of the chat in Google Messages versions prior to 20250518.01.

**Spain:**

- The Unsubscribe option (both in chat and menu) was disabled for RBM.

**These updates change how users see the Unsubscribe option. Continue to process
all Unsubscribe events you receive for compliance.**

For more information about the Unsubscribe and Subscribe features, see the
[previous release note](https://developers.google.com/business-communications/rcs-business-messaging/whats-new/past-releases#april_28_2025)
and the [complete documentation](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe).

## June 9, 2025

### Coming soon

**Changes to media URL redirection handling**

For reliable and secure media delivery, we're changing how we handle media URL
redirects in RBM API calls:

- [files.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/files/create) API: Media URLs for file uploads will support **one redirect.**
- [agentMessage.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create) API: Media URLs in these requests will no longer support redirects.

**Timing:** The new redirect handling will take effect on July 30, 2025.

**Recommendation:** To maintain reliable media delivery and avoid disruptions:

- Create and reuse file IDs from the [files.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/files/create) API (file/{uid}).
- Use [uploadedRbmFile](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#UploadedRbmFile) with the file ID in your [Media](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#media) objects.
- Avoid using media URLs directly in [contentInfo](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#ContentInfo) for [phones.agentMessages.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create) requests.

## June 6, 2025

### New

### RBM Figma Sticker Sheet

Exclusively for registered RBM partners: Get accurate Google Messages UI
elements and design patterns with the new
[Figma Sticker Sheet](https://developers.google.com/business-communications/rcs-business-messaging/partner-marketing-toolkit#design-resources).
It's an essential resource for designers to visualize RBM features and create
consistent and intuitive user experiences for your brand.

> [!TIP]
> **Tip:** To view and copy the Sticker Sheet, you need access to your organization's RBM partner account. Please contact a team member with access to share the sheet with you.

To apply to become an RBM partner, fill out the
[partner registration interest form](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/register-partner#submit-partner-registration-interest-form).

## June 4, 2025

### Documentation enhancement

We've made several improvements to the
[Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview)
documentation.

- The following sections have been revised to enhance clarity and provide greater detail:
  - [Reputation score](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview#reputation-score)
  - [Traffic limit](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview#traffic-limit)

## May 30, 2025

### Documentation enhancement

We've updated the RBM agent launch documentation.

- The following sections have been revised to provide greater detail:
  - [Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification#submit-verification-information)
  - [Submit a launch request](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval#submit-launch-request)

## May 28, 2025

### Documentation enhancement

We've made several improvements to the Agents documentation and RBM
Troubleshooting guide.

- New section has been added to the Agents documentation to clarify the process for updating agent details for launched agents:
  - [Edit your agent's details for launched agents](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information#edit_your_agents_details_for_launched_agents)
- New sections have been added to the RBM Troubleshooting guide to address common requests related to agent and RBM partner management:
  - [Request changes to an RBM partner account](https://developers.google.com/business-communications/rcs-business-messaging/support/overview/troubleshooting#request_changes_to_an_rbm_partner_account)
  - [Request to migrate an agent from RBM partner A to partner B](https://developers.google.com/business-communications/rcs-business-messaging/support/overview/troubleshooting#request_to_migrate_an_agent_from_rbm_partner_a_to_partner_b)
- The following documentation has been revised to enhance clarity and provide greater detail:
  - [RBM Troubleshooting guide \> Request to update agent details](https://developers.google.com/business-communications/rcs-business-messaging/support/overview/troubleshooting#request_to_update_agent_details)

## May 12, 2025

### Changed

**Updated rich card carousel dimensions and font size**

The
[specifications for rich card carousels](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards#carousel-specs)
have been updated to reflect the latest Google Messages UI and specific UX
improvements for carousels. All
[rich cards](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards)
also have a slightly larger font for readability.

**Key changes**

- **Font size:** Text within all rich cards (standalone and carousel) now renders at 16 SP, increased from 14 SP.
- **Small carousel dimensions:** Fixed width of 180 DP (increased from 120 DP), maximum height of 542 DP (remains the same).
- **Medium carousel dimensions:** Fixed width of 296 DP (increased from 232 DP), maximum height of 592 DP (remains the same).
- **Carousel scaling:** Carousels have been scaled up by approximately 1.5x to provide more content space.
- **Media heights (unchanged):**
  - Short media: 112 DP
  - Medium media: 168 DP
  - Tall media: 264 DP
- **Media ratio change:** With the increased width of small and medium carousel cards, and no change to their media heights, the media will now appear wider than before.

**Impact on your designs and visualization**

- **Rich cards:** Expect slightly larger text, and adjust your layouts as needed.
- **Small carousels:** Use the expanded fixed width (180 DP) and maximum height (542 DP). Be aware that media will look wider now because the card is wider but the media height hasn't changed. You might need to adjust your image sizing or layout.
- **Medium carousels:** Use the expanded fixed width (296 DP) and maximum height (592 DP). Note that media in these cards will also appear wider due to the card size change. Review your media to confirm it looks good in this wider format.
- **Carousel height:** All cards within a carousel will continue to scale to the height of the tallest card.
- **Carousel truncation:** The [existing logic for truncation](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards#limits) remains in effect.

**Benefits**

- Larger font improves text readability across all rich cards.
- More space in carousels give you more flexibility for displaying multiple items for users to explore.
- This update significantly improves the UX for rich cards and carousels in Google Messages, so you can incorporate more engaging and effective carousels across your campaigns.

**Before and after**

- Small carousel, short media, short text content:

| Feature | Previous dimensions | Current dimensions |
|---|---|---|
| Carousel width | 120 DP (fixed) | 180 DP (fixed) |
| Max height | 592 DP | 542 DP |
| Font size | 14 SP | 16 SP |
| Visualization | Compact, text potentially very small | Wider, more readable text |
| Example | ![Previous content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/small_previous.png) | ![Current content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/small_current.png) |

- Medium carousel, medium media, medium text content:

| Feature | Previous dimensions | Current dimensions |
|---|---|---|
| Carousel width | 232 DP | 296 DP (fixed) |
| Max height | 592 DP | 542 DP |
| Font size | 14 SP | 16 SP |
| Visualization | Moderate space, readable text | More spacious, more readable text |
| Example | ![Previous content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/medium_previous.png) | ![Current content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/medium_current.png) |

- Medium carousel, tall media, long text content:

| Feature | Previous dimensions | Current dimensions |
|---|---|---|
| Carousel width | 232 DP | 296 DP (fixed) |
| Max height | 592 DP | 542 DP |
| Font size | 14 SP | 16 SP |
| Visualization | Text potentially truncated, tighter layout | More room for text, improved visual balance |
| Example | ![Previous content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/tall_previous.png) | ![Current content](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/tall_current.png) |

## April 29, 2025

### New

**Webviews are now generally available in Google Messages**

- Webview functionality has exited Early Access. Now, production agents can use the [Open URL](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#url) suggested action to embed [webviews](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#webview) directly in RBM conversations. This enables users to easily access web content, like payment platforms, without leaving the Messages app. Webviews can display in full, half, or tall screen. Learn more in [What can agents do?](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-can-rbm-do#webviews).
- Note that a client update is required to enable webviews, so this feature will become more widespread over time. On devices that don't support webviews (yet), the specified web page will open in the user's default browser.

## April 28, 2025

### New

- Open beta release of the
  [unsubscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe)
  and [resubscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#resubscribe)
  feature for RBM conversations within Google Messages.

  > [!WARNING]
  > **Beta:** We're gradually rolling out this feature in Google Messages, so users may not have access to it right away. To get access before the full rollout, you can [join the Messages Open Beta program](https://support.google.com/messages/thread/9499609).

  > [!IMPORTANT]
  > **Important:** To help developers transition to the new `UNSUBSCRIBE` and `SUBSCRIBE` webhook events, Google Messages is also sending "STOP" and "START" messages alongside the webhook events. While you can rely on your existing STOP/START logic for now, we strongly recommend updating your logic to handle the `UNSUBSCRIBE` and `SUBSCRIBE` events, as these will become mandatory in compliance with the GSMA spec.

**Key features**

- **Unsubscribe/Subscribe options (replace Block \& report at the bottom
  of the chat)**: Users can easily opt-out or opt-in to conversations.
- **Webhook event notifications** : Partners receive `UNSUBSCRIBE` and `SUBSCRIBE` requests via new webhook events.
- [**Unsubscribe reasons**](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe_reasons): Users can provide a reason when unsubscribing, and have the option to report spam. The existing **Block \& report spam** option remains available in the chat menu.

**Benefits**

- **Actionable insights**: Partners and carriers gain insights into user engagement with business messages.
- **Enhanced user experience**: Users have greater control over the messages they receive, reducing unwanted messages and improving overall satisfaction with RCS.
- **Brand integrity**: Helps businesses maintain a positive brand image by respecting user preferences and promoting ethical messaging practices.

**Availability**

- The **Unsubscribe** and **Subscribe** options will be available for:
  - RBM messages in the United States, Brazil, France, Germany, India, Mexico, Spain, and the United Kingdom.
  - A2P SMS or MMS messages in the United States from short codes (phone numbers with 5-6 digits) and alphanumeric senders.

## April 15, 2025

### New

- To help simplify the agent launch process, now you can [request agent launch from the Developer Console](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval) or [Management API](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/AgentLaunch#questionnaire) without needing to provide an opt-in description.
- Note that solution providers are still responsible for securing user opt-in before sending RBM messages, as noted in the [Terms of Service](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/tos) and [Acceptable Use Policy](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/aup).

## March 25, 2025

### New

- [Business Communications Developer Console](https://business-communications.cloud.google.com/console/partner-console) now includes an [Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview) tab. This tab allows for more effective monitoring of agent spam metrics, enabling you to identify opportunities for spam reduction.

### Coming soon

- Open beta release of the
  [unsubscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe)
  and [resubscribe](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#resubscribe)
  feature for RBM conversations within Google Messages.

  > [!WARNING]
  > **Beta:** We're gradually rolling out this feature in Google Messages, so users may not have access to it right away. To get access before the full rollout, you can [join the Messages Open Beta program](https://support.google.com/messages/thread/9499609).

  > [!IMPORTANT]
  > **Important:** While the user interface for unsubscribe/subscribe is rolling out in the Google Messages Open Beta, the webhook events for `UNSUBSCRIBE` and `SUBSCRIBE` are not yet available. We are sharing the documentation now so partners can understand how the feature will function and prepare for its full release in a future update.

**Key features**

- **Unsubscribe/Subscribe options (replace Block \& report at the bottom
  of the chat)**: Users can easily opt-out or opt-in to conversations.
- **Webhook event notifications** : Partners receive `UNSUBSCRIBE` and `SUBSCRIBE` requests via new webhook events.
- [**Unsubscribe reasons**](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events#unsubscribe_reasons): Users can provide a reason when unsubscribing, and have the option to report spam. The existing **Block \& report spam** option remains available in the chat menu.

**Benefits**

- **Actionable insights**: Partners and carriers gain insights into user engagement with business messages.
- **Enhanced user experience**: Users have greater control over the messages they receive, reducing unwanted messages and improving overall satisfaction with RCS.
- **Brand integrity**: Helps businesses maintain a positive brand image by respecting user preferences and promoting ethical messaging practices.

**Availability**

- The **Unsubscribe** and **Subscribe** options will be available for:
  - RBM messages in the United States, Brazil, France, Germany, India, Mexico, Spain, and the United Kingdom.
  - A2P SMS or MMS messages in the United States from short codes (phone numbers with 5-6 digits) and alphanumeric senders.

## March 4, 2025

### Changed

- If a user whose device doesn't support [webviews](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#webview) opens a link to a web page in the messaging app, the web page now opens in the user's browser instead.

## March 4, 2025

### New

- To align with the GSMA RCC.07 specification, [a new `messageTrafficType` field has been added to the RBM API](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#traffic-type). This field lets you specify the use case, or "traffic type," of each message (for example: authentication, transaction, and promotion types of traffic). By identifying the traffic type of each message, this field will make it possible for one agent to support multiple use cases.

**What do you need to do?**

- To set the message traffic type, use the [`messageTrafficType`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#messagetraffictype) field in the RBM API when sending messages.
- The field is currently **optional**, but we strongly recommend that you start using it now, to avoid future errors when the field becomes required.

> [!NOTE]
> **Note** : This feature does not impact existing [agent use cases or business rules](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#businessrules) at this time.

## February 24, 2025

### Changed

[100 MiB combined file attachment limit per message to US numbers](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#message_size_limits)

- To improve the user experience and prevent unexpected data consumption, a 100 MiB size limit has been implemented for the total combined size of all media and PDF attachments within a single RBM message sent to US phone numbers. This limit applies exclusively to RBM traffic on US carriers.
- Agents operating in multiple countries, such as Canada and the US, are only subject to this limit when sending messages to US phone numbers.

## February 11, 2025

### Changed

For improved error handling, the RBM platform has updated its error responses
for failed [phones.getCapabilities](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones/getCapabilities)
and [phones.agentMessages.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create)
requests. Specifically, the platform now returns a **404 Not Found** error code
in all scenarios where the target user or network is not reachable or configured
for RCS.

**New 404 error behavior:**

- The RBM platform will now return a 404 NOT_FOUND error code in the following situations:
  - A capability check or a message is sent to a user whose device doesn't support RCS or doesn't have RCS enabled.
  - A capability check or a message is sent to a user on a network where the agent is not launched or where RCS traffic is not enabled.

**Change from 403 error:**

- Previously, a 403 PERMISSION_DENIED error was returned when sending capability checks or messages to RCS users on networks where the agent was not launched or RCS traffic was not enabled.

**Impact on developers:** Developers should update their error handling logic to
correctly interpret 404 errors in response to
[phones.getCapabilities](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones/getCapabilities)
and [phones.agentMessages.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create).

## February 4, 2025

### Documentation enhancement

- A new [Rich card](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards)
  guide provides specifications for rich cards and carousels. Understanding
  these specs is essential for creating engaging and functional rich cards in
  Google Messages. Key updates include:

  - Clarified media support (image and video formats, sizing, and aspect
    ratios).

  - Detailed character limits for titles, descriptions, and suggested
    replies and actions.

  - Explanation of vertical and horizontal rich card layouts.

  - Specifications for carousels, including sizing and content limits.

  - Guidance on handling content truncation and whitespace.

## January 29, 2025

### Documentation enhancement

We've made several improvements to the RBM billing documentation.

- A new [RBM billing FAQ](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq) page has been added to address common questions about RBM billing.
- The following documents have been revised to enhance clarity and provide greater detail:
  - [Billing event reports and activity logs](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports)
  - [Create an agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents)

## December 23, 2024

### New

- RBM supports SMS deep links, allowing users to [start a conversation with your agent from a URL](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/deeplinks). By embedding the URL as a link, button, or QR code in emails, websites, apps, or even physical locations, you can provide users with a frictionless way to connect with your agent.

## December 19, 2024

### Changed

- RBM now supports two formats for phone numbers in the chatbot information: either the full E.164 format (for example, "+12223334444") or an unformatted local/toll-free phone number without '+', prefix, or country code (for example, "6502530000"). Emergency numbers are not allowed.

## December 18, 2024

### Changed

- The [bulk capability check](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/capabilities#send_a_bulk_capability_check) now requires between 500 and 10,000 *unique* phone numbers per request. Requests with fewer than 500, more than 10,000, or duplicate numbers will now return an error. For lists exceeding 10,000 numbers, split your requests into batches of 10,000 or fewer.

## November 1, 2024

### Changed

- We have fully transitioned to the partner-based RBM model. The legacy RBM model has been deprecated, and the associated documentation has been removed. The partner-based model enables the following:
  - Creation of a [partner account](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account) to centralize management of all the partner's agents
  - Ability for [multiple users](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account#manage_users) to access partner and agent data through the Developer Console (with full edit access or read-only access)
  - Use of a [partner-level service account](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account#set_up_service_account_to_authenticate_api_calls) so that all the agents share the same credentials to access the RBM API
  - Ability to [configure webhooks](https://developers.google.com/business-communications/rcs-business-messaging/guides/integrate/webhooks#partner_webhooks_and_agent_webhooks) at the partner level or agent level
  - Full use of the [RBM Management API](https://developers.google.com/business-communications/rcs-business-messaging/early-access/rbm-mgmt-api)

## October 31, 2024

### Changed

- The URLs provided in the [Open URL](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#url) suggested action will be rejected if they don't conform to the URI syntax as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986).

## October 21, 2024

### New

- The [Open URL](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#url) suggested action now supports [webviews](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#webview), allowing users to open a specified web page (such as a payment platform) right in the messaging app.
- Webviews can display in full-, half-, or tall-screen mode. For more information, see [What can agents do?](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-can-rbm-do#webviews).

> [!IMPORTANT]
> **Important:** Webviews are available in RBM. However, we're gradually rolling out webview support for RBM in Google Messages. To use webviews in Google Messages *now*, you need to join the Early Access Program for testing. (The feature will become available in Google Messages for production agents at a later date.) To request Early Access for testing webviews in Google Messages, reach out to your RBM contact.

### New

> [!WARNING]
> This feature is deprecated!

- A new suggested action to compose messages opens the user's messaging app to send a text, audio, or video message to a predefined phone number, such as Customer Support.

> [!WARNING]
> **Beta:** We're gradually rolling out the Compose action in Google Messages, so you may not have access to it right away. To get access before the full rollout, you can [join the Messages Open Beta program](https://support.google.com/messages/thread/9499609).

## August 30, 2024

### New

RBM agents can now [send audio files](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#media)
for more accessible and engaging interactions:

- **Improve accessibility:** Enable communication for users with visual impairments, literacy challenges, or motor skill limitations.
- **Enhance customer service:** Help users troubleshoot technical issues by offering audio guides, or live advice, with step by step instructions.
- **Support multilingual customers:** Enable communication in customers' preferred languages---especially valuable for travel or hospitality services.
- **Express your brand's personality:** Add an element of fun with character voices and sound effects, great for the media and entertainment industries.

See
[Supported media types](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#supported_media_types)
for details on compatible audio formats.

## August 1, 2024

### New

We've clarified the brand verification and agent launch process (the process
itself has not fundamentally changed):

- **More intuitive Developer Console experience** : New instructions in the **Verification** tab clarify that [verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification#submit-verification-information) is required before you can submit the agent for its first launch. To prevent confusion, the **Launch** tab is now disabled until verification information is provided.
- **To make sure verification is always performed with the most accurate
  data** :
  - You can no longer cancel verification for RBM agents ([brands.agents.updateVerification](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/updateVerification)).
  - You can no longer edit verification information after you submit a launch request, unless the launch is rejected ([brands.agents.updateVerification](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/updateVerification)).
  - You can't [modify agent information](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information) if the agent is pending verification or was successfully launched ([brands.agents.patch](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/patch)).
- **To explain how brand verification works** : A new [brand verification
  FAQ](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification) covers frequently asked questions.

### New

- You can no longer edit your **Partner name** or **Display name** in the
  [partner account settings](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account#update_partner_account_information).
  To request a change to these names, contact
  rbm-support@google.com.

  > [!IMPORTANT]
  > **Important:** Your **Display name** is used as the `owner_name` in [RBM billing reports](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports#format), which carriers use for validation. If you change your **Display name**, please inform your carriers to avoid billing issues.

## April 1, 2024

### New

- Now you can view an agent's launch history in the RBM consoles. Historical data is available from March 7, 2024 onwards.
  - Partners can [use the Developer Console](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval#view-agent-launch-history) to track changes to an agent's launch status across all relevant carriers.
  - Carriers can [use the Administration Console](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage#view_an_agents_launch_history) to track changes to an agent's launch status on their network.
- To view the most recent change in launch status, see the agent Overview. For a historical record of launch status updates, see Agent history. Details include what the change was, who made it, when, and (in the case of suspension or rejection) why.

## March 26, 2024

### New

- Now all partners using the partner-based RBM model have access to the [RBM Management API](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/overview). This API replicates the capabilities of the Developer Console, so partners can programmatically do the following by API:
  - Create brands and agents
  - List all agents created for a brand
  - Retrieve and edit agent information
  - Submit agents for brand verification and retrieve the verification status
  - Submit agents for launch on selected carriers and retrieve the launch status
  - Add and remove agent webhook integrations

### New

- Carriers (and partners working on behalf of carriers) now have access to the [RBM Operations API](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/overview) for managing RBM agent approvals on their networks. This API replicates the capabilities of the Administration Console, so mobile network operators can programmatically do the following by API:
  - Get a list of all RBM agents submitted for launch on their network
  - Review agent information
  - Retrieve agent launch status and questionnaire
  - Launch or reject pending agents
  - Suspend and terminate live agents

## February 27, 2024

### New

- In your [agent information](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information), now you can provide *either* an email contact *or* a phone number. (Only one form of contact is required, though both are encouraged.)

### New

- Now you can use RBM to [send one-time passwords](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#one-time_passwords_for_user_verification) (OTPs) for automatic user verification in apps that are registered with the [SMS Retriever API](https://developers.google.com/identity/sms-retriever/overview).
  - By leveraging the SMS Retriever API, you can streamline user verification without extra development work.
  - Users benefit from a faster, smoother verification process due to improved latency, higher verification success rates, and the convenience of automatic OTP entry.

## December 21, 2023

### New

- Now partners who register with RBM gain access to the partner-based RBM model. The partner-based model enables the following:
  - Creation of a [partner account](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account) to centralize management of all the partner's agents
  - Ability for [multiple users](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account#manage_users) to access partner and agent data through the Developer Console (with full edit access or read-only access)
  - Use of a [partner-level service account](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/partner-account#authenticate_api_calls) so that all the agents share the same credentials to access the RBM API
  - Ability to [configure webhooks](https://developers.google.com/business-communications/rcs-business-messaging/guides/integrate/webhooks#partner_webhooks_and_agent_webhooks) at the partner level or agent level
  - Full use of the [Management API](https://developers.google.com/business-communications/rcs-business-messaging/early-access/rbm-mgmt-api) when it launches (it's currently available in an Early Access Program)

## December 20, 2023

### Changed

- You can no longer delete an RBM agent.

## December 8, 2023

### Changed

- Our [Acceptable Use Policy](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/aup) has been updated.

## November 29, 2023

### New

- Message expiration is critical for time-sensitive messages like OTPs, urgent notifications, reminders, and limited-time offers. Now you can simplify your developer logic and [set a message expiration](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#expire) to help with timely message delivery. By setting the new `expiration` field, you can revoke messages automatically if they're not delivered by a certain time and then reroute them to a fallback channel.

## November 13, 2023

### New

- Now your agent can [send a PDF file](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#media) by uploading the file or specifying a publicly available URL.

## October 16, 2023

### New

- Now you can specify a thumbnail image when you [use the file upload method](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#file_binary_example) to send media in a rich card.

## September 30, 2023

### New

- Google has extended RBM reachability to users with more unstable connectivity. As a result, you may see higher message delivery rates and higher delivery latency to these users. To help with timely message delivery, [set a message expiration](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#expire) or manually [revoke messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/revoke) and send them through an alternate channel.

## July 03, 2023

### Changed

- Updated [Python First Agent sample](https://developers.google.com/static/business-communications/rcs-business-messaging/samples/rbm-python-client-v1.zip) to Python 3, removed unused dependencies and upgraded to latest libraries.

## June 23, 2023

### New

- An overview of [data security information](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies#data-security) about RBM is now available on the Support page.

## May 10, 2023

### New

- RBM's new integration with [Google Wallet](https://developers.google.com/wallet) lets you issue boarding passes through a rich conversation in [Messages by
  Google](https://messages.google.com/). This means that users of Wallet and Messages can complete the check-in process, receive their boarding pass, and add it to their wallet entirely from Google's Messages app.
- A new use case describes how to seamlessly [add a boarding pass to Google Wallet](https://developers.google.com/business-communications/rcs-business-messaging/guides/use-cases/boarding-wallet) from Google's Messages app. The use case includes a sample conversation with technical steps and design tips for a complete check-in flow.

## April 14, 2023

### New

- [Empty carrier report files](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports#file_availability) can now be generated upon request.

## April 13, 2023

### New

- Added C# code snippet for Pub/Sub pull.

### Changed

- [Kitchen Sink C# sample](https://developers.google.com/business-communications/rcs-business-messaging/samples#agents) updated to Visual Studio 2019 and latest library dependencies.

## April 11, 2023

### Changed

- [First C# sample](https://developers.google.com/business-communications/rcs-business-messaging/samples#agents) updated to Visual Studio 2019 and latest library dependencies.

## December 13, 2022

### New

- More information on [sending messages to offline users](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#sending_to_an_offline_user).
- Clarifying when activity events are [generated](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports#generation).
- Pub/Sub event information about delivery, read and typing [notifications](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/receive#handle_incoming_events).
- An explanation of the Basic Message [length](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#basic_message_content_-_conversion_of_sms).
- Added version history to carrier [Terms of Service](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/carriers/tos).

### Changed

- Updated carrier [console links](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage) to match recent console changes.

## November 15, 2022

### Changed

- Our [Terms of Service](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/tos) and [Acceptable Use Policy](https://developers.google.com/business-communications/rcs-business-messaging/terms-and-policies/aup) have been updated.

### New

- The [use case](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases) is now a required field for agent creation that identifies the nature of the RBM conversations and helps businesses comply with [business rules](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#businessrules).

### New

- Block and report is now more visible to users with the new persistent and dismissable user interface affordance.

## November 3, 2022

### New

- [RBM developer registration](https://developers.google.com/business-communications/rcs-business-messaging/guides/get-started/register-partner). Google Accounts used by RBM developers must now be tied to corporate email addresses and not Gmail accounts.

## November 02, 2022

### New

- The [Billing Category](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents#billingCategory) is now a required field for agent creation that identifies whether the agent supports conversations or discrete messages.
- Carrier [Billing event reports](https://developers.google.com/business-communications/rcs-business-messaging/carriers/reports#billing) documentation has been updated to reference the impact of the agent [Billing Category](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents#billingCategory)
- [RBM Admin Console documentation](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage#review) has been updated to reference the agent [Billing Category](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents#billingCategory).

## August 26, 2021

### New

- The `agentId` field identifies the agent a user-generated message or event belongs to. See [Receive
  messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/receive) and [Events](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events).

## May 03, 2021

### New

- Agents can perform bulk capability checks on up to 10,000 phone numbers per API call with [`users.batchGet`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/users/batchGet). See [Capability
  checks](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/capabilities).

### Changed

- The Bulk Capability Check Script ([Sign in to
  download]()) now uses [`users.batchGet`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/users/batchGet). to perform bulk capability checks.

## April 2, 2020

### New

- RBM agents can now set a fallbackUrl for DialAction, ViewLocationAction, CreateCalendarEventAction, and ShareLocationAction for clients that don't support the native application. See the [guide](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#actions) and [reference](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages#suggestedaction).
- All samples and client libraries updated for fallbackUrl support. See [samples](https://developers.google.com/business-communications/rcs-business-messaging/samples).

## December 20, 2019

### New

- RBM agents can now upload media file binaries in addition to uploading files by URL. See the [guide](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send#media) and [reference](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/files/create).

## December 2, 2019

### New

- The Bulk Capability Check Script ([Sign in to
  download]()) demonstrates how to use the RBM SDK to check a large set of devices for RBM capability. To run this script against devices that aren't registered as testers, your agent must be launched.

### Changed

- [Capability
  checks](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/capabilities#bulk_capability_checks) now covers configuration and usage for the Bulk Capability Check Script.
- [Samples](https://developers.google.com/business-communications/rcs-business-messaging/samples) now includes a Tools section.