In at least one example, as described herein, messages and/or other content can be presented via different presentation characteristics, which can be based on metadata associated therewith. In some examples, a message can be associated with metadata. In some examples, such a message can be called an “event message,” such that the event message can trigger other functionality via the communication platform. In some examples, the metadata can indicate priorities associated with individual messages. In some examples, different priorities can cause messages to be presented with different presentation characteristics, in an effort to enable users to easily consume data presented via the user interface 144. In some examples, priorities can be determined based on hard-coded rules provided by developers, indicators that can be selected by originating users, and/or can be learned using machine learning techniques (e.g., based on interaction data indicative of user interaction with prior messages associated with the communication platform, based on identified trends among similar users, etc.). In some examples, priorities can be determined based at least in part on an originating source (e.g., which user and/or application sent the message), a date of a message, a time of a message, a type of message, content of a message, a topic of a message, and/or the like. In at least one example, such characteristics can be determined based at least in part on metadata associated with messages.