The incident channel
A production incident from alert to all-clear. The shape every SaaS demo and post-mortem deck needs.
Use this templateBuild a Slack channel or DM that looks like the real thing — flat rows rather than bubbles, square avatars, consecutive messages collapsing into runs, reaction chips under the text and the aubergine header around all of it.
Each one opens in the editor as an editable, fictional scene — names, timings and interface details already set. Change a word, or change everything.
A production incident from alert to all-clear. The shape every SaaS demo and post-mortem deck needs.
Use this templateThe numbers landing in real time, with the reaction everyone screenshots.
Use this templateA one-to-one where nobody says the thing directly. For talks and training about workplace communication.
Use this templateThe three above are the ones people build: an incident channel from alert to all-clear, launch-day numbers landing in #general, and a quiet DM about a deadline.
Turn on Group and set the name to #whatever. Add the people who post in the People section — each gets their own colour automatically.
Set who wrote each one and when. Consecutive messages from the same person collapse into a run without a repeated name, exactly as Slack does.
Give a message a reaction and it renders as a chip with a count underneath. It is the detail that makes a channel look lived-in rather than scripted.
PNG at 1× free, up to 3× on Pro, the whole channel or one screen, with or without the phone frame.
Our Slack skin is rebuilt from the real interface in code rather than traced from a screenshot, so the details that make it recognisable survive at export resolution. Here is what those details actually are.
This is the thing every fake gets wrong. Messages are flat rows against the page background — name in bold, time beside it, text underneath, nothing enclosing any of it. If your mockup has rounded coloured bubbles it is a messaging app wearing Slack's colours, and anyone who uses Slack for work will see it immediately.
Slack rounds its avatars to a soft square. Almost every other app in this roster uses a circle. It is a small radius difference that your eye reads before you have finished looking at the text.
When the same person posts twice in a row, the second message has no avatar and no name — just the text, indented to line up. That collapsing is most of what gives a Slack channel its density, and drawing every row with a full header makes a five-message thread look like a support ticket.
Slack's chrome is that deep purple, with the channel name and its member count. Not blue, not grey. It is the frame the whole screenshot sits in, so getting the hue wrong costs more than any single row.
A Slack reaction is a small rounded chip with the emoji and a count, sitting beneath the text on its own line — not overlapping a bubble corner the way iMessage and Messenger do. Add a reaction in the editor and it renders as the chip.
The box at the bottom carries bold, italic, link and the rest along its edge, because Slack's composer is a rich-text field rather than a plain input. It is the last thing in the screenshot and it is often the giveaway.
Everything made here is simulated. SocialMock has no connection to Slack and cannot read, send or alter a real message. Do not use a mockup to impersonate anyone, pass it off as a genuine screenshot, or present it as evidence in any legal, workplace or academic matter — see our Acceptable Use policy. For general information about legal risk, read is it legal to fake a screenshot? If you publish somewhere a viewer might mistake it for real, switch on the “Simulated” label before exporting.
Click straight into the preview and type. Export when you are done — free at 1×, up to 3× on Pro.
Open the Slack editor