Resume or repair Quick Start

Goal

Resume Quick Start or correct an early setup choice without resetting canonical Posts, approvals, schedules, or brand data.

Before you begin

• Open Slash Social App Home and confirm the active brand.
• You need access to the brand or an eligible setup assignment.
• Do not delete the workspace or recreate a saved Post to recover a pending action.

Steps

1. Open Slash Social App Home.
2. Follow the primary Quick Start action:
   • Set up brand direction when no brand exists.
   • Review brand direction when direction needs acceptance.
   • Resume Composer when an unsaved compose session exists.
   • View Post progress while generation is running or the result is ready.
   • Open failed work when generation needs recovery.
3. Correct only the authoritative record that is wrong:
   • Switch the active brand before editing brand-scoped data.
   • Edit brand settings or brand direction from Settings.
   • Edit pillars from Settings.
   • Edit cadence or the approval channel when a scheduling or review action requires it.
4. Open the saved Post from Create if Quick Start already completed.
5. Retry the intended action from that Post. Slash Social resumes a valid pending intent once; if it is no longer valid, the app offers a safe replacement action.

Understand what recovery preserves

Quick Start recovery moves forward from saved product records. It does not restore an older setup screen or erase work to make the first-run experience start over.

• Accepted brand direction remains attached to the brand.
• A saved Post remains in Create, even when generation, review, or scheduling fails afterward.
• An unsaved compose session can resume when its durable session is still valid.
• Review assignments remain in Approvals.
• Scheduled work remains in Calendar.
• A delegated setup assignment remains with the eligible teammate until they complete or decline it.

If the original action can no longer continue, Slash Social shows one safe next action. For example, an expired account connection routes to reconnection, a removed reviewer routes to reassignment, and a Post that was already saved routes to Create instead of opening first-run Composer again.

Correct an early choice

You do not need a reset to correct information entered during Quick Start:

1. Use the brand switcher to select the intended brand.
2. Open Settings to update brand direction, pillars, cadence, or approval routing.
3. Open Create to edit the saved Post.
4. Retry the Post action that depends on the corrected setting.

Changing a setting does not duplicate the Post or replay work that already succeeded. Check the destination that owns the result before retrying: Create for Posts, Approvals for reviews, and Calendar for schedules.

Confirm it worked

• App Home shows the expected Quick Start state for the active brand.
• Saved Posts remain in Create.
• Approval decisions remain in Approvals and scheduling commitments remain in Calendar.
• Retrying does not create a duplicate Post, review, schedule, charge, or notification.

If setup was delegated, also confirm the assignment appears for the intended teammate and that billing or brand ownership did not change. Delegation grants only the access needed to complete setup.

If something goes wrong

Quick Start does not appear

Quick Start retires after the first canonical Post is saved. Open Create and select the saved Post instead.

Composer does not resume

Confirm the active brand, return to App Home, and select Resume Composer. If the compose session expired, open Composer and start a new Post using the accepted brand direction.

A pending action opens a safe fallback

The original object, permission, or prerequisite changed. Follow the offered recovery action rather than attempting to restore the retired onboarding path.

Saved work is missing

Confirm the active brand and search Create. If the Post is still missing, record the workspace, brand, approximate time, and error reference shown by Slack before contacting support. Do not send tokens or private Post content.

Generation still fails after retry

Use Retry a failed generation and keep the existing canonical Post or compose session.

The same action appears twice

Do not complete both copies. Open the canonical destination and check whether the Post, approval, or schedule already exists. Continue from the existing object. If duplicate side effects remain visible, capture their links and contact support without deleting either record.

A teammate cannot accept delegated setup

An administrator should confirm that the teammate still belongs to the workspace and can access the brand. If they are no longer eligible, have them decline the assignment and delegate to another teammate.

Next step

Return to Save your first Post with Quick Start or open the saved Post in Create.