Messaging Events

AWS End User Messaging can stream event data for SMS, MMS, and voice message deliveries. Because it can take up to 72 hours to receive events generated by carriers, you should not use them to determine if there is a delay in outbound message delivery. After 72 hours, if AWS End User Messaging has not received a final event from a carrier, the service automatically returns an UNKNOWN messageStatus as we do not know what happened to that message.

SMS example log

The JSON object for an SMS event contains the data shown in the following example.

{
    "eventType": "TEXT_SUCCESSFUL",
    "eventVersion": "1.0",
    "eventTimestamp": 1686975103470,
    "isFinal": true,
    "originationPhoneNumber": "+12065550152",
    "destinationPhoneNumber": "+14255550156",
    "isInternationalSend": false,
    "mcc": "310",
    "mnc": "800",
    "messageId": "862a8790-60c0-4430-9b2b-658bdexample",
    "messageRequestTimestamp": 1686975103170,
    "messageEncoding": "GSM",
    "messageType": "PROMOTIONAL",
    "messageStatus": "SUCCESSFUL",
    "messageStatusDescription": "Message has been accepted by phone carrier",
    "context": {
        "account": "bar"
    },
    "totalMessageParts": 1,
    "totalMessagePrice": 0.09582,
    "totalCarrierFee": 0.0
}

SMS Protect example log

The JSON object for a SMS event when using SMS Protect contains the data shown in the following example.

{
    "eventType": "TEXT_PROTECT_BLOCKED",
    "eventVersion": "1.0",
    "eventTimestamp": 1686975103470,
    "isFinal": true,
    "originationPhoneNumber": "+12065550152",
    "destinationPhoneNumber": "+14255550156",
    "isoCountryCode": "US",
    "mcc": "310",
    "mnc": "800",
    "messageId": "862a8790-60c0-4430-9b2b-658bdexample",
    "messageRequestTimestamp": 1686975103170,
    "messageEncoding": "GSM",
    "messageType": "PROMOTIONAL",
    "messageStatus": "PROTECT_BLOCKED",
    "messageStatusDescription": "Message blocked by protect configuration",
    "context": {
        "account": "bar"
    },
    "totalMessageParts": 1,
    "totalMessagePrice": 0,
    "totalCarrierFee": 0, 
    "protectConfiguration": {  
        "protectConfigurationId": "protect-d777777777777771bbd5d59f4d903479", 
        "protectStatus": "FILTER" 
    }, 
    "protectConfigurationAssessment": { 
        "protectRecommendation": "BLOCK"
         "protectInsights": { 
            "blockReason": "AIT_SUSPECTED" 
         }
         
    }
}

Voice example event log

The JSON object for a Voice event contains the data shown in the following example.

{
    "eventType": "VOICE_COMPLETED",
    "eventVersion": "1.0",
    "eventTimestamp": 1697835373500,
    "isFinal": true,
    "originationPhoneNumber": "+12065550153",
    "destinationPhoneNumber": "+14255550159",
    "isoCountryCode": "US",
    "messageId": "567f6c11-6e8b-4352-9749-a42a0example",
    "messageRequestTimestamp": 1697835372720,
    "messageStatus": "COMPLETED",
    "callDurationInSeconds": 60,
    "totalDurationInMinutes": 1,
    "totalMessagePrice": 0.013,
    "context": {
        "account": "bar"
    }
}

MMS example log

The JSON object for an MMS event contains the data shown in the following example.

{
    "contentType":"MMS",
    "eventType": "MEDIA_DELIVERED",
    "eventVersion": "1.0",
    "eventTimestamp": 1635197695208,
    "isFinal": true,
    "originationPhoneNumber": "+12065550153",
    "destinationPhoneNumber": "+14255550159",
    "isoCountryCode": "US",
    "messageId": "b4a3196d-5b61-4884-a0d9-745acf1f6235example",
    "messageRequestTimestamp": 1635197693241,
    "messageType": "TRANSACTIONAL",
    "messageStatus": "DELIVERED",
    "messageStatusDescription": "Message has been accepted by phone",
    "context": {"foo":"bar"},
    "totalMessageParts": 1,
    "totalMessagePrice": 0.0195,
    "totalCarrierFee": 0.00266
}

RCS example log

RCS events use an eventType of RCS_DELIVERED, RCS_READ, and the related RCS status event types. Every RCS event also carries an rcsBusinessId and an agentIsoCountryCode that identify the RCS agent, which SMS and MMS events do not include. The originationPhoneNumber field contains the RCS agent ID when the message is delivered natively over RCS, and an E.164 phone number or short code when the message falls back to SMS.

Delivery event. A delivered message reports an eventType of RCS_DELIVERED and a messageStatus of DELIVERED. Rich RCS messages include billing metadata, where rcsMetadata.billingEventType is RICH:

