Put social decisions back in the right channel.

Goal

Handle social work where your team already talks in Slack. Channel cards bring approval requests, publishing status, inbox alerts, and report summaries into team channels so approvers, creators, and admins can act without opening App Home first.

When to use this

Use channel cards when:

• Review requests should land in the channel your team uses for sign-off
• Publishing health or account connection issues need a visible next step in channel
• Inbox alerts or listening signals should prompt a reply or triage action in place
• Report summaries should open the linked workflow from the channel message

Skip channel-only work when you prefer the Workflow work center in App Home or when notifications are not routed to that channel yet.

Before you begin

Confirm you have access to the Workflow work center for the brand on the card. Your workspace should route Slash Social notifications to the channels you use for approvals, publishing, or reporting.

You need permission to act on the brand shown on the card. Cards respect brand and role scope, so you only see buttons your role allows.

If your team uses multi-step or external approval paths, those features require a Team plan or higher. You do not need a separate tracker for channel cards to work; they complement App Home, DMs, and Slack Lists.

Steps

Find the card in channel

1. Open the team channel where Slash Social posts approval requests, status updates, inbox alerts, or report summaries.
2. Locate the card message. Read the state, owner, and brand context shown on the card.
3. Decide whether you can act now or need the full review surface for more detail.

Act from the card buttons

Use the buttons on the card when you are ready:

• Pending content: Approve, request changes, or open the full review
• Publishing health: Reconnect an account or follow the next step shown on the card
• Reports or linked work: Open the report or drill into the linked workflow

If the card opens a modal or reply surface, complete the action there. The card may update in place, or a thread reply may confirm the outcome.

Handle inbox-driven cards

Some cards surface inbox or listening context in channel. When the card points to a conversation that needs a response, use the reply action to open the reply modal, draft your response, and send from there. This keeps triage in the same channel thread your team already monitors.

Branch: open full detail instead of a quick action

When the preview is not enough, open the full post or workflow from the card. Finish the decision in the review surface, then return to the channel to confirm the card state moved forward.

Success criteria

You know the flow worked when one or more of these are true:

• The card status updates in the channel
• The item moves to the next workflow state, such as approved, assigned, changes requested, or completed
• Slack confirms the action with an updated message or thread reply
• Approvers who opened the full post see the same state as the card preview

Troubleshooting

Expected cards never arrive

Check notification and routing settings for the brand. Confirm the channel is the one configured for that notification type. Open the same work from App Home in the Workflow work center as a fallback.

Buttons are missing or grayed out

Your role may not include the action for that brand. Ask a brand admin to confirm your approver or creator access. Switch to the correct active brand if your workspace manages more than one.

The card opens a modal but nothing changes

Complete all required fields in the modal before submitting. If the card still shows the old state, refresh App Home and compare the item state there. For approval blockers, see Resolve approval workflow blockers.

You need a command entry point instead

Use /social-approve to open pending approvals when channel cards are unavailable. See Slash commands reference for supported public commands.