Chat Is Disappearing Into the Work Surface — and Taking the Downtime With It

Three things happened in the same five-day window that, read together, describe where chat interfaces are actually headed. Salesforce and Anthropic put an entire CRM inside Claude. Google put Gemini inside the app where work conversations already happen. And OpenAI's own chat product went down twice, taking a growing amount of other people's workflows with it. The pattern isn't "AI gets smarter," it's "AI stops being a place you go and becomes a layer you depend on" — with all the upside and fragility that implies.

1. Claude Moves Into the CRM, Not the Other Way Around

On August 26, Salesforce and Anthropic announced Claudeforce: Salesforce's CRM data, workflows, and 37 prebuilt sales skills — meeting prep, deal-health reviews, pipeline analysis — running directly inside Claude, so a seller can query, update, and act on live CRM records without opening Salesforce at all. It's available to pilot customers now, with open beta planned for September. The direction is the notable part. Past integrations bolted a chat assistant onto an existing app; this one moves the CRM's actions into the chat surface and lets Salesforce's own product become optional. Claude is also now the default reasoning model behind Agentforce Vibes and Agentforce Coworker, and — thanks to a run through Amazon Bedrock — sits inside Salesforce's own Trust Boundary, so the data residency argument that used to block this kind of integration is now Salesforce's own selling point rather than an objection.

2. Gemini Becomes Google Chat's Command Line

The same day, Google began rolling out Ask Gemini in Chat: a unified command, reachable with Ctrl/Cmd+G, that searches Gmail, Drive, and Calendar, drafts updates, schedules meetings, and organizes ongoing work into revisitable sessions — all without leaving the conversation thread where a team was already talking. It's a smaller architectural move than Claudeforce but the same instinct: don't ask people to open a new tool, put the assistant inside the tool that already has their attention. Promotional usage limits run through October 1, after which normal caps apply, which is Google's usual signal that it expects this to become a habit worth metering.

// Two products, same shape: the assistant reads from and writes to
// systems of record it doesn't own, inside a surface it doesn't own either.
async function handleRequest(intent: WorkIntent, context: EmbeddedSurface) {
  const records = await context.host.query(intent.targetSystem, intent.filter);
  const action = await assistant.plan(intent, records);
  return context.host.commit(action); // success now depends on two uptimes, not one
}

3. Then ChatGPT Work Mode Went Down Twice

On August 27, OpenAI's own Workspace Agents and ChatGPT Work on web and mobile saw elevated error rates for several hours before recovering. Four days later, on August 31, it happened again: Work mode became unavailable for a share of paying Plus subscribers starting around 11 AM ET, with Downdetector logging north of 10,000 reports before service stabilized. OpenAI's status updates described the symptoms — elevated latency, failed requests — without disclosing a root cause either time. Neither incident was catastrophic by outage standards, and both resolved the same day. But Work mode is precisely the product built to sit inside a team's daily workflow the way Claudeforce and Ask Gemini in Chat are designed to — and it went down twice in the same week those two competitors were making the case that chat belongs inside your other tools.

What This Means for Builders

The throughline across all three stories is that "chatbot" is quietly becoming the wrong mental model. Claudeforce and Ask Gemini in Chat aren't chat products with better answers, they're integration layers that read from and write to systems of record — a CRM, a shared drive, a calendar — that the AI vendor doesn't own and can't fully guarantee. That's a stronger product than a standalone assistant, and it's also a new failure mode: when the assistant goes down, it's no longer just "the chatbot is unavailable," it's "the CRM update didn't happen" or "the meeting didn't get rescheduled." ChatGPT's back-to-back Work mode outages are a preview of exactly that blast radius, from the vendor furthest along in making chat a daily dependency. If you're building on any of these integrations, the question worth asking isn't just "what can the assistant do inside my tool," it's "what happens to my workflow, silently, for the hours it can't."

Suggested visuals: a simple before/after diagram showing a CRM or Workspace app with the chat assistant as a bolt-on panel (old model) versus the assistant as the primary interface with the app's actions as callable skills underneath (new model); and a timeline strip marking the August 26 Claudeforce/Ask Gemini launches against the August 27 and August 31 ChatGPT Work outages, to make the one-week compression of the trend visible at a glance.

— Maya