Merge pull request #4320 from braze-inc/BD-1701

BD-1701: Note that Inbound SMS attribution has a one-minute cache

_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md

@@ -1193,7 +1193,11 @@ This event occurs when an SMS experiences delivery failure. Use this event and t
 SMS, InboundReceived
 {% endapitags %}
 
-This event occurs when one of your users sends an SMS to a phone number in one of your Braze SMS subscription groups. Note when Braze receives an Inbound SMS, we attribute that inbound message to any user that shares that phone number. As a result, you may receive multiple events per inbound message if multiple users in your Braze instance share the same phone number. If you require attribution of specific user IDs based on previous messages sent to that user, you can use the SMS Delivered event to attribute Inbound Received events to the user ID who most recently received a message from your Braze number. If we detect that this inbound message is a reply to an outbound campaign or Canvas component sent from Braze, we will also include the campaign or Canvas metadata with the event. Braze defines a reply as an inbound message coming within four hours of an outbound message.
+This event occurs when one of your users sends an SMS to a phone number in one of your Braze SMS subscription groups. 
+
+When Braze receives an inbound SMS, we attribute that inbound message to any user that shares that phone number. As a result, you may receive multiple events per inbound message if multiple users in your Braze instance share the same phone number. If you require attribution of specific user IDs based on previous messages sent to that user, you can use the SMS Delivered event to attribute Inbound Received events to the user ID who most recently received a message from your Braze number.
+
+If we detect that this inbound message is a reply to an outbound campaign or Canvas component sent from Braze, we will also include the campaign or Canvas metadata with the event. Braze defines a reply as an inbound message coming within four hours of an outbound message. However, there is a one-minute cache for the attributed campaign information of the last outbound SMS received.
 
 ```json
 // SMS Inbound Received: users.messages.sms.InboundReceive