[{"data":1,"prerenderedAt":1204},["ShallowReactive",2],{"site-nav-content":3,"blog:/blog/collaborative-ai-for-customer-support":179,"blog-index-copy":696,"blog:/blog/collaborative-ai-for-customer-support:surround":717,"hiring-banner-content":1173,"site-cta-content":1185},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":163,"title":164,"archived":165,"authors":166,"badge":166,"body":167,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":175,"relatedHeading":166,"seo":176,"series":166,"sitemap":165,"status":166,"stem":177,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":178},{"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,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https://docs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","/careers",{"label":82,"to":83},"System status","/status",{"label":7,"to":85},"/contact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","/glossary",{"label":91,"to":92},"Compare","/compare",{"label":94,"to":95},"Evaluate","/evaluate",{"label":97,"to":98},"Problems","/problems",{"label":100,"to":101},"Use cases","/use-cases",[103,106],{"label":104,"to":105},"Terms of Service","/terms",{"label":107,"to":108},"Privacy Policy","/privacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https://www.linkedin.com/company/gonimbusai/",{"label":114,"href":115},"X","https://x.com/gonimbusai",{"label":117,"href":118},"Instagram","https://www.instagram.com/gonimbus_ai/",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","/compliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","/llms.txt",true,{"text":133,"prompt":134},"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":135,"platforms":137},{" Summarize the highlights from Nimbus's website":136},"https://gonimbus.ai",[138,143,148,153,158],{"name":139,"label":140,"icon":141,"hrefPrefix":142},"chatgpt","ChatGPT","simple-icons:openai","https://chatgpt.com/?prompt=",{"name":144,"label":145,"icon":146,"hrefPrefix":147},"perplexity","Perplexity","mdi:magnify","https://www.perplexity.ai/search/new?q=",{"name":149,"label":150,"icon":151,"hrefPrefix":152},"grok","Grok","simple-icons:x","https://x.com/i/grok?text=",{"name":154,"label":155,"icon":156,"hrefPrefix":157},"claude","Claude","simple-icons:anthropic","https://claude.ai/new?q=",{"name":159,"label":160,"icon":161,"hrefPrefix":162},"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":168,"value":169,"toc":170},"minimark",[],{"title":171,"searchDepth":172,"depth":172,"links":173},"",2,[],"md","/shared/nav",{"title":164,"description":171},"shared/nav","1dD7ahDRl0SQ4hz53-kKo0tEFrGaLuaztZ3PPfp6a9k",{"id":180,"title":181,"archived":165,"authors":182,"badge":185,"body":187,"date":668,"definedTerm":166,"department":166,"description":669,"extension":174,"eyebrow":166,"faqHeader":670,"faqs":673,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":686,"relatedHeading":166,"seo":687,"series":688,"sitemap":131,"status":166,"stem":689,"subhead":166,"tags":690,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":695},"content/blog/collaborative-ai-for-customer-support.md","What is collaborative AI for customer support?",[183],{"name":184,"to":136},"Nimbus Research",{"label":186},"Use case",{"type":168,"value":188,"toc":659},[189,193,210,223,228,231,262,265,277,281,284,299,306,323,327,371,378,382,385,388,408,411,440,443,456,469,533,537,540,547,550,572,584,588,591,594,608,611,622,633,636,640,650,655],[190,191,192],"p",{},"Customer support already has a path for when the playbook runs out. The frontline agent knows the customer, the ticket history, and what was promised in this thread. A specialist knows the product edge case, the known defect, the escalation path. A named person — team lead, billing ops, or a delegate with a spend limit — can issue a credit or a policy exception. Sometimes legal joins when the words might bind the company. The failure mode is a commitment without a signer, and fluency mistaken for resolution.",[190,194,195,196,203,204,209],{},"In February 2024 the Civil Resolution Tribunal of British Columbia held Air Canada to a bereavement fare its chatbot had invented — reported by ",[197,198,202],"a",{"href":199,"rel":200},"https://www.cbc.ca/news/canada/british-columbia/air-canada-chatbot-lawsuit-1.7116416",[201],"nofollow","CBC News",", decision ",[197,205,208],{"href":206,"rel":207},"https://decisions.civilresolutionbc.ca/crt/crtd/en/525448/1/document.do",[201],"Moffatt v. Air Canada",". No CRM write was required. The message was the write. That caution belongs in the first screen of every support AI conversation: the customer-facing sentence is often the system of record for the relationship.",[190,211,212,213,217,218,222],{},"This guide is about one shared exception case — not a project to replace the helpdesk with a bot that closes tickets faster, and not a deflection metric. ",[197,214,216],{"href":215},"what-is-collaborative-ai","What is collaborative AI"," is the definition. ",[197,219,221],{"href":220},"collaborative-ai-and-personal-assistants","Collaborative AI and personal assistants"," is when an agent’s private draft should stay private until there is a case.",[224,225,227],"h2",{"id":226},"what-collaborative-ai-for-support-actually-is","What collaborative AI for support actually is",[190,229,230],{},"Support already has roles before anyone mentions a model. Collaborative AI puts those people on one job with the same ticket view and the same policy.",[232,233,234,243,249,256],"ul",{},[235,236,237,238,242],"li",{},"The ",[239,240,241],"strong",{},"agent"," keeps the customer voice accurate, attaches context, and does not sign credits above their limit.",[235,244,237,245,248],{},[239,246,247],{},"specialist"," proposes product facts and cannot override billing policy without an approver.",[235,250,251,252,255],{},"A ",[239,253,254],{},"named approver"," rejects or signs the exact credit or policy exception — amount, currency, reason code, tax treatment.",[235,257,258,261],{},[239,259,260],{},"Legal or compliance"," joins when the words might bind, and can refuse the send.",[190,263,264],{},"The AI role is named: it may read this case and this knowledge article; it may draft the customer reply and the credit memo; it may not post the refund; it may not state a fare-like rule on the website without a signer class. Attach the approver to the case before the model proposes money.",[190,266,267,268,271,272,276],{},"A ticket closed without the exception recorded is a metric, not a job. Write-back is when AI changes a live system — a billing credit, a subscription change, a CRM field the customer can see. It also includes ",[239,269,270],{},"customer messages that bind"," when the customer could rely on the sentence. Fail-closed means if nobody approves, nothing happens. ",[197,273,275],{"href":274},"what-is-write-back-governance","What is write-back governance"," is the control on that step.",[224,278,280],{"id":279},"why-a-commitment-without-a-signer-is-the-failure","Why a commitment without a signer is the failure",[190,282,283],{},"The usual pattern inside the company is softer than Air Canada and just as familiar. An agent asks a personal assistant to “draft the apology and 15% credit.” The draft is polished. Billing never sees the amount. The customer replies “thanks for the $40 credit” when the draft said 15% of an unclear base. The specialist learns on Friday.",[190,285,286,287,292,293,298],{},"Zendesk’s ",[197,288,291],{"href":289,"rel":290},"https://cxtrends.zendesk.com/",[201],"Customer Experience Trends Report"," tracks rising expectations for personalised support and AI-assisted agents — alongside pressure on first-contact resolution. Speed without a shared case recreates the DM problem: a fluent answer in a private window that the next shift cannot find. McKinsey’s ",[197,294,297],{"href":295,"rel":296},"https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai",[201],"State of AI"," (2025) shows the same gap at the industry level: adoption in customer-facing functions outruns the shared process behind the reply.",[190,300,301,302,305],{},"The common belief is that AI should ",[239,303,304],{},"replace tier-one"," and free humans for hard cases. Replacement without a shared case and a named exception path scales the wrong failure: tidy closure in the tool, messy truth in billing and in the customer’s inbox. Collaborative AI is the opposite pattern — keep the humans on exceptions, automate the listing and drafting inside a room everyone can reopen.",[190,307,308,312,313,317,318,322],{},[197,309,311],{"href":310},"collaborative-ai-for-legal-and-compliance-review","Collaborative AI for legal and compliance review"," is the sibling when the artefact is binding language. ",[197,314,316],{"href":315},"collaborative-ai-for-revenue-operations","Collaborative AI for revenue operations"," is the pattern when the case affects forecast or renewal truth. ",[197,319,321],{"href":320},"decisions-made-in-direct-messages","Decisions made in direct messages"," is the failure this page is trying to stop on the helpdesk.",[224,324,326],{"id":325},"words-you-will-hear","Words you will hear",[232,328,329,335,341,347,353,359,365],{},[235,330,331,334],{},[239,332,333],{},"Exception."," The case the playbook does not finish: a credit, an SLA breach, a policy statement that sounds like a fare.",[235,336,337,340],{},[239,338,339],{},"Named approver."," The identity with a spend limit or a policy-exception grant. “Whoever is on chat” is not a signer.",[235,342,343,346],{},[239,344,345],{},"Payload."," The exact credit or the exact customer sentence, shown before it lands.",[235,348,349,352],{},[239,350,351],{},"Write-back."," A change to billing, CRM, subscription, or a message the customer can rely on.",[235,354,355,358],{},[239,356,357],{},"Fail-closed."," Missing approval means nothing posts and nothing sends.",[235,360,361,364],{},[239,362,363],{},"Deflection."," Closing a ticket without recording the exception. A metric, not a job.",[235,366,367,370],{},[239,368,369],{},"Signer class."," The same bar you would use for an agent email, applied to a website bot.",[190,372,373,377],{},[197,374,376],{"href":375},"what-is-ai-governance","What is AI governance"," is the wider programme. This page is the support subset: one case, one exception, one name on the money or the sentence.",[224,379,381],{"id":380},"how-to-use-ai-on-tickets-without-losing-the-exception-path","How to use AI on tickets without losing the exception path",[190,383,384],{},"Ask the model for a case summary and a proposed payload, not an unsupervised close.",[190,386,387],{},"Put on the job:",[232,389,390,396,402],{},[235,391,237,392,395],{},[239,393,394],{},"ticket or case id",", read-only, with the thread the customer can see.",[235,397,237,398,401],{},[239,399,400],{},"policy or macro version"," that applies — refunds, SLAs, goodwill limits — with a date.",[235,403,237,404,407],{},[239,405,406],{},"billing or subscription view",", read-only, if money moves.",[190,409,410],{},"Then:",[412,413,414,421,428,434,437],"ol",{},[235,415,416,417,420],{},"Generate a ",[239,418,419],{},"draft reply"," that cites those sources, not a private rewrite.",[235,422,423,424,427],{},"If money moves, show the ",[239,425,426],{},"exact credit",": amount, currency, reason code, tax treatment.",[235,429,430,431,433],{},"Assign the ",[239,432,254],{}," on the roster before the write is possible.",[235,435,436],{},"Treat a billing post as write-back with a payload: before and after.",[235,438,439],{},"Keep fail-closed: if nobody approves, nothing posts and the customer message does not send.",[190,441,442],{},"Do not start with unsupervised auto-close for exceptions above your threshold. Do not let the website bot state prices, fares, or cancellation rules without the same signer class you would use for an agent email. Air Canada did not need a CRM API. The sentence was enough.",[190,444,445,446,450,451,455],{},"The harness — the tools, stops, and checks around the model — is what keeps “just refund them” from becoming an unsupervised clerk. ",[197,447,449],{"href":448},"what-is-harness-engineering","What is harness engineering"," is the guide to that environment. ",[197,452,454],{"href":453},"what-is-human-in-the-loop-ai","What is human-in-the-loop AI"," is why a checkbox is not a quote.",[190,457,458,459,463,464,468],{},"For unattended hygiene — duplicate tickets, stale fields, Monday queue scans — that is standing-order work, not this room. See ",[197,460,462],{"href":461},"loops-for-revenue-operations","loops for revenue operations"," when the queue is commercial, and ",[197,465,467],{"href":466},"what-is-loop-engineering","what is loop engineering"," for the compile-and-skip discipline. Exception cases with a signer belong in the collaborative room.",[470,471,475],"pre",{"className":472,"code":473,"language":474,"meta":171,"style":171},"language-mermaid shiki shiki-themes github-light github-dark","flowchart TD\n  ticket[\"Ticket\"] --> sharedCase[\"Shared case\"]\n  policy[\"Policy version\"] --> sharedCase\n  agent[\"Frontline agent\"] --> sharedCase\n  specialist[\"Specialist\"] --> sharedCase\n  model[\"Draft\"] --> sharedCase\n  approver[\"Named approver\"] -->|sign or reject| sharedCase\n  sharedCase --> billing[\"Billing change\"]\n  sharedCase --> customer[\"Customer reply\"]\n","mermaid",[476,477,478,486,491,497,503,509,515,521,527],"code",{"__ignoreMap":171},[479,480,483],"span",{"class":481,"line":482},"line",1,[479,484,485],{},"flowchart TD\n",[479,487,488],{"class":481,"line":172},[479,489,490],{},"  ticket[\"Ticket\"] --> sharedCase[\"Shared case\"]\n",[479,492,494],{"class":481,"line":493},3,[479,495,496],{},"  policy[\"Policy version\"] --> sharedCase\n",[479,498,500],{"class":481,"line":499},4,[479,501,502],{},"  agent[\"Frontline agent\"] --> sharedCase\n",[479,504,506],{"class":481,"line":505},5,[479,507,508],{},"  specialist[\"Specialist\"] --> sharedCase\n",[479,510,512],{"class":481,"line":511},6,[479,513,514],{},"  model[\"Draft\"] --> sharedCase\n",[479,516,518],{"class":481,"line":517},7,[479,519,520],{},"  approver[\"Named approver\"] -->|sign or reject| sharedCase\n",[479,522,524],{"class":481,"line":523},8,[479,525,526],{},"  sharedCase --> billing[\"Billing change\"]\n",[479,528,530],{"class":481,"line":529},9,[479,531,532],{},"  sharedCase --> customer[\"Customer reply\"]\n",[224,534,536],{"id":535},"what-a-shared-support-case-looks-like","What a shared support case looks like",[190,538,539],{},"One case, one exception.",[190,541,542,543,546],{},"The agent attaches context and keeps the customer voice accurate. The specialist proposes product facts. The named approver rejects or signs the ",[239,544,545],{},"exact"," credit or policy exception. Finance or billing ops may appear as guest on high-value cases. After signature, a new customer message that changes the deal is a new proposal. A side-channel “actually make it $50” is a new version with a new sign — not an edit to the closed ticket note.",[190,548,549],{},"The signed outcome contains the customer message if it sent, the credit payload if it posted, the policy version, the approver’s name, and the ticket id. The model’s draft is not the signature.",[190,551,552,556,557,561,562,566,567,571],{},[197,553,555],{"href":554},"rbac-for-enterprise-ai","RBAC for enterprise AI"," keeps a guest from inheriting the billing write token. ",[197,558,560],{"href":559},"multiplayer-ai-and-multi-agent-ai","Multiplayer AI and multi-agent AI"," is why several agents passing tickets to each other is not the same as finance seeing the credit payload. ",[197,563,565],{"href":564},"how-to-evaluate-collaborative-ai","How to evaluate collaborative AI"," is the sheet for the job. ",[197,568,570],{"href":569},"what-is-an-ai-workstream","What an AI workstream is"," is one container shape.",[190,573,574,575,578,579,583],{},"When the case touches renewal or pipeline truth, pull finance or RevOps onto the roster as guest — the same week’s ",[197,576,577],{"href":315},"collaborative AI for revenue operations"," job may need the exception visible before a forecast signs. ",[197,580,582],{"href":581},"collaborative-ai-for-human-resources","Collaborative AI for human resources"," is the pattern when the case is an employee-facing commitment rather than a customer credit.",[224,585,587],{"id":586},"how-to-start-with-one-exception-type","How to start with one exception type",[190,589,590],{},"Pick one recurring exception: goodwill credits above a named amount, SLA credits, subscription pauses, policy statements that sound like fares or cancellation rules.",[190,592,593],{},"Four weeks:",[412,595,596,599,602,605],{},[235,597,598],{},"Read-only ticket plus billing view for that slice.",[235,600,601],{},"A draft reply the model may not send alone.",[235,603,604],{},"A named approver with a real spend limit.",[235,606,607],{},"No production billing writes until the first rejection is stored.",[190,609,610],{},"Count how many credits were still decided in side chats. If that number does not fall, you automated deflection rather than the case. Keep a short note: who was on the roster, how many credits were proposed and rejected, whether billing matched the signed payload, whether a customer-facing sentence left without a signer class.",[190,612,613,614,617,618,621],{},"Website and support bots need the same split. A bot may detect that a customer asked about a fare-like rule. The ",[239,615,616],{},"send"," of that language still routes to a person with a signer class, or stays draft-only. ",[197,619,208],{"href":206,"rel":620},[201]," is the reminder that the message can be the write.",[190,623,624,625,628,629,632],{},"For high-volume ",[239,626,627],{},"non-exception"," work — categorisation, duplicate detection, suggested macros — a standing-order loop on the queue may be the right unattended layer. Keep exceptions in the collaborative case. ",[197,630,631],{"href":466},"Loop engineering"," is the compile-and-skip discipline; it is not a substitute for the approver on money.",[190,634,635],{},"Support AI is not measured only by tickets closed. It is measured by whether the exception that left the building had a name on it — and whether the customer can rely on a sentence that nobody signed.",[224,637,639],{"id":638},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[190,641,642,643,646,647,649],{},"Nimbus ",[197,644,645],{"href":32},"workstreams"," hold the shared support case next to the roster: ticket view, policy version, proposed credit, named approver. ",[197,648,39],{"href":40}," is where customer-facing claims and billing writes have to live as fail-closed behaviour. You can start with a shared folder and a written billing stop if that is what you have.",[190,651,652,654],{},[197,653,565],{"href":564}," is still the sheet for the job. The product is useful only if last Friday’s credit can be reconstructed without asking the agent who drafted the apology.",[656,657,658],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":171,"searchDepth":172,"depth":172,"links":660},[661,662,663,664,665,666,667],{"id":226,"depth":172,"text":227},{"id":279,"depth":172,"text":280},{"id":325,"depth":172,"text":326},{"id":380,"depth":172,"text":381},{"id":535,"depth":172,"text":536},{"id":586,"depth":172,"text":587},{"id":638,"depth":172,"text":639},"2026-09-12","Collaborative AI for support is one shared case — agent, specialist, and a named person who can issue a credit or policy exception — not a chatbot that replaces the helpdesk. A guide to exceptions, not deflection.",{"eyebrow":671,"title":672},"Common questions","Cases, credits, and a named exception",[674,677,680,683],{"question":675,"answer":676},"Should AI resolve tickets without a human?","It may draft and may suggest. Resolution that changes billing, policy, or a commitment still needs a named person who can issue the exception — with the exact payload visible before it lands. A ticket closed without the exception recorded is a metric, not a job. Fail-closed means if nobody approves, nothing posts and the customer message does not send. Speed without a shared case recreates the side-chat problem: a fluent answer in a private window that the next shift cannot find. Keep the humans on exceptions. Automate listing and drafting inside a room everyone can reopen.",{"question":678,"answer":679},"Is a chatbot on the website the same as support collaborative AI?","Only if the bots sentences are governed like writes. Air Canada was held to chatbot text with no CRM change. Treat customer-facing claims as payloads with a signer class, or keep the bot draft-only. A website sentence about fares, credits, or cancellation rules is often the system of record for the relationship. Collaborative AI for support is the shared case behind exceptions, not a project to replace the helpdesk with a bot that closes tickets faster. If the customer could rely on the sentence, treat it as a write even when no billing API fired.",{"question":681,"answer":682},"Where should we start?","Start with one exception type: credits above a threshold, SLA breaches, or fare-like policy statements. Put a read-only ticket view and a read-only billing view on the case. Name the approver with a real spend limit. Do not enable production billing writes until the first rejection is stored. Count how many credits were still decided in side chats. If that number does not fall, you automated deflection rather than the case.",{"question":684,"answer":685},"Does this replace tier-one support?","No. Replacement without a shared case and a named exception path scales the wrong failure: tidy closure in the tool, messy truth in billing and in the customers inbox. Collaborative AI keeps humans on exceptions and uses the model to draft inside a room the next shift can reopen. High-volume non-exception work — categorisation, duplicate detection, suggested macros — can sit on a standing-order loop. Keep money, policy, and commitments on the collaborative case with a named signer.","/blog/collaborative-ai-for-customer-support",{"title":181,"description":669},"collaborative-ai","blog/collaborative-ai-for-customer-support",[688,691,692,693,694],"customer-support","helpdesk","exceptions","write-back","EW3KHdyTpOqlvwMq_95TC8IThMjAUBfXvihjuDvgNSw",{"hero":697,"id":699,"title":700,"archived":165,"authors":166,"badge":166,"body":701,"date":166,"definedTerm":166,"department":166,"description":705,"extension":174,"eyebrow":706,"faqHeader":166,"faqs":166,"footerBand":707,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":60,"relatedHeading":713,"seo":714,"series":166,"sitemap":131,"status":166,"stem":715,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":716},{"filename":698},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content/blog/index.md","Exploring the future of intelligence.",{"type":168,"value":702,"toc":703},[],{"title":171,"searchDepth":172,"depth":172,"links":704},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":708,"description":709,"primaryLabel":710,"primaryTo":711,"secondaryLabel":712,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","/newsletter","Explore the platform","More research",{"title":700,"description":705},"blog/index","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[718,166],{"id":719,"title":720,"archived":165,"authors":721,"badge":723,"body":724,"date":668,"definedTerm":166,"department":166,"description":1150,"extension":174,"eyebrow":166,"faqHeader":1151,"faqs":1153,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":165,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1165,"relatedHeading":166,"seo":1166,"series":688,"sitemap":131,"status":166,"stem":1167,"subhead":166,"tags":1168,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1172},"content/blog/collaborative-ai-for-human-resources.md","What is collaborative AI for human resources?",[722],{"name":184,"to":136},{"label":186},{"type":168,"value":725,"toc":1139},[726,729,738,746,750,753,778,781,796,802,806,809,822,831,839,841,882,887,891,894,897,914,917,924,928,936,942,955,958,962,965,1001,1004,1015,1055,1059,1062,1065,1068,1078,1089,1093,1096,1099,1116,1119,1122,1124,1132,1137],[190,727,728],{},"Human resources already runs people decisions through a committee, whether anyone calls it that. The manager knows the operational fact — the project slip, the customer complaint, the pattern of absence. The HR business partner knows which policy version applies, what precedent looks like, and which step in the process is next. Legal joins when the words might bind the company. A named signer — often HR, sometimes a delegated director — is the person who can refuse the outcome. The failure mode is a decision with nobody’s name on it, and personal data sitting in a room that was never scoped.",[190,730,731,732,737],{},"A manager asks a personal assistant to “draft the PIP.” The draft is confident. It cites no policy section. HR learns about it when the employee replies. Alternatively, HR and the manager agree in a side channel, and the only artefact is a paraphrase in email. Six months later someone asks which version of the leave policy applied. The folder has three PDFs with similar names. ",[197,733,736],{"href":734,"rel":735},"https://www.shrm.org/topics-tools/employment-law",[201],"SHRM’s employment law resources"," are a reminder that the paperwork is not decorative. Decisions about people carry discrimination, retaliation, and documentation duties that a fluent paragraph does not satisfy.",[190,739,740,741,217,743,745],{},"This guide is about one shared people decision — a leave exception, an offer band, a conduct step — not a claim that AI should replace your employee relations team, and not a path to auto-firing. ",[197,742,216],{"href":215},[197,744,221],{"href":220}," is when a manager’s private draft should stay private until there is a job.",[224,747,749],{"id":748},"what-collaborative-ai-for-hr-actually-is","What collaborative AI for HR actually is",[190,751,752],{},"People work already has roles before anyone mentions a model. Collaborative AI keeps those duties on one job instead of collapsing them into one chat.",[232,754,755,761,767,772],{},[235,756,237,757,760],{},[239,758,759],{},"manager"," attaches operational context they can stand behind, and can reject claims they cannot.",[235,762,237,763,766],{},[239,764,765],{},"HR business partner"," attaches the policy version in force, proposes language, and usually remains the signer for HRIS writes even when the manager opened the job.",[235,768,769,771],{},[239,770,64],{}," joins when the draft might bind — settlement language, regulatory wording, cross-border transfer text — and can refuse the send without sitting in every leave request.",[235,773,251,774,777],{},[239,775,776],{},"named signer"," is a person, not “HR team” and not a shared mailbox.",[190,779,780],{},"The AI role is narrow: read the attached policy and the employee facts you chose to put on the job; draft the exception memo or the letter language; do not change the HRIS; do not send mail to the employee; do not recommend termination as an unattended conclusion. Fluency is a draft. Employment is a signed outcome.",[190,782,783,784,789,790,795],{},"When the job holds personal data — and almost every HR job does — ",[197,785,788],{"href":786,"rel":787},"https://eur-lex.europa.eu/eli/reg/2016/679/oj",[201],"GDPR"," still applies to purpose, minimisation, and access. The ",[197,791,794],{"href":792,"rel":793},"https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/",[201],"UK ICO’s employment guidance"," is explicit that workers’ data in automated or semi-automated processes needs a lawful basis and a trail. A shared job is processing. Scope what you attach. Name who may see it.",[190,797,798,799,801],{},"Write-back is when AI changes a live system — including an HRIS status, a payroll code, or an email that commits the company. The payload is the exact field change or the exact message. Fail-closed means if nobody approves, nothing happens. A prompt that says “don’t fire anyone” is not that control. ",[197,800,275],{"href":274}," is the same checklist on a different object.",[224,803,805],{"id":804},"why-the-unsigned-people-decision-is-the-failure","Why the unsigned people decision is the failure",[190,807,808],{},"The common belief is that HRIS permissions protect people decisions. Permissions protect fields. They do not automatically produce a reconstructable decision: who saw which policy, who proposed the exception, who signed, what was sent. If you cannot reconstruct, you cannot defend — in an employment tribunal, in an internal audit, or in a simple “why did we treat these two cases differently?” conversation.",[190,810,811,812,815,816,821],{},"McKinsey’s ",[197,813,297],{"href":295,"rel":814},[201]," (2025) reports broad adoption of AI in functions including HR, while most organisations are still piloting governance. Adoption outruns the shared room. That gap is where “the model said” becomes the record. Yang and colleagues, writing in ",[197,817,820],{"href":818,"rel":819},"https://www.nature.com/articles/s41562-021-01196-4",[201],"Nature Human Behaviour"," (2022), found that firm-wide remote work made collaboration networks more static and siloed. People decisions already fight that pull. AI that lives only in a manager’s private thread can make the silo worse: each person has a fluent answer, and nobody has the same file.",[190,823,824,825,830],{},"This is not about auto-firing. Termination and serious discipline are among the outcomes that must never be an unattended model conclusion. The ",[197,826,829],{"href":827,"rel":828},"https://www.eeoc.gov/eeoc-disability-related-resources/artificial-intelligence-and-ada",[201],"U.S. Equal Employment Opportunity Commission"," has already warned that software, algorithms, and AI used to assess applicants and employees can screen people out in ways that violate the ADA if accommodations and human review are missing. A collaborative job is the opposite pattern: slow the path enough that a named HR or legal signer sees the exact language before it lands in a system or in an inbox.",[190,832,833,835,836,838],{},[197,834,311],{"href":310}," is the sibling when the artefact is a clause or a customer-facing sentence. ",[197,837,321],{"href":320}," is the failure this page is trying to stop inside HR.",[224,840,326],{"id":325},[232,842,843,849,855,861,866,870,876],{},[235,844,845,848],{},[239,846,847],{},"Policy version."," The PDF or wiki page with a date that the team agrees is live. “The leave policy” is not a version.",[235,850,851,854],{},[239,852,853],{},"Named signer."," The identity that can refuse the outcome. Shared mailboxes destroy this.",[235,856,857,860],{},[239,858,859],{},"Facts on the job."," The minimum employee information needed for this decision — not the entire personnel file.",[235,862,863,865],{},[239,864,351],{}," A change to a live system, including an employee-facing message that commits the company.",[235,867,868,358],{},[239,869,357],{},[235,871,872,875],{},[239,873,874],{},"Purpose and minimisation."," GDPR vocabulary for why you attached those facts and why you did not attach more.",[235,877,878,881],{},[239,879,880],{},"Reconstruction."," An independent reader can open the signed outcome and explain it without the authors.",[190,883,884,886],{},[197,885,376],{"href":375}," is the wider programme. This page is the people-decision subset: one job, one policy version, one signer.",[224,888,890],{"id":889},"what-the-model-may-do-and-must-not","What the model may do — and must not",[190,892,893],{},"The model may draft. It may point at sources you attached. It may list questions the manager still needs to answer. It may propose letter language next to the policy section it claims to follow.",[190,895,896],{},"The model must not:",[232,898,899,902,905,908,911],{},[235,900,901],{},"Change an HRIS status, compensation field, termination code, or access removal on its own.",[235,903,904],{},"Send mail to the employee.",[235,906,907],{},"Recommend termination or serious discipline as an unattended conclusion.",[235,909,910],{},"Pull the whole employee file “for context.”",[235,912,913],{},"Treat a manager’s confirmation click as an HR signature.",[190,915,916],{},"Name the HRIS changes the model will never post on its own. The model may draft those as a payload. A named HR or system delegate signs. If your vendor cannot show a stored rejection of a proposed status change, you have a demo that has not failed yet. A confirmation box the manager clicks through is not the same as an HR signature.",[190,918,919,920,450,922,455],{},"The harness — the tools, stops, and checks around the model — is how draft-and-sign stays in place when the case is urgent. ",[197,921,449],{"href":448},[197,923,454],{"href":453},[224,925,927],{"id":926},"shrm-ico-and-gdpr-the-paperwork-is-not-decorative","SHRM, ICO, and GDPR — the paperwork is not decorative",[190,929,930,931,935],{},"Employment law does not pause because a draft was generated. ",[197,932,934],{"href":734,"rel":933},[201],"SHRM"," collects the practical duties: documentation, consistency, retaliation risk, and the difference between a coaching note and a formal step. If two employees in similar facts get different letters because one manager had a better assistant, you have a discrimination problem wearing a productivity story.",[190,937,938,941],{},[197,939,788],{"href":786,"rel":940},[201]," Article 5 still wants purpose, minimisation, accuracy, and storage limitation. Article 22 still restricts decisions based solely on automated processing that produce legal or similarly significant effects — and employment outcomes sit in that neighbourhood even when a human later clicks confirm. You do not need to litigate every article to need a reconstructable log. You do need to know that a shared job is processing, that a retrieval index of personnel files is still processing, and that “the model needed context” is not a lawful basis.",[190,943,237,944,948,949,954],{},[197,945,947],{"href":792,"rel":946},[201],"UK ICO employment guidance"," is written for organisations that already hold workers’ data. It asks for a lawful basis, for access that matches the purpose, and for a trail when processing is automated or semi-automated. The ",[197,950,953],{"href":951,"rel":952},"https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/",[201],"ICO’s AI guidance"," adds the same instinct for systems that infer or rank people. Attach the performance note you need for this leave exception. Do not attach five years of Slack because it was easy.",[190,956,957],{},"Retention on the signed outcome should match how long you must explain the decision — not how long chat keeps threads. A later rewrite is a new version with a new sign. A later prompt that “updates” the outcome because someone remembered a detail is not an edit. It is a new proposal.",[224,959,961],{"id":960},"how-to-run-one-people-decision-with-ai","How to run one people decision with AI",[190,963,964],{},"Attach the policy version. Cite it. Sign the outcome people will act on.",[412,966,967,974,981,988,991,998],{},[235,968,969,970,973],{},"Put the ",[239,971,972],{},"policy PDF or wiki page with a date"," on the job. Agree which version is live.",[235,975,976,977,980],{},"Attach only the ",[239,978,979],{},"facts needed for this decision"," — not the entire personnel file.",[235,982,983,984,987],{},"Let the model draft a memo that ",[239,985,986],{},"points at those sources",", not at a private rewrite.",[235,989,990],{},"Invite the manager to reject operational claims they cannot stand behind.",[235,992,993,994,997],{},"Name the ",[239,995,996],{},"HR signer"," before any HRIS write or employee message is possible.",[235,999,1000],{},"File the signed outcome on the job. A later rewrite is a new version with a new sign.",[190,1002,1003],{},"Do this for one decision type you already escalate: leave above the grid, offer outside the band, remote work in a restricted country, a conduct step that needs employee-relations eyes. Do not start with termination. Do not start with a bulk “clean up performance ratings” job.",[190,1005,1006,1007,1011,1012,1014],{},"After signature, a new fact in a side channel is a new proposal. ",[197,1008,1010],{"href":1009},"search-is-not-memory","Search is not memory"," is why “search Teams for the PIP thread” is not a file. ",[197,1013,555],{"href":554}," is why the intern must not inherit an HRIS post when they join as a guest.",[470,1016,1018],{"className":472,"code":1017,"language":474,"meta":171,"style":171},"flowchart LR\n  manager[\"Manager facts\"] --> job[\"Shared HR job\"]\n  policy[\"Policy version\"] --> job\n  model[\"Draft\"] --> job\n  hrbp[\"HR business partner\"] -->|approve or reject| job\n  legal[\"Legal, if needed\"] --> job\n  job -->|signed| hris[\"HR system write\"]\n",[476,1019,1020,1025,1030,1035,1040,1045,1050],{"__ignoreMap":171},[479,1021,1022],{"class":481,"line":482},[479,1023,1024],{},"flowchart LR\n",[479,1026,1027],{"class":481,"line":172},[479,1028,1029],{},"  manager[\"Manager facts\"] --> job[\"Shared HR job\"]\n",[479,1031,1032],{"class":481,"line":493},[479,1033,1034],{},"  policy[\"Policy version\"] --> job\n",[479,1036,1037],{"class":481,"line":499},[479,1038,1039],{},"  model[\"Draft\"] --> job\n",[479,1041,1042],{"class":481,"line":505},[479,1043,1044],{},"  hrbp[\"HR business partner\"] -->|approve or reject| job\n",[479,1046,1047],{"class":481,"line":511},[479,1048,1049],{},"  legal[\"Legal, if needed\"] --> job\n",[479,1051,1052],{"class":481,"line":517},[479,1053,1054],{},"  job -->|signed| hris[\"HR system write\"]\n",[224,1056,1058],{"id":1057},"what-a-shared-hr-job-looks-like","What a shared HR job looks like",[190,1060,1061],{},"Manager, HRBP, optional legal, and sometimes an audit guest on one roster.",[190,1063,1064],{},"The manager sees the same facts everyone else is using. They do not sign policy exceptions unless they are also the named delegate. HR attaches the policy, proposes language, and remains the signer for HRIS writes. Legal joins when the draft might bind, and can refuse the send. Guests are common: a department head, an ER specialist in another region. If the product cannot invite a guest without giving them the write token, you have the wrong room.",[190,1066,1067],{},"The signed outcome contains the decision, the policy version in force, the date, the named signer, and the facts that were on the job — not a model paraphrase of facts that lived only in chat. The narrative the model drafted is support, not signature.",[190,1069,1070,1072,1073,1075,1076,571],{},[197,1071,560],{"href":559}," matters here: several people in one session is not the same as a job that still exists on Monday. ",[197,1074,565],{"href":564}," is the sheet for that job. ",[197,1077,570],{"href":569},[190,1079,1080,1081,1085,1086,1088],{},"For unattended repetition — the Monday headcount extract that nobody changed — that is standing-order work, not this room. See ",[197,1082,1084],{"href":1083},"loops-for-finance-and-planning","loops for finance and planning"," when the extract is payroll or planning, and ",[197,1087,467],{"href":466}," for the compile-and-skip discipline. People decisions with a signer belong in the collaborative room first.",[224,1090,1092],{"id":1091},"how-to-start-with-one-decision-type","How to start with one decision type",[190,1094,1095],{},"Pick one recurring exception your team already escalates.",[190,1097,1098],{},"This cycle:",[412,1100,1101,1104,1107,1110,1113],{},[235,1102,1103],{},"Name the artefact: the memo, the letter, the HRIS change class that must not auto-post.",[235,1105,1106],{},"Attach the policy version the team already cites — with a date.",[235,1108,1109],{},"Add the manager, HRBP, and the signer who will live with the outcome.",[235,1111,1112],{},"Keep the HRIS read-only until you have a stored rejection: the first no is the control.",[235,1114,1115],{},"After the cycle, ask an independent reader to reconstruct the signed decision without the authors.",[190,1117,1118],{},"Count how many people decisions still happened in side chats. If that number does not fall, you automated a draft rather than the decision. Keep a short note: who was on the roster, which policy version was attached, whether the HRIS matched the signed payload, whether anyone rejected.",[190,1120,1121],{},"The exposure in HR is not only the HRIS API. It is that a people decision becomes operational truth with nobody’s name on it, and the model made producing those drafts easy. Put the signature on the artefact people and systems will act on — and keep termination and discipline off the unattended path entirely.",[224,1123,639],{"id":638},[190,1125,642,1126,1128,1129,1131],{},[197,1127,645],{"href":32}," are one container for the shared HR job: policy version, scoped facts, roster, and a named signer before any HRIS write. ",[197,1130,39],{"href":40}," is where fail-closed write-back has to live as behaviour, not as a prompt. You can start with a matter folder and a written stop if that is what you have.",[190,1133,1134,1136],{},[197,1135,565],{"href":564}," is still the sheet for the job. The product is useful only if a later reader can reconstruct the signed people decision without asking the authors.",[656,1138,658],{},{"title":171,"searchDepth":172,"depth":172,"links":1140},[1141,1142,1143,1144,1145,1146,1147,1148,1149],{"id":748,"depth":172,"text":749},{"id":804,"depth":172,"text":805},{"id":325,"depth":172,"text":326},{"id":889,"depth":172,"text":890},{"id":926,"depth":172,"text":927},{"id":960,"depth":172,"text":961},{"id":1057,"depth":172,"text":1058},{"id":1091,"depth":172,"text":1092},{"id":638,"depth":172,"text":639},"Collaborative AI for HR is one shared people decision — a policy version, manager and HRBP on the roster, a named signer — not a chatbot that decides someone’s employment. A guide to one decision, not auto-firing.",{"eyebrow":671,"title":1152},"Policy, people, and a named signer",[1154,1157,1160,1162],{"question":1155,"answer":1156},"Can the model recommend termination if a manager clicks confirm?","No. Employment outcomes still need a named HR or legal signer, the policy version in force, and a record a later reader can reconstruct. A fluent recommendation is not a decision, even when a confirmation box is clicked. Termination and serious discipline are among the outcomes that must never be an unattended model conclusion. The collaborative pattern is the opposite of auto-firing: slow the path enough that a named person sees the exact language before it lands in a system or in an inbox. A stored rejection of a proposed status change is the control. A prompt that says do not fire anyone is etiquette, not that control.",{"question":1158,"answer":1159},"Does GDPR apply if the job only holds a performance note?","If the note identifies a person, yes. Personal data in a shared job still needs a purpose, access control, and retention that match how long you must explain the decision. The UK ICO employment guidance is explicit that workers data in automated or semi-automated processes needs a lawful basis and a trail. Scope what you attach. Name who may see it. Do not dump the whole employee file into a retrieval index so the model has context. A later reader should be able to see why those facts were on the job, not reconstruct a private chat.",{"question":681,"answer":1161},"Start with one decision type you already run through a committee: a policy exception, a leave approval above a threshold, or a job-offer band. Attach the policy version with a date. Invite the manager, the HR business partner, and the named signer. Keep the HRIS read-only until someone signs the exact payload. After the first cycle, ask an independent reader to reconstruct the signed decision without the authors. If they cannot, you automated a draft, not a people process.",{"question":1163,"answer":1164},"Is a manager's personal assistant drafting a PIP the same as collaborative HR?","No. A personal assistant helps one person write. Collaborative AI for HR is the shared job where the policy version, the facts you chose to attach, and the named signer live together. The private draft can stay private until there is a job. Once language might reach the employee or change the HRIS, it belongs on the shared job with a signer who can refuse. Fluency in a private window is not a people decision.","/blog/collaborative-ai-for-human-resources",{"title":720,"description":1150},"blog/collaborative-ai-for-human-resources",[688,1169,1170,1171,788],"human-resources","HR","policy","BpOEcg9ziLA6hJ4VMY9Ld_eYIx0b5kCx-zSIDoWcbjE",{"enabled":165,"message":1174,"linkLabel":79,"linkHref":80,"id":1175,"title":1176,"archived":165,"authors":166,"badge":166,"body":1177,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":166,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1181,"relatedHeading":166,"seo":1182,"series":166,"sitemap":165,"status":166,"stem":1183,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1184},"We're hiring! Join the team building the Sentient Enterprise.","content/shared/hiring.md","Hiring banner",{"type":168,"value":1178,"toc":1179},[],{"title":171,"searchDepth":172,"depth":172,"links":1180},[],"/shared/hiring",{"title":1176,"description":171},"shared/hiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"fold":1186,"id":1190,"title":1191,"archived":165,"authors":166,"badge":166,"body":1192,"date":166,"definedTerm":166,"department":166,"description":171,"extension":174,"eyebrow":166,"faqHeader":166,"faqs":166,"footerBand":1196,"headline":166,"image":166,"industry":166,"jobType":166,"listed":131,"location":166,"navigation":131,"openRoles":166,"pageLayout":166,"path":1200,"relatedHeading":166,"seo":1201,"series":166,"sitemap":165,"status":166,"stem":1202,"subhead":166,"tags":166,"video":166,"whyJoin":166,"workplaceType":166,"__hash__":1203},{"headline":1187,"description":1188,"primaryLabel":8,"primaryTo":1189,"secondaryLabel":712,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed agent swarms, 2,000+ integrations, and a knowledge graph that stays inside your walls. Start on Free.","/signup?plan=free","content/shared/cta.md","Site CTAs",{"type":168,"value":1193,"toc":1194},[],{"title":171,"searchDepth":172,"depth":172,"links":1195},[],{"headline":1197,"description":1198,"primaryLabel":8,"primaryTo":1189,"secondaryLabel":1199,"secondaryTo":85},"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.","Talk to our team","/shared/cta",{"title":1191,"description":171},"shared/cta","PS2VPJsszmUpMBZT6nEp8cWXCdeiN6zDRl-p8d0uY2k",1789797894568]