This page provides information about the latest changes in RCS for Business.

### November 13, 2026

**Suggested replies and actions in Google Messages notifications**

Google Messages now displays a single suggested reply or action directly
within Android system notifications. This allows users to reply to a message or
trigger an action (such as opening a URL, dialing a number, or creating a
calendar event) in one tap without opening the Messages app.

Because only the first eligible suggestion in a message is shown in the
notification, we recommend placing your most important suggestion first. No
API or server changes are required on your end to enable this behavior.

> [!NOTE]
> **Note:** The **Share location** action isn't supported in notifications and won't be displayed.

## November 4, 2026

### New

**New API field for rich card media alt text**

RCS for Business now supports alt text for rich card media. You can use the new
`contentDescription` field within the `Media` object to describe images and
videos for screen readers, supporting your accessibility efforts.

For more details, see the updated
[Rich cards](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards.md.txt#alt-text)
guide and the
[phones.agentMessages](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages.md.txt#Media)
API reference.

## October 30, 2026

### Changed

**Unsubscribe reasons phrasing**

We've updated the unsubscribe experience in Google Messages to improve clarity
and reduce category ambiguity. This change is rolling out gradually through the
end of November, so the updated interface may take some time to appear for all
users.

| Before | After |
|---|---|
| ![Unsubscribe reasons before](https://developers.google.com/static/business-communications/rcs-business-messaging/whats-new/images/unsubscribe-reasons-before.png) | ![Unsubscribe reasons after](https://developers.google.com/static/business-communications/rcs-business-messaging/whats-new/images/unsubscribe-reasons-after.png) |

**Key features**

- **First-person phrasing** : Unsubscribe reason labels have been updated to use clear, first-person language:
  - **Too many messages**
  - **I never signed up for this** (formerly *Never signed up*)
  - **I'm no longer interested** (formerly *No longer interested*)
  - **This looks like a scam** (formerly *Spam*)
  - **Other**
- **Randomized order** : To reduce selection bias, the first four options are displayed in a randomized order for each user. This order stays consistent across the user's visits, and **Other** remains fixed at the bottom.
- **Analytics reporting** : Unsubscribe feedback continues to be reported in the [Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview.md.txt#unsubscribe-reasons) under the corresponding metric categories.

**Action required**

No action is required on your end.

For more details, see the updated
[Receive events](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events/receive-events.md.txt#unsubscribe_reasons)
guide.

## October 29, 2026

### New

To prevent race conditions where short-lived messages expire before carrier
networks and user devices can process message delivery and return delivery
receipts, the RCS for Business platform is establishing a **minimum six-second
expiration** for all agent messages that specify `ttl` or `expireTime`.

#### What's changing

If a request specifies a `ttl` duration between zero and six seconds, or an
`expireTime` timestamp less than six seconds after message submission, the
platform automatically extends the expiration to six seconds. The `expireTime`
timestamp in the API response reflects this adjusted value.

Requests with a `ttl` of zero or less or an `expireTime` at or before message
submission return a `400 INVALID_ARGUMENT` error.

#### What you need to do

- **Update your expiration values** : If your agent sets `ttl` or `expireTime`, ensure the expiration is at least six seconds after message submission.
- **Align with webhook notifications** : During the automatic adjustment period, a request with a sub-six-second `ttl` (for example, two seconds) will remain active for six seconds.
  - Trigger fallback only when you receive the revocation webhook notification indicating the message has expired.
  - Add a brief buffer after the `ttl` window to allow late-arriving delivery receipts to settle.

For more information, including the recommended practices, see the
[Send messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt#expire)
guide and the
[`phones.agentMessages`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages.md.txt)
reference.

## October 8, 2026

### Documentation enhancement

We've updated the
[Standard billing reports and activity logs](https://developers.google.com/business-communications/rcs-business-messaging/carriers/billing/reports.md.txt)
and
[US billing reports](https://developers.google.com/business-communications/rcs-business-messaging/carriers/billing/us-billing-reports.md.txt)
documentation to clarify that billing reports and activity log files are UTF-8
encoded without a byte order mark, use line feeds for line endings, and include
a header row.

## October 7, 2026

### Changed

**Agent preview video now optional for Google-managed launches**

To help you launch RCS for Business agents faster and make onboarding
seamless, an agent preview video is no longer strictly required for launches on
Google-managed carriers. You can now choose to provide either an agent preview
video or detailed, step-by-step text transcripts in the **Agent experience**
section of the launch questionnaire.

> [!IMPORTANT]
> **Important:** Carrier-managed launch requirements vary by carrier. Check with individual carriers for details.

**What you need to do**

When submitting a launch request for Google-managed carriers, you must clearly
demonstrate your agent's experience. You must provide either an agent preview
video or detailed, step-by-step transcripts for the following fields:

- **Trigger description**: The specific user actions or backend events that trigger messages.
- **Interaction description**: A transcript of the agent's conversation flow, including sample user journeys and suggested replies and actions.
- **Opt-out description** : The supported opt-out keywords (such as `STOP`) and the exact confirmation message sent to users.

For best practices and sample templates by use case (OTP, Transactional,
Promotional, and Multi-use), see
[Describe your agent experience](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/launch-approval.md.txt#describe-agent-experience).

## August 25, 2026

### New

**Partner billing reports**

We are introducing partner billing reports, which provide aggregated daily
counts of billable events, grouped by agent, event type, and carrier. This
high-level summary provides valuable analytics and the necessary visibility to
manage your traffic.

Reports are generated daily in CSV format and delivered securely using the
Google SFTP Service.

To learn how to set up your SFTP credentials and access these reports, see the
[Partner billing reports](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/partner-billing-reports.md.txt)
guide.

## July 31, 2026

### Documentation enhancement

We've updated the [Send messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt#media-compression-and-transcoding)
documentation to clarify the automatic media compression and transcoding
behavior for RCS for Business.

## July 20, 2026

### New

#### New audit trail feature: Capture `acting_party` in the RBM Operations API

To help you maintain accurate audit records, we are introducing an optional
`acting_party` parameter for the
[`brands.agents.updateLaunch`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/updateLaunch.md.txt)
API.

**Why we're making this change**

When an agent launch status is updated using the RBM Operations API, the
**User ID** field in history logs defaults to "API Call" because service
account-based authentication lacks user context.

**Key enhancements**

- **Identifiable API actions** : API callers can now explicitly provide an `acting_party` parameter to represent the email address or identifier of the user executing the action.
- **Console and webhook visibility** : The captured identifier is visible in the **Agent history** of the Administration Console, and is included in `AgentLaunchEvent` webhook notifications.
- **Audit trail consistency**: Logs for API-initiated actions now match those generated by manual console approvals.

**How to use the new parameter**

To begin capturing user identifiers, append the `acting_party` query parameter
to your API requests for `brands.agents.updateLaunch`.

For more details, see the updated
[Change agent launch status](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api.md.txt#change_agent_launch_status)
guide.

## July 13, 2026

### New

**New webhook HTTP header**

The RCS for Business platform now includes an `X-Goog-Webhook-Type` HTTP header
in all webhook requests. This header lets you identify request types for
all incoming webhooks instantly, without needing to parse the JSON body.

For more details, see the updated
[Webhooks](https://developers.google.com/business-communications/rcs-business-messaging/guides/integrate/webhooks.md.txt#identify_request_types)
guide.

## July 6, 2026

### Changed

**Analytics overview unsubscribe metrics**

The [RCS for Business Developer Console](https://business-communications.cloud.google.com/)
now shows unsubscribe metrics for non-promotional agents on the
[Analytics overview](https://developers.google.com/business-communications/rcs-business-messaging/guides/measure/analytics-overview.md.txt),
replacing the 'N/A' placeholder.

## June 26, 2026

### New

**Custom sorting for agent lists**

The `brands.agents.list` endpoint now supports the `orderBy` query parameter.
This allows partners to sort their agents by name, creation time, or last
updated timestamp.

**Key enhancements**

- **Multiple sorting fields:** You can now order your agents using the following fields:
  - `updateTime`: Sorts chronologically by the last update timestamp.
  - `displayName`: Sorts alphabetically by the human-readable agent name.
  - `agentId`: Sorts by the unique system-generated agent identifier.
- **Directional control:** You can set the sorting direction by adding an `" asc"` or `" desc"` suffix to the field name. Fields specified without a suffix will default to ascending order.
- **Default sorting:** If the `orderBy` parameter is omitted, the list defaults to sorting by `agentId` in ascending order.

For more information, see the updated
[brands.agents.list reference documentation](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/list.md.txt).

## June 11, 2026

### Documentation enhancement

We've updated our documentation to clarify that partners can transition an
agent's launch status from `PENDING` to `UNLAUNCHED` to cancel a pending launch
request.

For details, see the
[Receive events](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events/receive-events.md.txt#partner-initiated)
guide.

## May 22, 2026

### Enforcement of regional endpoints for batch capability checks

#### Changed

Starting May 4, 2026, the [`users.batchGet`](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/users/batchGet.md.txt)
method requires the use of regional endpoints. Batch requests must be sent
to the API endpoint that corresponds to the geographical region of the phone
numbers in that batch.

**Why we're making this change**

To optimize API performance and reliability, and to contain the impact of any
potential disruptions.

**What you need to do**

1. Update your application to call the [correct regional endpoint](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/best-practices.md.txt#regional-endpoints) for your `users.batchGet` requests.
2. Ensure each `users.batchGet` request contains phone numbers from a single region only. Requests containing mixed-region phone numbers or sent to the incorrect regional endpoint will fail with a 400 Bad Request error.

**What's not changing**

Single capability checks (`phones.getCapabilities`) and sending messages are not
affected by this enforcement at this time. However, we strongly recommend using
regionalized APIs for all calls to optimize API performance now and to prepare
for future updates.

## May 12, 2026

### New

#### Persistent suggestions for text messages

RCS for Business now supports **persistent suggestions** for standalone text
messages. Unlike standard transient suggestions that disappear when a
conversation continues, persistent suggestions are displayed inside the message
bubble and remain fixed throughout the conversation.

**Why we're making this change**

This feature allows users to revisit useful actions---such as opening a URL,
dialing a number, or viewing a location---long after the initial message was sent,
providing a more consistent and reliable user experience.

"Open a URL" persistent suggestions display the destination URL directly within
the button to build user confidence and reduce "click-hesitation" caused by
unknown links.

> [!WARNING]
> **Warning:** We're currently rolling out the "Open a URL" persistent suggestions feature, so some users may not see the destination URL directly within the button.

**Supported types of messages**

- **Supported**: Standalone text messages.
- **Not supported** : Standalone media messages (image, video, GIF, PDF, or audio). For these use cases, use [rich cards](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards.md.txt).

**Combine suggestions**

You can combine persistent and transient suggestions in a single text
message. Each suggestion must "opt-in" to be persistent.

- **Total limit** : A single text message can support up to **11** total suggestions.
- **Persistent suggestions** : Up to **four** suggestions (displayed inside the bubble).
- **Transient suggestions** : Up to **11** transient suggestions (displayed outside the bubble).

**Supported clients for persistent suggestions**

- **Supported:** Google Messages (version `20260225.00` or later).
- **Not supported:** Google Messages versions earlier than `20260225.00`, iOS, and Samsung Messages.

For more details, see our updated
[Suggestions guide](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt#suggestions).

## April 27, 2026

### Changed

**Updated RBM branding and verification standards in Google Messages**

We are introducing updates to RCS for Business branding and verification to
enhance user trust and align with Google standards. These updates affect
agents' appearance in the Google Messages conversations list, conversation
screen, and conversation details.

**Key enhancements**

- **New logo shape**: The logo is now a rounded square throughout Google
  Messages. The transition to the new rounded square shape is automatic.

  **Note** : If your current logo is a circle on a transparent background,
  it will still be shown as a circle in the Google Messages app. We recommend
  you manually upload a full-background image to ensure it looks best in the new
  UI. For more information, see
  [Edit agent information](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information.md.txt#format-logo).
- **Verification checkmark** : Verified agents now include a verification
  checkmark. The checkmark will appear automatically for agents that have
  completed the [verification process](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt).

| Before | After |
|---|---|
| ![Circular agent's logo](https://developers.google.com/static/business-communications/rcs-business-messaging/images/logo-guidelines/logo_before.png) | ![Rounded square agent's logo](https://developers.google.com/static/business-communications/rcs-business-messaging/images/logo-guidelines/logo_after.png) |

## April 27, 2026

### Documentation enhancement

We've updated the [Webhooks](https://developers.google.com/business-communications/rcs-business-messaging/guides/integrate/webhooks.md.txt)
documentation with new best practices for managing webhooks, specifically
addressing how to handle the risks of shared partner queues and prevent message
delivery failures.

For more information, see the updated
[Webhooks](https://developers.google.com/business-communications/rcs-business-messaging/guides/integrate/webhooks.md.txt#behavior_on_delivery_failure)
guide.

## April 6, 2026

### New

**Upload and delete agent verification documents with the Business
Communications API**

To streamline the agent verification process, we have introduced new methods in
the [Business Communications API](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest.md.txt)
that allow partners to upload and delete supporting documents. This feature is
optional.

**Key enhancements**

- **New API methods** : Partners can now use the following methods to manage verification attachments:
  - [`attachments.create`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/attachments/create.md.txt): Uploads a verification document.
  - [`brands.agents.attachments.delete`](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents.attachments/delete.md.txt): Deletes an attached verification document.
- **Carrier visibility**: For carrier-managed launches, the uploaded documents are shared with each carrier you've selected for launch.

**Technical details and limits**

- **File support:** Initially, the API supports PDF files.
- **Max file size**: 50 MB per file.
- **Quantity limit**: Up to 5 unique documents per agent.

For more information on the verification process, see
[Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information).

## April 1, 2026

### New

**Cross-agent traffic limits for low-reputation promotional agents in India**

We are introducing a cross-agent traffic limit to reduce user inbox fatigue for
subscribers in India. This new limit restricts the total number of promotional
messages a user can receive from all **low reputation agents** per day.

This limit applies across all low reputation agents. **High** and **medium**
**reputation** agents are exempt from this cross-agent restriction.

For a detailed explanation of these new traffic limits and other business rules,
see the [Agent use cases and business rules](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases.md.txt#india)
page.

## April 1, 2026

### New

**New visibility controls: Archive and hide agents**

To help manage console clutter, we've introduced new visibility controls for
both partners and carriers. These features let you remove old or unused agents
from their primary views in the Console and through the API without affecting
agents' operational state.

#### For partners: Archive and unarchive agents

You can archive or unarchive agents that are in an inactive state
(`UNLAUNCHED`, `SUSPENDED`, or `REJECTED`). You can't archive agents that are
`LAUNCHED` or `PENDING` on any carrier network.

**Key features**

- **RCS for Business Developer Console** : Archive or unarchive agents individually or in bulk (up to 100). For details, see [Archive/Unarchive an agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/agents/manage-agents.md.txt#archive-agent).
- **Management API** : Programmatically manage an agent's archive status. For details, see [Archive or unarchive an agent](https://developers.google.com/business-communications/rcs-business-messaging/guides/management-api/agents.md.txt#archive-agent).
- **Filtered views**: By default, archived agents are excluded from the main list. To include the archived agents in their results, use filters in the Console or parameters in the API.

#### For carriers: Hide and unhide agents

You can hide or unhide agents that are in an inactive state (`SUSPENDED` or
`REJECTED`) on your network. You can't hide an agent if its launch status on
your network is `LAUNCHED` or `PENDING`.

**Key features**

- **Administration Console** : Hide and unhide agents individually or in bulk (up to 100). For details, see [Hide/Unhide an agent](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage.md.txt#hide-agent).
- **Operations API** : Manage an agent's hidden status for your network. For details, see [Hide/Unhide agents](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api.md.txt#hide-agent).
- **Filtered views**: By default, agents marked as hidden are excluded from the main list. To view these agents, use filters in the Console or parameters in the API.

## March 10, 2026

### Changed

We have updated the allowed launch state transitions when managing agents
through [RBM Operations API](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api.md.txt)
and
[Business Communications API](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents.md.txt)
and
[Administration Console](https://business-communications.cloud.google.com/console/partner-console/carrier-agents)
and
[RCS for Business Developer Console](https://business-communications.cloud.google.com/).
This ensures consistent logic and synchronization between API and Console.

Here are the updated allowed launch state transitions:

**Carrier-initiated**

- From `PENDING` to `LAUNCHED` or `REJECTED`
- From `LAUNCHED` to `SUSPENDED`
- From `SUSPENDED` to `LAUNCHED` or `UNLAUNCHED`

**Partner-initiated**

- From `UNSPECIFIED`, `UNLAUNCHED`, or `REJECTED` to `PENDING`

> [!NOTE]
> **Note:** If you attempt to change the launch status to a value outside of the allowed ones, the API will return a corresponding error message.

## March 9, 2026

### Changed

**URL transparency in 'Open a URL' suggested action**

Google Messages now displays the underlying URL address directly within the
'Open a URL' action for in-card suggestions of rich cards and carousels.
For details, see
[Open a URL](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt#url).

| Before | After |
|---|---|
| ![Rich card without URL](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/rich-cards/rich_card_before.png) | ![Rich card with URL](https://developers.google.com/static/business-communications/rcs-business-messaging/guides/images/rich-cards/rich_card_after.png) |

By surfacing the URL, we aim to:

- **Build user confidence**: Reduce friction and "click-hesitation" caused by unknown links.
- **Drive engagement**: Establish consistent and reliable usage habits within RCS for Business.

### **Recommended actions**

- **Deployment**: This feature is enabled automatically; no technical integration or API changes are required on your part.
- **Audit your links**: Ensure your destination URLs are concise and consistent with your brand.
- **Review UX**: Check your current 'Open a URL' suggested actions in rich cards and carousels to ensure the display text and the now-visible URL don't feel redundant or cluttered.

## February 28, 2026

### Changed

**API deprecation for the phones.testers resource**

To provide more comprehensive control, we launched the new
[testers](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers.md.txt)
API for complete tester lifecycle management. Now you can send or resend
invites, get status, and remove testers programmatically.

Because of this expanded functionality, we've deprecated the legacy
`phones.testers` resource.

To ensure uninterrupted testing for your agents, all partners are required to
migrate their implementations to the new, streamlined
[testers](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers.md.txt)
API resource. Agents that haven't migrated won't be able to invite or manage
test devices after this date.

| **Resource** | **Status** |
|---|---|
| phones.testers | Deprecated |
| [testers](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers.md.txt) | Current |

#### What you need to do:

1. Review the new [testers API reference](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/testers.md.txt) and the updated guide to [set up a test device](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/test.md.txt).
2. Update your existing code that calls the `phones.testers.create` method to use the new `testers` resource endpoints.
3. Implement and test the new logic.

## February 16, 2026

### New

**New fields in `analytics.agentPerformances.list` response with additional
metrics**

The [analytics.agentPerformances.list](https://developers.google.com/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/analytics.agentPerformances/list.md.txt)
method in the RCS Business Messaging API now includes additional fields in the
AgentPerformance object related to Unsubscribe Reason and Spam Trend data.

## February 12, 2026

### Documentation enhancement

We've updated the [Send messages](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt)
documentation with a new
[Time to live (TTL) for a message](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send.md.txt#ttl)
section to clarify expected notification behavior and provide recommendations
for managing delivery edge cases.

## February 5, 2026

### New

**New Contact RCS for Business support page**

We have replaced the "Email RBM support" link with a new
[Contact RCS for Business support](https://developers.google.com/business-communications/rcs-business-messaging/support/overview/contact.md.txt)
page.

All technical support requests should now be initiated through the
[support contact form](https://developers.google.com/business-communications/rcs-business-messaging/support/overview/contact.md.txt#contact-form)
linked on this page, which ensures that issues are accurately captured and
routed for faster resolution.

To help you prepare your submission, the page includes a quick start guide that
outlines the mandatory information required for various issue categories.

## February 5, 2026

### Documentation enhancement

We've updated the
[Send events](https://developers.google.com/business-communications/rcs-business-messaging/guides/build/events/send-events.md.txt)
and
[phones.agentEvent.create](https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentEvents/create.md.txt)
documentation with information about the delivery behavior of the `READ` and
`IS_TYPING` agent events within RCS for Business.

- The updates specify that `READ` events are persistent and stored for up to 30 days if a user has RCS enabled but is unreachable, while `IS_TYPING` events remain ephemeral and expire after approximately 20 seconds.

## January 30, 2026

### New

**Optional comments for agent launch approvals**

Carriers can now provide additional comments when approving agent launch
requests.

**Console changes**

Previously, when managing agents in the [Administration Console](https://business-communications.cloud.google.com/console/partner-console/carrier-agents),
carriers could provide a comment with a reason only when rejecting, suspending,
or terminating an agent.

With this update, we have introduced an **optional comment field** for the
approval process. This allows carriers to share important context directly with
agent owners at the point of approval. For more information, see
[Manage agents on your network](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage.md.txt#approve).

Comments provided during approval are recorded in **Agent history** of both the
[Administration](https://business-communications.cloud.google.com/console/partner-console/carrier-agents)
and [Business Communications](https://business-communications.cloud.google.com/console)
consoles.

**RBM Operations API changes**

The `comment` field now supports **all** state transitions when
[changing an agent's launch status](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api.md.txt#change_agent_launch_status).
Carriers can now provide an **optional** reason for any status change to improve
communication and record-keeping. For more information, see
[Manage agents with the RBM Operations API](https://developers.google.com/business-communications/rcs-business-messaging/carriers/operations-api/manage-by-api.md.txt#change_agent_launch_status).

## January 15, 2026

### New

Notifications for rich cards and carousels in Google Messages now
include a preview of the media, along with the title and description.

Media previews are only shown when:

- **Rich cards**: The card's media is an image or has a thumbnail.
- **Carousels**: The first card's media is an image or has a thumbnail.

| Collapsed notification | Expanded notification |
|---|---|
| ![Collapsed notification](https://developers.google.com/static/business-communications/rcs-business-messaging/whats-new/images/collapsed.png) | ![Expanded notification](https://developers.google.com/static/business-communications/rcs-business-messaging/whats-new/images/expanded.png) |

**Why we're making this change**

To boost engagement with your messages.

**Action required**

No action is required on your end.

### New

**File sharing for agent verification**

To streamline the agent approval process, partners now have the option to upload
supporting documents directly in the
[RCS for Business Developer Console](https://business-communications.cloud.google.com/).

### Key enhancements

- **Direct upload** : Partners can now upload authorization letters and other supporting documents directly into the [RCS for Business Developer Console](https://business-communications.cloud.google.com/). For more information, see [Submit verification information](https://developers.google.com/business-communications/rcs-business-messaging/guides/launch/brand-verification.md.txt#submit-verification-information). Note that even if an authorization letter is provided, the primary authorization method for launches on Google-managed carriers remains email.
- **Visibility** : Carriers who use the [Administration Console](https://business-communications.cloud.google.com/console/partner-console/carrier-agents) can view these uploaded documents to speed up their review. For more information, see [Manage agents on your network](https://developers.google.com/business-communications/rcs-business-messaging/carriers/console/manage.md.txt).
- **Flexible verification options**: The new feature supplements our standard email-based verification, which remains active.

While this feature is optional, keep the following technical limits in mind:

- **File type**: PDF only.
- **Max file size**: 50 MB per file.
- **Quantity limit**: Up to 5 unique documents. Avoid file duplications.

## January 7, 2026

### New

We are introducing new traffic limits for
[promotional](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases.md.txt#promotional)
RCS for Business agents in India.

#### Limits on total unique users

A new limit affects the total number of unique users an agent can message per 28
days based on its reputation. All new agents start with a **low**
reputation by default.

For a detailed explanation of these new traffic limits and other business rules,
see the [Agent use cases and business rules](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/agent-use-cases.md.txt)
page.