Your HR department has asked you to build an application for their #benefits-us channel.

A global shortcut is designed for exactly this entry-point requirement. Global shortcuts expose application functionality independently of a particular message or channel context, enabling users to launch an application's workflow from broadly accessible locations in Slack. Slack specifically describes global shortcuts as suitable for workflows that can operate without the context of an existing channel or message. After the shortcut is invoked, Slack sends the app an interaction payload containing a trigger_id. The application can acknowledge the invocation and use that trigger_id to open a modal. The modal can then present the required multi-question form. On submission, the application can process the captured fields, transmit the data to the backend system, and use Slack's messaging API to publish the appropriate information to #benefits-us. A message shortcut requires an existing message context, which this use case does not require. A reaction similarly depends on a message. An incoming webhook provides a mechanism for posting information into Slack but does not provide an application entry point for opening an interactive form. This is a direct example of Design the Interactive Flow of Your App, particularly selecting the correct user entry point and connecting shortcuts to modal workflows.