Message thread prioritization interface

A system comprising:

• a memory;
• and
• at least one hardware processor coupled to the memory and comprising instructions that causes the system to perform operations comprising:
• accessing a message repository associated with a user account, the message repository comprising a plurality of message threads that include at least a first message thread associated with a sender and a plurality of participants, each of the sender and the plurality of participants associated with user identifiers, and the first message thread comprising a plurality of messages received from the sender and the plurality of participants;
• generating a graphical user interface (GUI) that comprises an allocable region at a first position in the GUI, and a presentation of the plurality of message threads at a second position within the GUI, the presentation of the plurality of message threads including a display of the first message thread at location within the second position of the GUI;
• receiving an input that drags the display of the first message thread from the second position of the GUI to the allocable region within the first position of the GUI, the allocable region including a second message thread;
• presenting a request to allocate the first message thread to the allocable region responsive to the input that drags the display of the first message thread to the allocable region, the request including an indication that the second message thread is to be de-allocated from the allocable region;
• receiving a selection of the request to allocate the first message thread to the allocable region;
• de-allocating the second message thread from the allocable region responsive to the selection of the request;
• allocating the display of the first message thread associated with the sender to the allocable region at the first position in the GUI based on the input;
• generating a graphical icon based on user profile data associated with the sender and the plurality of participants of the first message thread;
• displaying the graphical icon associated with the display of the first message thread within the allocable region, based on the allocating the display of the first message thread to the allocable region;
• determining that the sender associated with the first message thread requested to allocate the first message thread to the allocable region at a client device associated with the sender;
• and
• presenting a notification that includes the user identifier of the sender within the allocable region in response to the determining that the sender associated with the first message thread requested to allocate the first message thread to the allocable region.

A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising:

• accessing a message repository associated with a user account, the message repository comprising a plurality of message threads that include at least a first message thread associated with a sender and a plurality of participants, each of the sender and the plurality of participants associated with user identifiers, and the first message thread comprising a plurality of messages received from the sender and the plurality of participants;
• generating a graphical user interface (GUI) that comprises an allocable region at a first position in the GUI, and a presentation of the plurality of message threads at a second position within the GUI, the presentation of the plurality of message threads including a display of the first message thread at location within the second position of the GUI;
• receiving an input that drags the display of the first message thread from the second position of the GUI to the allocable region within the first position of the GUI, the allocable region including a second message thread;
• presenting a request to allocate the first message thread to the allocable region responsive to the input that drags the display of the first message thread to the allocable region, the request including an indication that the second message thread is to be de-allocated from the allocable region;
• receiving a selection of the request to allocate the first message thread to the allocable region;
• de-allocating the second message thread from the allocable region responsive to the selection of the request;
• allocating the display of the first message thread associated with the sender to the allocable region at the first position in the GUI based on the input;
• generating a graphical icon based on user profile data associated with the sender and the plurality of participants of the first message thread;
• displaying the graphical icon associated with the display of the first message thread within the allocable region, based on the allocating the display of the first message thread to the allocable region;
• determining that the sender associated with the first message thread requested to allocate the first message thread to the allocable region at a client device associated with the sender;
• and
• presenting a notification that includes the user identifier of the sender within the allocable region in response to the determining that the sender associated with the first message thread requested to allocate the first message thread to the allocable region.