How-to guide

Complete Quick Start and continue your Post

Follow the complete Slack workflow to complete quick start and continue your post, including prerequisites, decisions, and recovery steps.

Goal

Save the first canonical Post through Quick Start, then continue that same Post in Create, Approvals, or Calendar.

When to use this

Use this workflow when:

You installed Slash Social and need to create the first brand and Post.
A teammate delegated first-brand setup to you.
You closed Slack, Composer, OAuth, or checkout and need to resume the exact Post or action.
Generation, account connection, or access failed and you need the canonical recovery path.

Quick Start is a truthful projection of canonical records. It does not store a mutable completion percentage, and it does not count a generation attempt as saved value.

Before you begin

Slash Social must be installed in your Slack workspace. The actor must be an eligible administrator, brand owner, or delegated setup operator.

You do not need a connected social account. Quick Start requires a brand name, accepted brand direction, and one saved canonical Post.

Steps

Create or resume the brand

Open Slash Social App Home.
Select Set up brand direction when no brand exists.
Enter the brand name and, optionally, a website.
Continue with editable starter direction if enrichment is slow, skipped, or fails.
Review and accept the direction.

If another teammate should complete this work, select Delegate setup. The teammate receives setup access without billing or ownership authority. A delegated operator can select Decline setup to return the assignment.

Save the canonical Post

Select Open Composer.
Write or generate the Post in the permanent Create Composer.
If generation runs in the background, select View Post progress to inspect the canonical job and Post state.
Review the editable result and save it.
Open the saved Post from Create.

Quick Start completes only after the durable save. Composing, queued generation, failed generation, and rendered-but-unsaved content remain incomplete.

Choose what happens next

Choose the immediate job for this Post:

Schedule it yourself.
Ask a teammate to review it.
Ask a client to approve it when the workspace has a permanent client-review capability.
Keep it as a draft.

Slash Social can recommend one option from safe evidence, but your explicit choice wins. The choice applies to this Post, not to a permanent customer persona.

Resume across a blocker

When the selected action needs OAuth, access, approval, generation, or checkout, Slash Social stores a durable pending intent. After the blocker resolves, it reopens the same authorized Post and action once.

If the intent is no longer valid, Slash Social invalidates or reroutes it to one safe recovery action. It does not restore the retired checklist or create a second onboarding-only Post.

Confirm it worked

Quick Start displays ✓ First real Post saved before it retires.
The Post reopens from Create with the same content and provenance.
A review decision lives in Approvals.
A schedule or publishing commitment lives in Calendar.
Closing and reopening Slack resumes the same valid object and action.

Troubleshooting

Quick Start still shows the Post as incomplete

Confirm you saved the Post. Generation completion or a preview does not count until the canonical Post is durably saved.

Generation failed

Select Open failed work, review the failure in Create, and retry. Your accepted brand direction and compose session remain available.

OAuth or checkout was canceled

Return to App Home or Create. The Post remains saved. Retry the selected action when you are ready; cancellation is neither success nor failure.

Access changed while the action was pending

Ask an administrator to restore the required access. Slash Social must not reveal or resume a Post after authorization is lost.

App Home shows a different work center

Open Create and select the saved Post. Explicit navigation takes precedence over first-run guidance, so App Home should render the destination you selected.