A command is not recognized

Use this guide when Slack does not autocomplete or respond after you type a Slash Social slash command.

Symptoms

You see one or more of these when you try to run a command:

• Slack shows no autocomplete suggestion for the command you typed.
• Pressing Enter does nothing or Slack says the command is unknown.
• A different app with a similar name appears in autocomplete instead of Slash Social.
• Commands that worked before stopped working after a workspace change or admin update.
• You typed a command you expected from documentation or a teammate, but only /social appears.

You need access to Slash Social in the affected workspace. Admin approval or reinstall may require a workspace owner or support.

Likely causes

• Slash Social is not installed in this workspace.
• You typed a command that is not one of the three public slash commands.
• The app install is stale after a workspace migration, permission change, or outdated manifest.
• You are in a guest workspace, shared channel, or wrong team where Slash Social is not installed.
• Slack suggests a different app with a similar name.
• The workspace admin has not approved or restricted the app install.

Checks

1. Confirm you are in the workspace where the team installed Slash Social, not a guest or shared channel from another workspace.
2. Type /social with no extra text and wait for Slack autocomplete.
3. Try /social-create and /social-approve, the other public commands.
4. Open Apps and search for Slash Social. Confirm it is installed and not pending approval.
5. For tasks beyond the three public commands, type /social and search inside the Command Palette instead of inventing a new slash command.
6. Note whether App Home or modals from /social still open. If nothing responds, the install may be missing or broken.

Fix it

1. Use the public commands: /social, /social-create, and /social-approve.
2. Open tasks from the Command Palette when you need Create, Plan, Workflow, or Settings actions that are not direct slash commands. Type /social and search for the workflow you need.
3. Reinstall the app from https://go.slashsocial.app/slack/install if Slack no longer suggests any of the three commands.
4. Ask a workspace admin to approve the app if Slack shows it as restricted or pending.
5. Retry in the correct workspace if you were testing from a guest account or shared channel tied to another team.

Confirm the fix

Slack autocompletes the command you typed and opens the expected modal, App Home update, or approval view. /social-create opens the create flow and /social-approve opens approval surfaces when you have access.

Run the same test from Slack desktop and mobile if the original report came from one client only, and note which client still fails.

Prevent it next time

• Start from /social, /social-create, or /social-approve instead of guessing command names.
• Use the Command Palette inside /social for Plan, Workflow, and Settings tasks.
• Reinstall after major workspace migrations or when admins change app permissions.
• Bookmark the install URL for your team so admins can refresh the app quickly.

Contact support

Escalate when all three public commands fail in the same workspace after reinstall and the app appears under Apps. Send support the workspace name, exact command text you typed, Slack client (desktop or mobile), any error banner Slack shows, and whether App Home opens from the Apps menu.

Related reading: Start workflows from slash commands, Slack slash commands reference, and Install or reinstall does not complete.