Send client approval packs

Goal

Send client review packs, collect approve or change requests from external stakeholders, and track pack status without exposing unrelated internal production context. You manage clients from a dashboard, add contacts, act on packs and individual items, and resubmit or cancel when the review cycle changes.

When to use this

Use client approval packs when:

• External stakeholders must approve content before publish
• Clients should review a batch of items together instead of one-off DMs
• Your agency needs a client-facing surface that hides internal pipeline noise
• You send reminders, collect structured change requests, or close a pack that is no longer needed

Email and external approval paths require Team. Slack Connect client approval channels are not available in the current public plan catalog.

Before you begin

Confirm plan access:

• Team: External approvals for email and external review paths
• Not currently sold: Slack Connect client approval channels

Identify who will act in the configured client approval channel. Approval actions require authorization in that channel.

Internal multi-step review may still run before a pack goes to the client. Finish internal steps first when your brand uses both flows.

Steps

Open the clients dashboard

1. Run /social and search for clients in the command palette, then run the clients action.
2. Confirm the active brand when Slack asks.
3. Review the dashboard variant for your workspace: no client yet, single brand, or multi-brand.

The dashboard modal is your home for pack status, client records, and pack-level actions.

Add a client contact

1. Choose Add client from the dashboard.
2. For email review, enter the client email used for the secure review link.
3. Slack Connect channel creation is available only in explicitly enabled internal environments; it is not a public purchase path.
4. If workspace policy blocks the automatic invite, resend it or invite the client manually from the generated channel.
5. Wait for App Home or direct messages to refresh with the new client record.

Email review uses a secure external link. Slack Connect review uses the generated shared channel after the client accepts the invite.

Review packs and individual items

1. Open a client pack from the dashboard to see pending items.
2. Open pack details when you need the full item list or pack-level menu.
3. From the pack or item menu, choose Approve, Request changes, or Reject.
4. For change requests, add the feedback the creator needs in the request-changes modal and submit.
5. Send a reminder when the client has not responded and the pack is still pending.

Slack Connect actions must originate in that client’s generated shared channel and from an authorized client workspace. If a button is unavailable, confirm the channel and workspace match the client record.

Resubmit or cancel a pack

1. Open pack details from the dashboard.
2. Choose Resubmit when internal edits are ready for another client review cycle.
3. Choose Cancel when the pack should leave the client review queue.

Use resubmit after your team addresses requested changes. Use cancel when the pack should not continue toward client approval.

What clients see

Clients interact through the review surface shared with them, such as the approval thread or pack view they receive. They can approve, request changes, or reject without seeing unrelated internal items. Your dashboard reflects their decisions on the client path.

Review and export client feedback

1. From the client dashboard, open Feedback log to review the feedback recorded for the active brand.
2. Apply filters or mark a feedback item as responded when the team has completed the follow-up.
3. Choose Export CSV when you need a spreadsheet copy of the current feedback results.

The export contains the feedback available to the active brand at the time you run it. Review the filtered log before you export so the file contains the intended records.

Success criteria

You know the flow worked when:

• Approved items move out of pending approval on the client path
• Requested changes return work to your internal team with the reasons you captured in the request-changes modal
• Rejected items show the review decision you selected and no longer block the pack toward publish
• Pack status on the dashboard matches what clients see in their review surface
• Reminders reach clients who still owe a decision on a pending pack
• Feedback log filters and response state persist when you reopen the log; the CSV export delivers to the Slack destination used by the action.

Troubleshooting

The clients dashboard does not open

Use Team external review links for the public workflow. Treat Slack Connect controls as unavailable unless an operator has explicitly enabled the internal capability.

Clients never receive packs

See Resolve client approval delivery. Verify the client contact, channel authorization, and that internal review completed when required.

Approve or reject is blocked

Confirm you are authorized in the client’s generated shared channel. An admin may need to verify the Slack Connect channel and client-workspace mapping for the brand.

Change requests lack detail

Reopen the request-changes modal and include specific feedback creators can act on. Resubmit the pack after internal edits are ready.

You need internal policy context

Read Approvals and review governance for how client review fits internal governance.

You need command entry points

See Slash commands reference for supported public commands. Use /social and the command palette to reach the clients action.