{
    "eventType": "RCS_DELIVERED",
    "eventVersion": "1.0",
    "eventTimestamp": 1781661267660,
    "isFinal": true,
    "originationPhoneNumber": "rcs-c020de2520714385964ebf7b095c4b60",
    "destinationPhoneNumber": "+13022640220",
    "isoCountryCode": "US",
    "isInternationalSend": false,
    "messageId": "test-sc1-004",
    "messageRequestTimestamp": 1781300397157,
    "messageEncoding": "UNICODE",
    "messageType": "TRANSACTIONAL",
    "messageStatus": "DELIVERED",
    "messageStatusDescription": "Message has been accepted by phone",
    "totalMessageParts": 1,
    "totalMessagePrice": 0.007,
    "totalCarrierFee": 0.00494,
    "rcsMetadata": { "billingEventType": "RICH" },
    "rcsBusinessId": "endusermessagingtesting1_06fr8x6o_agent",
    "agentIsoCountryCode": "US"
}

Read event. A read receipt reports an eventType of RCS_READ and a messageStatus of READ. A RCS_DELIVERED event is always sent before or together with the RCS_READ event:

{
    "eventType": "RCS_READ",
    "eventVersion": "1.0",
    "eventTimestamp": 1781661267203,
    "isFinal": true,
    "originationPhoneNumber": "rcs-c020de2520714385964ebf7b095c4b60",
    "destinationPhoneNumber": "+13022640220",
    "isoCountryCode": "US",
    "isInternationalSend": false,
    "messageId": "test-sc1-004",
    "messageRequestTimestamp": 1781300397157,
    "messageEncoding": "UNICODE",
    "messageType": "TRANSACTIONAL",
    "messageStatus": "READ",
    "messageStatusDescription": "Message has been read by recipient",
    "totalMessageParts": 1,
    "totalMessagePrice": 0.0,
    "totalCarrierFee": 0.0,
    "rcsBusinessId": "endusermessagingtesting1_06fr8x6o_agent",
    "agentIsoCountryCode": "US"
}

Delivery event within a conversation. When a message is part of an active conversation session, the delivery event adds the conversation fields and reports a totalMessagePrice and totalCarrierFee of 0.0, because the one-time conversationSessionFee covers the message:

{
    "eventType": "RCS_DELIVERED",
    "eventVersion": "1.0",
    "eventTimestamp": 1751234567890,
    "isFinal": true,
    "originationPhoneNumber": "rcs-f4e4252a5abe48bea50a6c176a056124",
    "destinationPhoneNumber": "+14376638816",
    "isoCountryCode": "CA",
    "isInternationalSend": false,
    "messageId": "b4a3196d-5b61-4884-a0d9-745acf1f6235",
    "messageRequestTimestamp": 1751234565000,
    "messageEncoding": "UNICODE",
    "messageType": "TRANSACTIONAL",
    "messageStatus": "DELIVERED",
    "messageStatusDescription": "Message has been accepted by phone",
    "totalMessageParts": 1,
    "totalMessagePrice": 0.0,
    "totalCarrierFee": 0.0,
    "rcsMetadata": { "billingEventType": "BASIC" },
    "rcsBusinessId": "endusermessagingtesting1_06fr8x6o_agent",
    "agentIsoCountryCode": "CA",
    "conversationInitiatingMessageId": "177930985040408106521449",
    "conversationInitiatingMessageType": "OUTBOUND",
    "conversationSessionFee": 0.012
}

CONVERSATION_STARTED event. AWS End User Messaging sends this event to your RCS event Amazon SNS topic when a conversation session begins. The messageBody is a JSON string:

{
    "originationNumber": "14376638816",
    "destinationNumber": "rcs-e138fa39eabf4d6d8e95546248c8dfa7",
    "messageBody": "{\"type\":\"CONVERSATION_STARTED\",\"startTime\":\"2026-06-28T04:03:08.002+0000\",\"endTime\":\"2026-06-29T04:08:08.002+0000\",\"conversationInitiatingMessageId\":\"7e7da6ec-234a-4d4f-bbc5-943bcca663ab\",\"conversationInitiatingMessageType\":\"OUTBOUND\"}",
    "inboundMessageId": "7e7da6ec-234a-4d4f-bbc5-943bcca663ab"
}

Inbound typing indicator. Inbound interaction events are delivered to the two-way Amazon SNS topic on your RCS agent, not to a configuration set event destination. The messageBody is a JSON string with a type of RCS_TYPING:

{
    "originationNumber": "12679164820",
    "destinationNumber": "rcs-cb1e6e519e9049fabf8c0ae38e4d876b",
    "messageBody": "{\"type\":\"RCS_TYPING\",\"receivedAt\":\"2026-06-17T17:36:29.937+0000\"}",
    "inboundMessageId": "12679164820-2026-06-17T17:36:29.937+0000"
}

Suggestion tap (postback). When a recipient taps a suggestion, you receive a postback on the two-way Amazon SNS topic. The messageBody carries the postbackData you configured on the suggestion:

