[{"data":1,"prerenderedAt":633},["ShallowReactive",2],{"site-nav-content":3,"hub:problems:posts":178,"site-cta-content":601,"hiring-banner-content":621},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":131,"id":162,"title":163,"archived":164,"authors":165,"badge":165,"body":166,"date":165,"definedTerm":165,"department":165,"description":170,"extension":173,"eyebrow":165,"faqHeader":165,"faqs":165,"footerBand":165,"headline":165,"image":165,"industry":165,"jobType":165,"listed":130,"location":165,"navigation":130,"openRoles":165,"pageLayout":165,"path":174,"relatedHeading":165,"seo":175,"series":165,"sitemap":164,"status":165,"stem":176,"subhead":165,"tags":165,"video":165,"whyJoin":165,"workplaceType":165,"__hash__":177},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","/overview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","/product/conflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","/product/agent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","/product/lifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","/product/wiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","/product/workstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","/product/perception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","/product/governance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","/models",{"label":47,"to":48},"Pricing","/pricing",{"label":50,"to":51},"Integrations","/integrations",{"label":53,"to":54},"Security","/security",{"label":56,"to":57},"Partners","/partners",{"label":59,"to":60},"Insights","/blog",{"productHeading":5,"companyHeading":62,"legalHeading":63,"docsLabel":64,"docsUrl":65,"statementLines":66,"copyright":69,"companyLinks":70,"legalLinks":100,"socialLinks":110,"bottomLinks":120},"Company","Legal","Docs","https://docs.gonimbus.ai",[67,68],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[71,72,73,74,75,78,81,84,87,90,92,95,98],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":76,"to":77},"Glossary","/glossary",{"label":79,"to":80},"Compare","/compare",{"label":82,"to":83},"Evaluate","/evaluate",{"label":85,"to":86},"Problems","/problems",{"label":88,"to":89},"Use cases","/use-cases",{"label":91,"to":57},"Partner Program",{"label":93,"to":94},"Careers","/careers",{"label":96,"to":97},"System status","/status",{"label":7,"to":99},"/contact",[101,104,107],{"label":102,"to":103},"Terms of Service","/terms",{"label":105,"to":106},"Privacy Policy","/privacy",{"label":108,"to":109},"Compliance","/compliance",[111,114,117],{"label":112,"href":113},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":115,"href":116},"X","https://x.com/gonimbusai",{"label":118,"href":119},"Instagram","https://www.instagram.com/gonimbus_ai/",[121,123,125,126,127],{"label":122,"to":103},"Terms",{"label":124,"to":106},"Privacy",{"label":108,"to":109},{"label":96,"to":97},{"label":128,"to":129,"external":130},"LLMs.txt","/llms.txt",true,{"text":132,"prompt":133},"Ask AI about Nimbus",{"I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making":134,"platforms":136},{" Summarize the highlights from Nimbus's website":135},"https://gonimbus.ai",[137,142,147,152,157],{"name":138,"label":139,"icon":140,"hrefPrefix":141},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":143,"label":144,"icon":145,"hrefPrefix":146},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":148,"label":149,"icon":150,"hrefPrefix":151},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":153,"label":154,"icon":155,"hrefPrefix":156},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":158,"label":159,"icon":160,"hrefPrefix":161},"google-ai","Google AI","simple-icons:google","https://www.google.com/search?udm=50&aep=11&q=","content/shared/nav.md","Site navigation",false,null,{"type":167,"value":168,"toc":169},"minimark",[],{"title":170,"searchDepth":171,"depth":171,"links":172},"",2,[],"md","/shared/nav",{"title":163,"description":170},"shared/nav","rDEv5cVG6P2l9ATcdQv2n6VOQiSL5ioOutyfvGevcD0",[179,398],{"id":180,"title":181,"archived":164,"authors":182,"badge":185,"body":187,"date":374,"definedTerm":165,"department":165,"description":375,"extension":173,"eyebrow":165,"faqHeader":376,"faqs":379,"footerBand":165,"headline":165,"image":165,"industry":165,"jobType":165,"listed":164,"location":165,"navigation":130,"openRoles":165,"pageLayout":165,"path":389,"relatedHeading":165,"seo":390,"series":391,"sitemap":130,"status":165,"stem":392,"subhead":165,"tags":393,"video":165,"whyJoin":165,"workplaceType":165,"__hash__":397},"content/blog/search-is-not-memory.md","What is the difference between search and memory at work?",[183],{"name":184,"to":135},"Nimbus Research",{"label":186},"Playbook",{"type":167,"value":188,"toc":367},[189,193,207,212,215,218,221,224,253,256,260,263,266,276,285,288,291,295,298,301,304,311,314,317,331,334,338,341,344,347,350,354,357,360],[190,191,192],"p",{},"Search finds a string. Memory is a decision you chose to keep: who owns it, what it said, and where it still lives after the people leave. They get treated as one because both return text, and a hit on last year’s channel feels like remembering. A ranking function over messages is not the same as a small number of facts somebody was willing to sign.",[190,194,195,196,201,202,206],{},"This guide is for teams whose answer to “what did we decide?” is “search Slack.” You do not have to buy a new index. You do need a habit for what the company is prepared to assert. ",[197,198,200],"a",{"href":199},"what-is-institutional-memory-in-enterprise-ai","Institutional memory in enterprise AI"," is the company-scale version of this distinction; ",[197,203,205],{"href":204},"decisions-made-in-direct-messages","decisions made in direct messages"," is the cost side.",[208,209,211],"h2",{"id":210},"what-is-the-difference-between-search-and-memory","What is the difference between search and memory?",[190,213,214],{},"Search answers: which messages used these words, in rooms I can still see, on dates the retention slider still holds.",[190,216,217],{},"Memory answers: which facts we stand behind, who owns each one, when it took effect, and where the live copy is.",[190,219,220],{},"Slack and Teams store “this message contains the characters p-r-i-c-e.” They do not store “this message is the price.” The hit on “higher price” does not name the SKU, the customer, or the quote version.",[190,222,223],{},"Four limits show up quickly:",[225,226,227,235,241,247],"ul",{},[228,229,230,234],"li",{},[231,232,233],"strong",{},"Retention."," A 90-day delete is a storage and privacy choice. Last year’s exception will not be in the index. “We can always search” is false on day 91.",[228,236,237,240],{},[231,238,239],{},"Permission."," Private channels and DMs are not in everyone’s results. The person reconstructing the invoice often has the worst access to the room where the exception was typed.",[228,242,243,246],{},[231,244,245],{},"Export."," A company-wide dump is a legal artefact, not a daily tool. Custody is a place that still holds the artefact, not a promise that search used to work.",[228,248,249,252],{},[231,250,251],{},"Ranking."," Search orders by recency and popularity. The wrong “12 percent” — a joke, a different account, a draft — can sit above the right one. Ranking is not judgement.",[190,254,255],{},"If the archive is your memory, you have outsourced remembering to whoever typed the most searchable sentence.",[208,257,259],{"id":258},"why-does-finding-the-message-not-reconstruct-the-job","Why does finding the message not reconstruct the job?",[190,261,262],{},"Because the first answer was a message, not a fact with an owner.",[190,264,265],{},"Someone asked “what is the cap on this SKU.” Someone answered in a thread. A week later another person asks again, in another channel, because they cannot see the first thread or do not trust it. A third asks the model, which summarises both and offers a blend. The second ask is not stupidity. Asking again can be cheaper than trusting a hit you cannot attribute.",[190,267,268,269,275],{},"Yang and colleagues, in ",[197,270,274],{"href":271,"rel":272},"https://www.nature.com/articles/s41562-021-01196-4",[273],"nofollow","Nature Human Behaviour"," (2022), analysed email, calendar, messages and calls of 61,182 US Microsoft employees. Firm-wide remote work made collaboration networks more static and siloed, with fewer bridging ties. Questions that used to travel through a person sitting between two teams now die in a channel those teams do not share. Search does not rebuild those ties. It ranks the silos.",[190,277,278,279,284],{},"Asana’s ",[197,280,283],{"href":281,"rel":282},"https://www.businesswire.com/news/home/20220405005399/en/Asana-Anatomy-of-Work-Index-2022-Work-About-Work-Hampering-Organizational-Agility",[273],"Anatomy of Work Index"," (2022), from a survey of more than 10,000 knowledge workers, put coordination at 58% of the day. Re-asking is coordination.",[190,286,287],{},"A sidebar that answers instantly does not fix this. It has no owner, and next month it answers differently because the thread grew. Onboarding is a factory for the same loop: a new joiner has no threads, so they ask the living, who answer from memory. The answer drifts. By the third joiner the cap is a folk number.",[190,289,290],{},"When someone leaves, you lose the index in their head: which thread was the real one, which “12” was a joke, who owned the exception. Their messages may stay; the meaning of “we agreed” does not. A thumbs-up from the person who owned the budget is not recoverable as a role once they are a disabled account. Negative knowledge is worse: “we tried 12 on this SKU last year and legal refused” is rarely written. Search will not return a refusal that was only a spoken warning in a huddle.",[208,292,294],{"id":293},"how-do-you-make-work-easier-to-reopen-later","How do you make work easier to reopen later?",[190,296,297],{},"Write a short assertion the company will stand behind, then point chat at it.",[190,299,300],{},"Use an owner-and-date test on anything you call knowledge: can you name the person who owns this sentence and the date it took effect? If not, it is not memory, whatever it is indexed in. If the only copy left with the laptop, it was a conversation that ended.",[190,302,303],{},"A wiki that is a paste of threads is a dump of chat with a nicer URL: no owner, no date that means “in force,” and a page that grows until nobody trusts it. A wiki that is memory is a short set of assertions: the cap, the policy version, the playbook for this job. Someone owns each page. When it changes, the old version remains.",[190,305,306,310],{},[197,307,309],{"href":308},"what-is-an-ai-workstream","What an AI workstream is"," is not a wiki of everything. It is the brief and the artefacts for this outcome, visible to the roles on it. A dump tries to be everyone else’s memory and becomes no one’s. That named container is the workstream.",[190,312,313],{},"Remember what another team will be measured on after you leave: prices, credits, dates, scope, who was allowed to change them, and where the change landed. Do not remember the status ping, the joke, or “can you join at 3.” Short retention is correct for those.",[190,315,316],{},"A practical list for one function, not a programme:",[225,318,319,322,325,328],{},[228,320,321],{},"The exception, with object names the systems use.",[228,323,324],{},"The signer, with a timestamp from the system, not from memory.",[228,326,327],{},"The policy version that was in force that day.",[228,329,330],{},"The outcome in the system of record.",[190,332,333],{},"If you cannot name the owner of an item, keep it out of the wiki and let it expire in chat.",[208,335,337],{"id":336},"what-does-this-look-like-on-a-real-team","What does this look like on a real team?",[190,339,340],{},"A revenue team is asked, twice in two weeks, what the discount cap is on SKU A-440. Search finds three hits: a joke in #social, a draft in a private channel, and last year’s exception for a different customer. Nobody can say which sentence is in force.",[190,342,343],{},"A useful memory for the same question is one line on a page or workstream note: cap, date, owner, link to the rate card. Chat can still debate a new exception. The page is what the second asker opens.",[190,345,346],{},"Offboarding that says “export their Slack” produces a zip with no owner. “Transfer the jobs they signed” produces a roster change. The zip is for counsel. The roster is for Monday.",[190,348,349],{},"More corpus is not automatically more memory. An index over unowned text can raise confidence without raising accuracy: a near-miss from a different customer reads as a fact. A vector store of the archive is still the archive — a neighbour in language, not a fact in force. You have bought fluency about things nobody asserted.",[208,351,353],{"id":352},"how-do-you-start-without-a-new-search-product","How do you start without a new search product?",[190,355,356],{},"Take the question your team asked twice last week. Write the answer in one sentence with an owner and a date. Link it from the thread. That takes longer than pasting the thread, and the extra minute is the cost of memory. The re-ask is the cost of skipping it.",[190,358,359],{},"Then write the refuse as well as the grant, if last year’s “no” is still load-bearing. Yang et al. observed fewer bridging ties under firm-wide remote work; the leaver was often the only bridge. The written refuse is how the next person inherits the warning.",[190,361,362,363,366],{},"Nimbus can hold asserted playbooks next to a ",[197,364,365],{"href":32},"workstream",". You do not need that product to start. You need one fact the company is willing to be held to, sitting somewhere that is not only the index.",{"title":170,"searchDepth":171,"depth":171,"links":368},[369,370,371,372,373],{"id":210,"depth":171,"text":211},{"id":258,"depth":171,"text":259},{"id":293,"depth":171,"text":294},{"id":336,"depth":171,"text":337},{"id":352,"depth":171,"text":353},"2026-08-06","Search finds a message that used your words. Memory is a fact somebody chose to keep — with an owner, a date, and a place that still holds it after people leave. This guide explains why a hit is not a job you can reopen.",{"eyebrow":377,"title":378},"Short answers","Questions about search and memory",[380,383,386],{"question":381,"answer":382},"Can we just index every channel and call that memory?","You can index them. You will get strings people typed, for dates retention still holds, in rooms you can see. You will not get a list of decisions the company stands behind.",{"question":384,"answer":385},"Is a wiki automatically memory?","Only if each assertion has an owner and a date that means in force. A page titled “notes from Slack, March” is the archive with a nicer URL.",{"question":387,"answer":388},"Do we need a new search product to start?","No. Take the question your team asked twice last week, write the answer in one sentence with an owner and a date, and link it from the thread.","/blog/search-is-not-memory",{"title":181,"description":375},"enterprise-problem","blog/search-is-not-memory",[391,394,395,396],"search","memory","wiki","ajpuCChGaBg93Y17VRTcOYP30bsiLmWisy87hOlI7io",{"id":399,"title":400,"archived":164,"authors":401,"badge":403,"body":404,"date":579,"definedTerm":165,"department":165,"description":580,"extension":173,"eyebrow":165,"faqHeader":581,"faqs":583,"footerBand":165,"headline":165,"image":165,"industry":165,"jobType":165,"listed":164,"location":165,"navigation":130,"openRoles":165,"pageLayout":165,"path":593,"relatedHeading":165,"seo":594,"series":391,"sitemap":130,"status":165,"stem":595,"subhead":165,"tags":596,"video":165,"whyJoin":165,"workplaceType":165,"__hash__":600},"content/blog/decisions-made-in-direct-messages.md","Why do decisions end up in direct messages, and what should you copy out?",[402],{"name":184,"to":135},{"label":186},{"type":167,"value":405,"toc":572},[406,409,421,425,428,435,438,441,445,448,451,454,457,465,468,471,485,488,492,495,498,501,515,518,522,525,540,543,546,555,559,562,565],[190,407,408],{},"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.",[190,410,411,412,415,416,420],{},"This guide traces one pricing exception from a DM to an 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 ",[197,413,85],{"href":414},"/problems/"," hub is the wider series; ",[197,417,419],{"href":418},"search-is-not-memory","search is not memory"," is the general case. A DM is the same idea with a smaller room and a worse search.",[208,422,424],{"id":423},"why-do-decisions-end-up-in-direct-messages","Why do decisions end up in direct messages?",[190,426,427],{},"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.",[190,429,430,431,434],{},"Speed is the other reason. Typing “ok go 12” is faster than opening the quote. Asana’s ",[197,432,283],{"href":281,"rel":433},[273]," (2022), a survey of more than 10,000 knowledge workers, found that 58% of the day went to work about work — coordinating, searching, chasing status. Chasing “did we agree 12 or 8” is that 58%, paid by people who were not in the DM.",[190,436,437],{},"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.",[190,439,440],{},"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.",[208,442,444],{"id":443},"what-goes-wrong-when-the-only-yes-is-in-a-dm","What goes wrong when the only yes is in a DM?",[190,446,447],{},"Tuesday, 16:12. A seller and a customer-success manager are in a Slack DM. The customer has asked for 12% 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%.",[190,449,450],{},"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% stacks with the existing rebate.",[190,452,453],{},"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.",[190,455,456],{},"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.",[190,458,459,460,464],{},"Finance never saw it. The sales manager never saw it; exceptions above 10% 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. ",[197,461,463],{"href":462},"collaborative-ai-for-legal-and-compliance-review","collaborative AI for legal and compliance review"," often starts here: one team has a memory, the other has a system, and both are sincere.",[190,466,467],{},"On the first of the month the billing job reads Salesforce. The opportunity still has 8%. The invoice prints 8%. 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.",[190,469,470],{},"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.",[190,472,473,478,479,484],{},[197,474,477],{"href":475,"rel":476},"https://www.law.cornell.edu/rules/frcp/rule_37",[273],"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. ",[197,480,483],{"href":481,"rel":482},"https://www.govinfo.gov/content/pkg/PLAW-107publ204/html/PLAW-107publ204.htm",[273],"Sarbanes-Oxley"," (2002) 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.",[190,486,487],{},"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.",[208,489,491],{"id":490},"how-do-you-keep-private-conversation-without-losing-the-outcome","How do you keep private conversation without losing the outcome?",[190,493,494],{},"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.",[190,496,497],{},"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.",[190,499,500],{},"Practical catches that respect privacy:",[225,502,503,506,509,512],{},[228,504,505],{},"Invoicing rejects a discount that is not on the quote.",[228,507,508],{},"CRM requires a reason code and an approver on overrides above a threshold.",[228,510,511],{},"The job that proposes the exception is visible to finance before the invoice runs.",[228,513,514],{},"Fail-closed on the write: if nobody approves, nothing happens. The field stays at 8 until a signer moves it.",[190,516,517],{},"Sellers can keep DMs. The company can refuse to invoice from them. You cannot police a customer’s WhatsApp. You can refuse to treat it as the quote.",[208,519,521],{"id":520},"what-should-you-copy-out-of-a-dm","What should you copy out of a DM?",[190,523,524],{},"Copy the outcome, not the chat. Four lines are enough:",[526,527,528,531,534,537],"ol",{},[228,529,530],{},"The decision, with object names the systems use (SKU, quote id, currency, percent).",[228,532,533],{},"Who was allowed to make it.",[228,535,536],{},"Who signed, with a timestamp from the system, not from memory.",[228,538,539],{},"Where a stranger would find it in six months.",[190,541,542],{},"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.",[190,544,545],{},"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.",[190,547,548,551,552,554],{},[197,549,550],{"href":418},"Search is not memory"," is why “we can always find the DM” fails: private history, retention sliders, and the next owner’s missing access. ",[197,553,309],{"href":308}," is one named place those four lines can live.",[208,556,558],{"id":557},"how-do-you-start-with-one-recurring-decision","How do you start with one recurring decision?",[190,560,561],{},"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.",[190,563,564],{},"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.",[190,566,567,568,571],{},"If you want the chain in product form, ",[197,569,570],{"href":40},"governance"," is one place to hold who may approve a write. 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.",{"title":170,"searchDepth":171,"depth":171,"links":573},[574,575,576,577,578],{"id":423,"depth":171,"text":424},{"id":443,"depth":171,"text":444},{"id":490,"depth":171,"text":491},{"id":520,"depth":171,"text":521},{"id":557,"depth":171,"text":558},"2026-08-05","A pricing exception typed in a DM never reaches finance, the invoice, or the next owner of the account. This guide explains why private rooms attract yeses, what goes wrong, and how to keep the conversation without losing the outcome.",{"eyebrow":377,"title":582},"Questions about decisions in DMs",[584,587,590],{"question":585,"answer":586},"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.",{"question":588,"answer":589},"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.",{"question":591,"answer":592},"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.","/blog/decisions-made-in-direct-messages",{"title":400,"description":580},"blog/decisions-made-in-direct-messages",[391,597,598,599],"direct-messages","records","invoicing","sX2vSdX4xxI_JtYbFdYd7WheqQL-jjA9XiCrVkTFrOk",{"fold":602,"id":607,"title":608,"archived":164,"authors":165,"badge":165,"body":609,"date":165,"definedTerm":165,"department":165,"description":170,"extension":173,"eyebrow":165,"faqHeader":165,"faqs":165,"footerBand":613,"headline":165,"image":165,"industry":165,"jobType":165,"listed":130,"location":165,"navigation":130,"openRoles":165,"pageLayout":165,"path":617,"relatedHeading":165,"seo":618,"series":165,"sitemap":164,"status":165,"stem":619,"subhead":165,"tags":165,"video":165,"whyJoin":165,"workplaceType":165,"__hash__":620},{"headline":603,"description":604,"primaryLabel":8,"primaryTo":605,"secondaryLabel":606,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Free 7-day trial.","/checkout","Explore the platform","content/shared/cta.md","Site CTAs",{"type":167,"value":610,"toc":611},[],{"title":170,"searchDepth":171,"depth":171,"links":612},[],{"headline":614,"description":615,"primaryLabel":8,"primaryTo":605,"secondaryLabel":616,"secondaryTo":99},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger - free for 7 days.","Talk to our team","/shared/cta",{"title":608,"description":170},"shared/cta","wz4AdRHnaYH021WMdWcHnZvHmkZJNKaNG4XGZfnFBtw",{"enabled":164,"message":622,"linkLabel":93,"linkHref":94,"id":623,"title":624,"archived":164,"authors":165,"badge":165,"body":625,"date":165,"definedTerm":165,"department":165,"description":170,"extension":173,"eyebrow":165,"faqHeader":165,"faqs":165,"footerBand":165,"headline":165,"image":165,"industry":165,"jobType":165,"listed":130,"location":165,"navigation":130,"openRoles":165,"pageLayout":165,"path":629,"relatedHeading":165,"seo":630,"series":165,"sitemap":164,"status":165,"stem":631,"subhead":165,"tags":165,"video":165,"whyJoin":165,"workplaceType":165,"__hash__":632},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":167,"value":626,"toc":627},[],{"title":170,"searchDepth":171,"depth":171,"links":628},[],"/shared/hiring",{"title":624,"description":170},"shared/hiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",1788982427968]