Scale B.O.S.S. Messages Guide

How the collaboration and conversation layer works, why it matters, and how to use it effectively.

Messages is the shared communication layer inside Scale B.O.S.S. It provides a dedicated space for direct messages, small-group coordination, and work-linked conversations — all without leaving the platform or separating discussion from the work it supports.

What Messages Is

Messages is the in-platform communication center accessible from the top-right header. It opens as a side drawer, allowing users to review threads, reply to conversations, or start new ones without leaving their current page.

That placement is intentional. A collaboration tool is only useful when it's reachable the moment a question arises. By keeping Messages always available in the header, Scale B.O.S.S. enables teams to capture follow-up and resolve questions in context — rather than pushing discussion into disconnected email threads, texts, or memory.

Messages supports direct messaging between individuals, group messaging among a working set of people, and work-linked conversation threads tied to specific records in the system. Those linked discussions can be attached to regular charters, personal impact charters, ideas, CFOs, BE questions, recurring items, and related execution records.

Why This Feature Matters

It keeps communication inside the same operating system where the work lives.
It reduces context loss by keeping questions, updates, and decisions attached to the relevant initiative or item.
It gives every user a fast path from awareness to response without leaving the current page.
It complements private Notes & Tasks by providing the shared layer for team communication and follow-through.
It improves accountability because message history can be revisited rather than reconstructed from memory.

How Messages Fits with the Rest of the Platform

Messages is the shared communication layer inside Scale B.O.S.S. It works alongside Notes & Tasks, charters, ideas, CFOs, and other tracked work — it does not replace them.

Feature	Best Use	What It Is Not
Messages	Shared conversation, follow-up, clarification, and work-linked discussion between people or groups.	Not a private scratchpad or the place for personal reminders only one person needs to see.
Notes & Tasks	Private capture, drafting, and personal to-dos owned by an individual user.	Not the right place for decisions, instructions, or questions the broader team needs to see.
Charters, Ideas, CFOs, Goals	The official system of record for structured work, ownership, timing, and status.	Not the sole place for nuanced back-and-forth discussion; Messages supports the conversation layer around the record.

Opening the Message Center from Anywhere

The speech-bubble icon in the main header opens the Messages drawer from anywhere in the platform. Because it sits alongside other persistent header tools, users can move into communication without abandoning the page they're reviewing. This is especially valuable when working inside a charter, reviewing a KPI rhythm, evaluating performance, or checking dashboard signals and needing to ask a quick question.

The header also serves as the visibility layer for message activity. Users can see that new communication exists before opening the drawer, then move directly into the conversation from the same location — keeping awareness and response in one place.

Understanding the Drawer Layout

Left pane: Create a new conversation, search, apply filters, and scan existing threads.
Right pane: Read the selected discussion, review participants and dates, and continue the conversation in the composer.
Top row: Access conversation-level controls such as closing the drawer or switching between create and view states.
Bottom composer: Enter the next message without leaving the thread.

Filters and Thread Types

The left-side filter stack keeps the message center manageable as volume grows. Rather than scrolling through every thread, users can switch to the view that matches the type of communication they need to review.

Filter	What It Surfaces	How to Use It Well
All	Every visible thread in one list.	Use for a full view of current organizational communication and recent activity.
DMs	One-to-one conversations between specific users.	Best for quick coordination, clarifying responsibility, or requesting an update from one person.
Groups	Multi-person conversations with a shared thread and optional group name.	Use for recurring collaboration among a small set of people who need the same information.
Charters	Work-linked discussion threads associated with tracked initiatives and records.	Use when the conversation belongs next to the work, not only in a private chat.
Broadcasts	Broader message threads intended for wider visibility or announcement-style communication.	Use when a message needs controlled reach across a wider audience rather than a small working thread.
@Mentions	Threads where the user has been directly called into the conversation.	The fastest way to catch responsibilities, decisions, or questions that require your response.
Unread	Threads with new activity not yet reviewed.	Use as a daily inbox to ensure communication doesn't get lost in a busy workstream.

What the Thread List Is Telling You

The thread list is more than a message inbox — it's a quick operating view of active communication across your work. Each entry provides enough information to decide whether a thread needs immediate attention: title, short preview, relative date, and an unread indicator when applicable.

A thread list may include a recurring KPI scorecard rhythm, a Business Essentials item, a general topic, and a named working group — all side by side. That mix reflects the feature's design intent: direct communication and work-linked communication live together in one place.

Starting a New Conversation

The New button is the entry point for outbound communication. It separates Message from Broadcast so users make a deliberate choice about the type of communication they're initiating.

Choose Message when the conversation is intended for one or more named participants and should support normal back-and-forth discussion.
Choose Broadcast when the communication is intended for broader visibility or announcement-style distribution.

