The standup that drifted
Fifteen minutes becoming forty, one message at a time.
Use this templateBuild a Teams chat or group that looks like the real thing — presence rings on every avatar, outgoing messages in that pale lavender rather than a saturated blue, names collapsing across a run, and the toolbar composer along the bottom.
Each one opens in the editor as an editable, fictional scene — names, timings and interface details already set. Change a word, or change everything.
Fifteen minutes becoming forty, one message at a time.
Use this templateA request bouncing between three people who each think it belongs to someone else. Written for process training.
Use this templateThe welcome chat a new starter actually gets. Useful for onboarding decks and HR mockups.
Use this templateThe three above are the ones people build: a standup that drifts, an approval nobody owns, and a new starter's first morning.
A person's name for a one-to-one, or turn on Group and give it a title. The status line under the name is free text — Available, Busy, In a meeting.
Set who wrote each one and when. Consecutive messages from the same person collapse into a run with a single header, as Teams does.
Give a message a reaction and it renders the way Teams draws it. Useful for the moment in a thread where everyone agrees at once.
PNG at 1× free, up to 3× on Pro, the whole thread or one screen, with or without the phone frame.
Our Microsoft Teams 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.
Teams draws a small coloured badge on each avatar — available, busy, away, in a meeting. No other work chat in this roster does it, and it is the fastest way to tell a Teams screenshot from a Slack one at a glance, before you have read a word.
Outgoing messages sit in a very soft purple-grey, several shades lighter than the brand colour and nowhere near the saturated blue people expect from a Microsoft product. A mockup that fills the bubble with #6264A7 looks like a Teams-branded messenger rather than Teams.
Teams keeps enclosed message bubbles where Slack uses flat rows. That is the structural difference between the two, and it is why these are separate skins rather than one work-chat skin with a colour switch — a recolour would get exactly this wrong.
Teams puts formatting, attach, emoji, GIF, sticker and more along the bottom of the composer. It is visually heavier than any other composer here, and leaving it as a plain input is one of the quickest tells.
Consecutive messages from one person show the name and time on the first only. Repeating the header on every row makes a five-message exchange read as five separate conversations.
A Teams group carries a title — “Platform Standup”, “Procurement” — rather than a list of participants. Set it in the Contact section, and the People section decides who speaks.
Everything made here is simulated. SocialMock has no connection to Microsoft Teams 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 Microsoft Teams editor