About our guidance
Our guides help social teams make clear decisions about planning, approvals, and publishing. Our free tools help finish a small piece of that work.
The Slash Social product team publishes these resources and maintains the public product documentation. The team byline identifies Slash Social as the responsible publisher; it does not represent an independent review or a named outside expert.
Slash Social builds social media workflows for teams that work in Slack. You can explore the product, review its data handling, or contact the team.
Operating guides include team-authored examples and adaptable templates. Those examples are illustrative, not measured customer results. Product claims follow the current public product and availability contracts. A documented workflow does not mean that every platform, account type, or access path is available today.
Comparisons cite vendor product or help documentation and explain their method and review date. Vendor plans and behavior can change; use the linked sources to confirm current terms. We sell Slash Social and make that relationship clear when discussing alternatives.
Tool checks cover supported inputs, editing feedback, and downloaded artifacts. Platform guides and layouts are approximate. Image guides stay out of exports, video formats prepare still frames, and PDF pages contain rasterized visuals. Screenshot recognition can misread text; review it before reuse.
Published and updated dates identify content changes. A deployment alone does not refresh those dates. Support review dates describe the owning documentation contract. We correct concrete errors and revisit changing claims when the product or cited source changes.
Send a product or editorial question with the page URL, the passage, and a source or example that helps us check it. For tool problems, describe the input and result without sending private drafts, account credentials, or confidential screenshots.