In the compose screen, recipients are added to the To field as chips. An optional Group Name can be added when the thread should function as a named group. The message body captures the initial communication, and Send Message creates the thread.

Direct Message vs. Group Message

A one-to-one conversation is the right choice when only one person needs the information or decision. It keeps responsibility clear and avoids pulling unnecessary people into the thread. A group message is better when multiple people genuinely need the same information, context, and conversation record.

The optional group name is especially useful when the same people will work together repeatedly. A named group turns a temporary exchange into a reusable communication lane, reducing fragmentation and eliminating the need to recreate the same ad hoc thread repeatedly.

Working Inside an Active Thread

Inside a live thread, the interface is structured to preserve context. The conversation header shows the thread title and participant count. Message history is grouped chronologically so users can follow the sequence of discussion. Replies appear inline with date separators, and the composer remains anchored at the bottom for immediate response.

This design encourages a useful habit: review the history first, then respond with the current state in mind. A thread might preserve earlier questions and observations alongside a later follow-up requesting current status — keeping the full context in one place.

Messages Attached to Work Records

One of the feature's greatest strengths is that conversations don't have to float free from the work. Threads can be attached to tracked records in the platform, which is why a thread list may include a KPI rhythm item or a specific Business Essentials question alongside personal chat names.

This matters because shared execution often breaks down at the discussion layer. The official record may exist in the system, but the real nuance, question, or blocker sits in someone's memory or an external app. Messages closes that gap by keeping discussion where the work lives.

Use a work-linked thread when the conversation belongs to a charter, personal impact charter, idea, CFO, goal, evaluation item, or related record.
Use a direct message when the communication is person-specific and doesn't need to become part of the work record.
Use a named group when a recurring working team needs an ongoing conversation lane broader than a single object but narrower than a broadcast.

What Leaders Should Look For

Threads that remain active without response may signal stalled decisions or unclear ownership.
Repeated questions in the same area may indicate a process gap, unclear documentation, or weak handoff discipline.
Healthy message patterns show focused communication tied to real work — not recurring clarification on the same issue.
Unread and mention queues function as a leadership communication inbox; if ignored, execution quality degrades quickly.
If the same topic keeps surfacing in DMs instead of the work-linked thread, the team may be bypassing the system of record.

What Good Usage Looks Like

Strong Usage	Weak Usage
Using a work-linked thread to ask for the status of a KPI cadence item so the conversation stays attached to the initiative.	Asking for updates in disconnected channels where no one can later reconstruct what was decided.
Creating a named group for a recurring working team so the right people stay in one thread over time.	Starting a new one-off conversation every time the same people need to discuss the same subject.
Using mentions and unread filters as a personal inbox so responsibilities are addressed quickly.	Ignoring unread activity until decisions are late or work stalls because a question went unnoticed.
Keeping the official work record in the charter, idea, CFO, or goal while using Messages for discussion around the work.	Treating the chat thread as the sole source of truth for ownership, due dates, and scope.
Using Broadcasts for wider communication when the message requires broad awareness.	Using a small DM thread for something the broader group needs to see or act on.

Best Practices for Using Messages Well

Keep the official record in the platform object and use Messages for clarification, coordination, and decision support around that record.
Name recurring groups clearly so people understand the thread's purpose and when to use it.
Use direct messages for topics that genuinely belong between a small number of people.
Use work-linked threads when the conversation affects the object, owner, timeline, or outcome.
Check mentions and unread filters daily to keep the communication layer responsive and trustworthy.
Don't let important decisions die in a thread. When a conclusion affects the official record, update the charter, CFO, idea, or relevant object so the system reflects the outcome.

Common Mistakes to Avoid

Using Messages as the sole source of truth for scope, due dates, or status instead of updating the official record.
Starting too many one-off threads instead of keeping recurring teams in a named group.
Leaving a question in a DM when the discussion should sit on the charter, idea, CFO, or work record itself.
Ignoring unread or mention filters until response times degrade and people lose trust in the channel.
Broadcasting to a wide audience when the topic only requires a focused working thread.

Why Messages Strengthens the Rest of Scale B.O.S.S.

Scale B.O.S.S. is most effective when the platform not only tracks work but also helps people coordinate around it. Messages closes that loop — turning the system from a set of records into an operating environment where teams can ask, answer, clarify, and move work forward without losing context.

Used well, Messages doesn't compete with Notes & Tasks or formal work objects. Notes & Tasks helps individuals think and organize privately. Charters, CFOs, ideas, and goals hold the official structure of the work. Messages gives the team a collaborative lane to discuss the work while keeping that conversation close to what matters.

In a scaling organization, execution quality often comes down to whether the right conversation happens in the right place quickly enough. Messages is the layer inside Scale B.O.S.S. that helps make that possible.

Scale B.O.S.S. Messages Guide: Collaboration and Conversation