Why do decisions end up in direct messages, and what should you copy out?
A pricing exception typed in a DM never reaches finance, the invoice, or the next owner of the account — here is what to copy out the same day.
Tuesday, 16:12. A seller and a customer-success manager are in a Slack DM. The customer has asked for 12 percent off SKU A-440 on quote Q-8841, sterling, for a renewal that invoices on the first of next month. The rate card says 8 percent. The seller types: “ok go 12, I’ll sort it.” The CSM replies with a thumbs-up. No one opens the quote. No one names the currency again. No one says whether 12 percent stacks with the existing rebate. That message is the whole decision. It has a time from Slack’s clock, two display names, and a number. It has no object ids the billing system uses, no signer whose role owns exceptions, and no place finance is allowed to see.
A decision ends up in a direct message because that room is small, fast, and has no filing cost. Two people can say yes without inviting anyone who might object, and without naming an object the rest of the company can open. Private conversation is often appropriate. The outcome still needs a home the next team can find.
This guide traces that exception from the DM to the invoice, then offers a habit that keeps the private talk. You do not have to ban DMs. You do need a rule for what may not live only there. The Problems hub is the wider series; search is not memory is the general case. A DM is the same idea with a smaller room and a worse search.
Why the small room wins
They go to the smallest available room. That room holds nobody who can object in public, and no duty to write the result into a system. Policy decks say exceptions go to a manager. The DM is open now. The slide is not.
Speed is the other reason. Typing “ok go 12” is faster than opening the quote. Asana’s Anatomy of Work Index, a survey of more than 10,000 knowledge workers, found that 58 percent of the day went to work about work — coordinating, searching, chasing status. Chasing “did we agree 12 or 8” is that 58 percent, paid by people who were not in the DM.
People also use DMs because the topic is sensitive: a person, a customer complaint, a number that should not sit in #general. That instinct can be right. The mistake is treating privacy of the conversation as privacy of the outcome. Finance still has to invoice. The next seller still has to explain the margin.
Yang and colleagues, in Nature Human Behaviour, showed that remote work made collaboration networks more static and siloed. The DM is the extreme form of that silo: two people, no bridge, no artefact. The next owner of the account is not in the graph.
McKinsey’s State of AI found use in most organisations and scale in far fewer. Assistants arrived in the small room first, because that is where people already finish work. The official programme is still a pilot. The unofficial yes is already in production.
AI makes the small room feel more complete. A model can draft the customer email from the DM. The guess gets a better tone, not a field. A fluent paragraph in the same window is still a second unofficial copy. IBM’s shadow AI research is what happens when that window is a personal account: the draft leaves, and the company cannot reconstruct the decision. The sanctioned DM is only slightly better. It is still not a quote.
What goes wrong when the only yes is in a DM
The seller means to update Salesforce after the next call. The call overruns. A new thread starts about another account. On Wednesday the customer thanks them “for the 12” on an older email — a second unofficial copy, still not a field.
Finance never saw it. The sales manager never saw it; exceptions above 10 percent were supposed to go to her. Legal never saw it; twelve percent stacked with a rebate may breach another clause. Operations will pick the order against the list price. The next seller, when the first one leaves in six weeks, will not know to search for “A-440” in someone else’s private history. Collaborative AI for legal and compliance review often starts here: one team has a memory, the other has a system, and both are sincere.
On the first of the month the billing job reads Salesforce. The opportunity still has 8 percent. The invoice prints 8 percent. The customer refuses it. A credit note is raised for the difference, reason code “goodwill.” Two versions of the truth are now in official systems: the invoice at 8, the credit at the gap to 12, and a CRM that still says 8. The company funded a discount it cannot point to.
Six months later a new finance manager asks why margin does not match the rate card. She has no access to the original DMs. Slack retention on DMs was 90 days. Reconstruction becomes interviews. Votes are not controls.
Rule 37(e) is the US civil procedure test many counsel already know: if electronically stored information that should have been preserved is gone, a court can sanction the failure. A pricing exception that changed revenue is the kind of thing a later dispute asks for. Sarbanes-Oxley does not mention Slack. For companies that file with the US Securities and Exchange Commission, it does require a control trail for how a number became the number. “We think Sarah said 12” is not that trail.
Where Article 14 of the EU AI Act applies, a person must be able to interpret an output and refuse it. A thumbs-up in a DM is not that interpretation. A model that drafted the customer email from the same window has not created oversight. It has created a second sentence nobody signed.
A wider room is not automatically the fix. Ban business DMs, open a #decisions channel, buy DM capture so compliance holds everything: an archived DM still may have no object id, no signer role, and no field. The exception did not always need a bigger audience. It needed one authorising record.
| What lived in the DM | What finance needed | What you have six months later |
|---|---|---|
| “ok go 12” | SKU, quote id, currency, percent | Interviews, if retention survived |
| Two display names | A signer whose role owns exceptions | Disabled accounts |
| A thumbs-up | A timestamp from the system of record | Slack’s clock, maybe gone |
| A drafted customer email | A field on the quote | A credit note marked goodwill |
How you keep private conversation without losing the outcome
Keep the DM for “can you join at 3,” for a sensitive personnel note, for colour the customer should not see in a channel. Stop closing money only in that window.
One approach is a same-day rule: any change to price, credit, date, or scope that another team will be measured on gets written into the object that team uses, the same day, with a named signer. One sentence, usable in a sales meeting, and it requires nobody to read private chat.
Practical catches that respect privacy:
- Invoicing rejects a discount that is not on the quote.
- CRM requires a reason code and an approver on overrides above a threshold.
- The job that proposes the exception is visible to finance before the invoice runs.
- Fail-closed on the write: if nobody approves, nothing happens. The field stays at 8 until a signer moves it.
Sellers can keep DMs. The company can refuse to invoice from them. You cannot police a customer’s WhatsApp. You can refuse to treat ithe quote.
NIST’s AI Risk Management Framework asks you to govern and measure behaviour you can observe. A DM is observable to two people. It is not observable as a control. Mapping “we have Slack” is not mapping the exception.
What you should copy out
Copy the outcome, not the chat. Four lines are enough:
- The decision, with object names the systems use (SKU, quote id, currency, percent).
- Who was allowed to make it.
- Who signed, with a timestamp from the system, not from memory.
- Where a stranger would find it in six months.
Do not copy the jokes, the back-and-forth, or “I’ll sort it.” Do not paste the whole DM into a channel “for visibility.” Visibility is a link to the object.
If AI drafted the customer email from the DM, say so on the record, and send the email from the quote, not from the paste. Write-back — when AI changes a live system — should wait for the signer. The model may draft. It may not land from a private window.
Search is not memory is why “we can always find the DM” fails: private history, retention sliders, and the next owner’s missing access. What an AI workstream is is one named place those four lines can live.
Walk Tuesday again after the habit exists. The DM still happens. At 16:40 someone opens the quote, writes 12 percent, names the signer, and records whether it stacks. Finance can see the object before the first of the month. The invoice prints 12, or it prints 8 and a stored refusal. The credit note marked goodwill does not appear, because the number was never unofficial. The next seller, six weeks later, opens the quote rather than someone else’s private history.
That is the difference between capture and an authorising record. Capture is a zip. The record is a field.
How to start with one recurring decision
Ask accounts receivable for the last three credit notes marked goodwill and try to find the authorisation without talking to the seller. The ones you cannot find are your DM problem, already in cash.
Then pick one recurring class — pricing exceptions, ship-date changes, credit notes — and apply the same-day rule to the next instance only. Keep every other DM as it is. You are not running a culture campaign. You are closing one hole that already hit the ledger.
If the next instance still dies in a DM, the catch is not in place. Invoicing still accepts a number that is not on the quote, or CRM still allows an override without a reason code. Fix the catch before you buy a capture product. Capture without a field is how you get a larger archive of the same missing decision.
Day Webster’s chairman wanted a way to see who approved what. Digby Fine English wanted humans in the loop before anything commits. Those lines are about the object, not the chat. Hamiltons Chocolates wanted payroll, invoicing, and forecasting to stop consuming a month. Invoicing from a DM is how those hours come back as goodwill credits.
If you want the chain in product form, governance is one place to hold who may approve a write. Nimbus is a Collaborative AI operating system: the exception can live on a workstream that finance can see, with connectors read-only until a signer moves a field. Decision History will show who signed, with actor, tier, and timestamp. It is not the statutory archive and it is not the books. The quote and the ledger stay where they already live. The platform reaches 2,000+ integrations; a connection is not permission to invoice from a private window. GDPR applies today; ISO 27001 and SOC 2 Type 1 independent audits are underway.
You can start this week with the quote object and a named signer. Private rooms will stay useful. What changes is that the decisions that leave those rooms have a home that is not an interview.
Related reading
References
About Nimbus
Nimbus is a Collaborative AI Operating System built around four core pillars that bring human teams and autonomous AI together into a single, unified workspace.
Communication: Keep context tied to the job. Unify emails, meeting recordings, transcripts, and operational files directly within active projects—ending knowledge silos buried in private inboxes, scattered Slack threads, or unrecorded calls.
Collaboration: Work alongside AI in real time. Bring people and AI agents onto the exact same brief, visual canvas, or initiative. Query company-wide data, invite agents into live calls, and co-create in one shared space—eliminating the split between human group chats and isolated AI sidebars.
Automation: Put routine workflows on autopilot. Connect more than 2,000 enterprise tools and standardize repetitive operations. Background loops run on schedules or data triggers with full execution logs, ensuring operational knowledge is shared across the team rather than trapped in one person’s head.
Governance: Deploy AI with absolute control. Enforce strict role-based access controls across workspaces. AI agents can analyze, summarize, and draft—but no live system changes or external communications occur without explicit, verified human sign-off.
Questions about decisions in DMs
Should we ban business DMs?
You do not have to. Keep DMs for scheduling and sensitive talk. Copy price, credit, date, and scope into the object the next team uses, the same day, with a named signer.
Is archiving DMs enough?
An archive holds sentences. It still may lack the object id, the signer’s role, and the field that invoiced. Capture is not the same as an authorising record.
What if the customer only messages privately?
You cannot police a customer’s WhatsApp. You can refuse to invoice from it. The official number lives on the quote, not in the private window.
If AI drafted the customer email from a DM, is that the official record?
No. A fluent paragraph in the same window is a second unofficial copy. Send from the quote, name that the model drafted, and wait for a signer before any write-back.
See what governed AI looks like on your stack.
Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.