> ## Documentation Index > Fetch the complete documentation index at: https://docs.monnet.ai/llms.txt > Use this file to discover all available pages before exploring further. # Talking with Monnet > The public feed, your private one-to-one, and how a conversation follows you across Slack, Teams, and email. Every motion carries two conversations: a **public activity feed** everyone on the motion sees, and a **private one-to-one channel** between Monnet and each member. Both reach Monnet, and both can be held from the app, Slack, Microsoft Teams, email, or your coding agent. ## Your private chat with Monnet Open the chat panel from the motion page. This is where you ask for research, rework a draft before anyone sees it, talk through trade-offs, or ask Monnet to spin off a related thread. The chat is live and transparent: * **Streaming replies** — answers arrive token by token. * **Visible reasoning** — you can watch Monnet think before it answers. * **Tool activity** — when Monnet acts, the chat shows what it did: loading a playbook, editing the document, updating the plan, setting the priority, opening a thread. > [!WARNING] > > This is a back-channel, not a confidential one. The panel says so: *"This chat isn't private. Monnet may share what you write here with your team."* Monnet surfaces parts of it to other members when that moves the motion forward. Monnet always answers you in a private chat. If it goes quiet there, something went wrong — tell us. ## The public feed The **Activity** feed at the bottom of the motion is the shared record. Comments and motion events — kickoffs, plan updates, version changes, approvals, decisions — appear in one timeline, so the history of a decision lives in one place. The feed supports: * **@mentions** — type `@` to mention a teammate or an agent. * **Threaded replies** — reply under a comment to keep a side-discussion together. * **Quote-to-comment** — select text in the motion document and a floating **Comment** button drops it into the composer as a quote. * **Emoji reactions** — react to any comment or event. * **Editing** — hover your own comment and click **Edit**. Two view modes: **Highlights** (the default — comments, decisions, approvals, status changes) and **All**, which also shows every low-level action Monnet took. > [!NOTE] > > In a public room, Monnet staying quiet can be a deliberate choice. It's not obliged to reply to every message it can see. ## @mentions reach people where they are @mention someone in a public comment and they get **one** ping, on the channel they're actually reachable on: **Slack first, then Teams, then email**. Profile channel preferences do not change where @mention pings go. The ping quotes the comment and links the motion — and it lands in that person's **private** chat with Monnet, not in public. So replying to it continues the conversation privately, which is usually what you want when someone's been pulled in for a specific question. A direct @mention in a motion comment or shared thread also appears under **Needs your input** in the [inbox](/product/inbox). Replies in Monnet, Slack, or Teams move it to **On your radar**; this doesn't change which channel delivers the ping. ## Working from Slack, Teams, or email Four rules govern every channel: 1. **Monnet responds where it was invoked.** A Slack message gets a Slack reply. 2. **The web app is the source of truth.** Every channel's messages mirror onto the motion. 3. **An @mention notifies across channels**, in the order above. 4. **For private messages Monnet starts itself, it considers your channel preference** on your [Brain profile](/product/brain#choose-where-monnet-messages-you), the motion, and the message. It can choose the app, Slack, Teams, or email when that channel can reach you. Without a usable preference, it keeps the usual channel order. **In a direct message**, Monnet always engages. **In a shared channel** — a Slack channel, a Teams group chat — it waits to be invited: it engages when @mentioned, and stays engaged for the next few messages after it speaks. It won't jump into every thread it can see. **By email**, just hit reply. The address Monnet writes from identifies both the conversation and you, so your reply lands in the right place with no account and no login. For someone whose only channel is email — a guest, or a teammate invited by address who never signed up — email is how they take part in everything. ## Ask Monnet to check in later Some things don't need a plan step — they need a nudge at the right moment. Ask for one in the chat and Monnet schedules a **check-in**: > Send me a reminder on Thursday afternoon. > Ping the team on 12 March at 9am if we haven't heard back. You don't have to spell out an exact timestamp. Monnet turns *"Thursday afternoon"* into a real date and time using **your local timezone**, so a check-in lands when you meant it, not at some server hour. The chat shows **🔔 Scheduled a check-in** once it's set. At that moment Monnet picks the motion back up and does what you asked, in the same place you asked for it — the public feed, or your private conversation with it. ### Change or cancel a check-in Say so in the chat — *"make that Friday morning instead"*, or *"drop the Thursday reminder"*. Monnet knows which check-ins are pending on the motion, so you don't need to repeat the details. The chat shows **✏️ Updated a check-in** or **🔕 Cancelled a check-in**. > [!NOTE] > > Check-ins work on **Open** motions only: you can't schedule one from a draft, and a pending check-in is dropped if the motion is closed before it fires. Each one fires **once** — Monnet doesn't schedule repeating reminders. A check-in is not a [due date](/product/plan#dates). A due date says when work is due and drives a day-level nudge; a check-in is an appointment, kept to the minute. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.