Slack Schedules a Meeting When Employees Send a Fourth Message
Slack’s new conversation behavior converts a direct message or thread into a calendar event before either employee has agreed to meet, assigning attendees, a time, and a notes workspace.
Slack has begun treating the fourth message between two employees as a scheduling event. At that count, the conversation header changes from “Direct message” or a thread to “Scheduled meeting,” and the triggering sentence is copied into the agenda. The invite assigns both employees as attendees and selects a start time from their calendars.
During a printer-toner exchange, the pair used Slack’s huddle option and settled the question before the invite time. The event remained open, with an AI meeting-notes canvas attached to the thread and the huddle marked “pre-meeting resolution.” The canvas preserved the fourth message as its agenda while both employees returned to work.
Managers are praising a drop in message counts after staff started packing debates into single paragraphs. One employee sent 1,146 words about toner in a single message; Slack classified it as “efficient communication” and attached no meeting. Three hours later, nobody could locate the decision, but the old thread’s calendar icon kept blinking beside the word “resolved.”
