Abstract: A user device may receive an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session that is associated with a RCS application. The user device may generate, based on receiving the instruction, a snapshot of the RCS messaging session, and may transmit, based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server. The user device may generate, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session, where the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session. The user device may display, on a display of the device, the shortcut associated with the RCS messaging session.

Abstract: A device may receive a message from a source. The device may send, to a server device, a request for classification information that identifies a classification of the message after receiving the message. The device may receive a response message to the request for the classification information after sending the request. The response message may include the classification information identifying the classification. The device may dynamically provide the message to a channel based on the classification identified by the classification information after receiving the response message.

Abstract: A device may receive a message from a source. The device may send, to a server device, a request for classification information that identifies a classification of the message after receiving the message. The device may receive a response message to the request for the classification information after sending the request. The response message may include the classification information identifying the classification. The device may dynamically provide the message to a channel based on the classification identified by the classification information after receiving the response message.

Abstract: A user device may receive an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session that is associated with a RCS application. The user device may generate, based on receiving the instruction, a snapshot of the RCS messaging session, and may transmit, based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server. The user device may generate, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session, where the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session. The user device may display, on a display of the device, the shortcut associated with the RCS messaging session.

Abstract: A device may receive mapping information that maps an enterprise identifier to a first media identifier, and store the mapping information to allow a set of applications of the device to access the mapping information. The device may obtain updated mapping information based on an update condition being satisfied, and store the updated mapping information. The device may provide, for display via a user interface of an application of the device, a second media identifier in association with a communication.

Abstract: A device may receive, via an interface of the device, information associated with a broadcast enterprise message that is to be provided to a plurality of user devices. The device may provide the broadcast enterprise message to a plurality of user devices. The device may receive, from a user device, a response to the broadcast enterprise message. The device may generate a message thread that includes the broadcast enterprise message and the response. The device may provide, via the interface, information associated with the message thread.

Abstract: A device may receive a message from a third party messaging server device. The message may be destined for one or more user devices. The message may include a parameter that includes information related to the message. The device may determine that the message is an application-to-person (“A2P”) message type based on the message being received from the third party messaging server device. The device may configure a value of the parameter based on determining that the message is the A2P message type. The device may provide the message to a user device, of the one or more user devices, or an inter-carrier server device after configuring the value of the parameter.

Abstract: A device may receive, via an interface of the device, information associated with a broadcast enterprise message that is to be provided to a plurality of user devices. The device may provide the broadcast enterprise message to a plurality of user devices. The device may receive, from a user device, a response to the broadcast enterprise message. The device may generate a message thread that includes the broadcast enterprise message and the response. The device may provide, via the interface, information associated with the message thread.

Abstract: A device may receive a message from a third party messaging server device. The message may be destined for one or more user devices. The message may include a parameter that includes information related to the message. The device may determine that the message is an application-to-person (“A2P”) message type based on the message being received from the third party messaging server device. The device may configure a value of the parameter based on determining that the message is the A2P message type. The device may provide the message to a user device, of the one or more user devices, or an inter-carrier server device after configuring the value of the parameter.

Abstract: A device may receive mapping information that maps an enterprise identifier to a first media identifier, and store the mapping information to allow a set of applications of the device to access the mapping information. The device may obtain updated mapping information based on an update condition being satisfied, and store the updated mapping information. The device may provide, for display via a user interface of an application of the device, a second media identifier in association with a communication.

Abstract: A device may receive an encrypted short message service (SMS) message en route from an originating device to a recipient device, the encrypted SMS message to be encrypted by the originating device using a key. The device may identify a flag associated with the encrypted SMS message. The device may determine, based on the flag, that the SMS message is encrypted. The device may provide the encrypted SMS message to the recipient device.

Abstract: A device may receive an encrypted short message service (SMS) message en route from an originating device to a recipient device, the encrypted SMS message to be encrypted by the originating device using a key. The device may identify a flag associated with the encrypted SMS message. The device may determine, based on the flag, that the SMS message is encrypted. The device may provide the encrypted SMS message to the recipient device.

Abstract: A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.

Abstract: A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.

Abstract: A device is configured to receive triggering information including a set of conditions associated with spam. The device is configured to receive a message from a sending device, and to determine that the message is spam based on determining that the message satisfies a threshold quantity of conditions of the set of conditions. The device is configured to provide a notification indicating that the message may be spam, and receive response information, based on the notification, indicating that the sending device is to be blacklisted. The device is configured to cause, based on the response information, a future message from the sending device to be blocked prior to being presented to a user.

Abstract: A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.

Abstract: A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.

Abstract: A messaging device receives configuration information from a configuration device. The messaging device identifies application configuration information, associated with a first user device, based on the configuration information and sends the application configuration information to the first user device for configuring a messaging application on the first user device. The messaging device receives an incoming message, including message information, from the messaging application on the first user device. The messaging device identifies, based on the message information and the configuration information, a second user device and a message format associated with the second user device. The messaging device sends, in the message format associated with the second user device, an outgoing message, based on the message information and the configuration information, to the second user device.

Abstract: A device may receive, from a user device, a group text message. The device may identify a group of recipients associated with the group text message. The device may determine that the group of recipients includes an emergency services recipient and a non-emergency services recipient. The device may generate an emergency call text message based on the group of recipients including the emergency services recipient and the non-emergency services recipient. The device may send the emergency call text message to the emergency services recipient without sending the emergency call text message to the non-emergency services recipient. The device may send the group text message to the non-emergency services recipient without sending the group text message to the emergency services recipient.

Abstract: A device may obtain receipt data associated with a purchase of an item. The device may generate information for generating a virtual receipt based on the receipt data. The device may determine a user device associated with the receipt data. The device may send a text message, that includes the information for generating the virtual receipt, to the user device. The virtual receipt may be generated by the user device based on the information for generating the virtual receipt.