workflow · how to
Submit and review standups
Follow the submit and review standups workflow in Slack.
Goal
Record yesterday, today, and blockers for your brand, respond to standup prompts on schedule, and review past entries when you need context for the week.
When to use this
Use standups when your team runs a daily or weekly rhythm in Slack and you want structured updates tied to the active brand. Submit when Slash Social sends a standup prompt. Review history when you need to compare blockers across days or audit who filed updates for a date range.
Choose Remind me later when you are mid-task and need time before you write meaningful entries. Choose Skip today when no update is needed. Use blocker drill-down actions when the summary mentions accounts or items you need to open directly.
Before you begin
Confirm these requirements:
- Brand context: Select the active brand before you submit or filter history. Standup entries and history are brand-scoped. When multi-brand is enabled for your organization, the history filter modal includes a brand selector.
- Prompt delivery: Standup prompts arrive as Slash Social notifications. You need the app installed and notifications enabled in Slack for your user.
- Non-empty submissions: The submit modal requires meaningful entries in Yesterday, Today, and Blockers. Empty submissions are rejected.
No specific plan gate applies to standups beyond the Engage capabilities your organization already uses for inbox work.
Steps
Open standup history
- Open
/socialand search for standup in the command palette. - Run the standup action to open the history filter modal.
- Choose the date range you want to review.
- When multi-brand is enabled, choose the brand whose history you need.
- Submit the filter modal to view past standup entries for that window.
The history modal validates payload and trigger context before it opens. If the modal does not appear, retry from App Home so Slack provides a fresh trigger.
Submit today’s standup
- When Slash Social sends a standup prompt, choose Submit on the notification.
- Fill Yesterday, Today, and Blockers with meaningful entries. Do not leave fields blank.
- Submit the standup modal.
Slash Social writes the entry for the current standup run and closes the modal on success.
Other standup actions
Use these actions from standup prompts or follow-up messages when they match your situation:
| Action | Use it when |
|---|---|
| Remind me later | You need more time before submitting. |
| Skip today | No standup entry is needed today. |
| View full | You need the complete standup thread for a run. |
| Post update | A summary was posted and you need a thread follow-up. |
| View blockers | You need accounts, items, or unified blocker lists for the same standup run. |
View blockers branches to account lists, item lists, or a unified blocker view depending on which drill-down action you choose from the notification.
Post update opens a follow-up modal when you need to add context after the main summary posted.
Success criteria
You have finished this workflow when:
- Submitted standups appear in history for the selected brand and date window.
- Empty submit attempts are blocked with guidance instead of creating blank entries.
- Remind me later or Skip today completes without leaving a partial entry you did not intend.
- View full opens the complete thread for the standup run you selected.
- Blocker drill-down actions open the expected accounts view, items view, or unified blocker list.
Troubleshooting
Standup action does not open the history modal
Open /social from App Home and search for standup again. The command validates trigger context before modal open. Avoid running the action from surfaces that cannot open modals.
Submit is rejected
Fill Yesterday, Today, and Blockers with non-empty text. Whitespace-only entries count as empty.
History shows no entries for a date range
Widen the date range or confirm you selected the correct brand when multi-brand is enabled. Entries only exist for days someone submitted or skipped with a recorded action.
Blocker drill-down opens the wrong list
Use View blockers from the same standup run as the summary you are reviewing. Account and item views are scoped to that run’s blocker snapshot.
No standup prompt arrived
Confirm Slash Social notifications are enabled for your Slack user and that you have the active brand selected in App Home. Prompt timing is configured outside this article; ask your admin if prompts never arrive for your workspace.
For how Engage fits alongside other App Home areas, read Work centers. For the full list of Slash commands your workspace exposes, see Slack slash commands.