{
    "originationNumber": "12679164820",
    "destinationNumber": "rcs-cb1e6e519e9049fabf8c0ae38e4d876b",
    "messageBody": "{\"type\":\"SUGGESTION\",\"text\":\"Open\",\"postbackData\":\"Open\"}",
    "inboundMessageId": "nIMYZGrBUILWng0Qck0deqVaAoTSJY5PsktKYOBYJhVaTsrdMdrs714e8SLZAjD3"
}

To determine the delivery channel, inspect the originationPhoneNumber field. An RCS agent ID means the message was delivered over RCS; an E.164 phone number or short code means it was delivered over SMS, either directly or after RCS fallback.

RCS event types and fields

The following sections describe each RCS event type, the status values and fields it carries, and how to process it. The example payloads above show these events as they arrive at your event destination.

Common fields on RCS events

All RCS events, including delivery status events, read receipts, and inbound interaction events, include the following fields that identify the RCS agent:

These fields are present on all RCS events. They are not included on SMS or MMS events.

Delivery status events

Delivery status events indicate the lifecycle state of an outbound RCS message. You use these events to confirm delivery, trigger fallback logic, or alert your operations team to content violations.

Each outbound status event has an eventType of RCS_DELIVERED (and related RCS status event types) and a messageStatus field that holds one of the following values:

Read receipts

A read receipt indicates that the recipient opened or viewed your message. Use read receipts to track engagement and measure read rates.

The read event uses an eventType of RCS_READ with messageStatus set to READ.

You can calculate your read rate as the number of READ events divided by the number of DELIVERED events, multiplied by 100.

Typing indicators

Typing indicator events signal that a participant is composing a message. These events flow in both directions:

TTL expiration events

When you set a TimeToLive value on a message and the TTL elapses before the message is delivered, the RCS platform attempts to revoke (delete) the message. The outcome generates one of the following events:

TTL expiration events work together with your fallback strategy. For details on configuring message expiration, see the RCS message expiration documentation.

Fallback events

When an RCS message cannot be delivered and AWS End User Messaging triggers an SMS or MMS fallback (either through pool-based configuration or per-message FallbackConfiguration), the service generates events that indicate the fallback outcome.

Fallback events indicate:

Monitor these events to measure your fallback rate and identify phone numbers that consistently require fallback delivery. For details on configuring per-message fallback, see the RCS per-message fallback documentation.

Suggestion tap (postback) events

When a recipient chooses a suggestion (a suggested reply or suggested action), you receive a postback event containing the PostbackData string that you configured on that suggestion. Use postback data to route your conversational logic, not the display text.

The notification's messageBody contains a JSON object with a type of SUGGESTION, the display text, and the postbackData you set on the suggestion.

For details on how to configure suggestions and their postback data, see the RCS suggestions documentation.

Conversational pricing events and fields

If you register your RCS agent to use conversational pricing, AWS End User Messaging adds fields to delivery and inbound events while a message is part of an active conversation session, and sends a CONVERSATION_STARTED event when a session begins. For an overview of the conversational pricing model, see the RCS conversational pricing documentation.

Conversation fields

The following fields appear on a delivery or inbound event only when the message is part of an active conversation session. When the message is not part of a conversation, AWS End User Messaging omits these fields entirely.

When a message is part of an active conversation session, its delivery event reports a totalMessagePrice and totalCarrierFee of 0.0, because the session fee covers the message.

CONVERSATION_STARTED event

AWS End User Messaging sends a CONVERSATION_STARTED event to your RCS event Amazon SNS topic when a conversation session begins. A session begins when your agent sends a message and the recipient replies within 24 hours (business-initiated), or when the recipient sends a message and your agent responds (user-initiated).

The messageBody contains a JSON object with the following fields:

Best practices for event processing

Registration status change example

Unlike the message events in the preceding sections, which you receive through a configuration set event destination, the registration status change event is published directly to Amazon EventBridge on the default event bus. emits this event whenever the status of a registration, such as a phone number or sender ID registration, changes. Create an EventBridge rule on the default event bus with a source of aws.sms-voice and a detail type of Registration Status Change to route it to a target. The event contains the data shown in the following example.

{
    "version": "0",
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234example",
    "detail-type": "Registration Status Change",
    "source": "aws.sms-voice",
    "account": "123456789012",
    "time": "2024-04-25T00:00:00Z",
    "region": "us-east-1",
    "resources": [
        "arn:aws:sms-voice:us-east-1:123456789012:registration/reg-12345example"
    ],
    "detail": {
        "registrationArn": "arn:aws:sms-voice:us-east-1:123456789012:registration/reg-12345example",
        "registrationDetails": {
            "registrationId": "reg-12345example",
            "registrationVersionNumber": 1,
            "registrationType": "US_TEN_DLC_BRAND",
            "registrationStatusChangeTimestamp": 1714000000000,
            "currentStatus": "COMPLETE"
        }
    }
}