Send a message
AWS End User Messaging uses the same SendTextMessage API operation for both RCS and SMS
delivery. How the service routes your message depends on the origination identity that you specify
in the request. To send rich RCS content such as rich cards, carousels, media files, and
interactive suggestions, use the SendRcsMessage operation instead. You can send
through a phone pool (recommended), directly through an AWS RCS Agent ARN, or at the account
level.
API operations
Use the following API operations to send RCS messages.
| Operation | Description | Use for |
|---|---|---|
|
Sends a message that the service routes to RCS or SMS based on the origination identity. |
Standard text, with SMS fallback. |
|
Sends rich RCS content such as rich cards, carousels, media, and interactive suggestions. |
Rich RCS experiences. |
Types of send
AWS End User Messaging supports three ways to send a message. Each one determines how the service selects an origination identity and whether automatic SMS fallback is available.
| Type | How it works | When to use |
|---|---|---|
Pool-based (recommended) |
Specify a pool ID as the origination identity. The service selects the best identity from the pool and provides automatic SMS fallback. |
All use cases. Managed selection and compliance-safe routing with automatic SMS fallback. |
Direct |
Specify an AWS RCS Agent ARN. The message is sent via RCS only, with no SMS fallback. |
RCS-or-nothing use cases, or when you manage fallback yourself. |
Account-level |
Omit the origination identity. The service selects from the identities in your account. |
Simple single-use-case setups. Not recommended when the account has numbers for multiple use cases. |
For full detail and code examples, see Outbound messaging.
In this section
Outbound messaging
Send RCS messages with the pool-based, direct, and account-level sending patterns, including code examples. |
Inbound messaging
Test and receive inbound (two-way) RCS messages from your customers. |
