Coworker vs Moveworks (2026)

About thirty five connectors are named on the platform and agents pages, out of a stated 50+ OAuth connectors listed in a directory at /connectors.

On the platform page they cover CRM (Salesforce, HubSpot), communications and meetings (Slack, Gmail, Zoom, Google Meet, Google Calendar, Microsoft 365), docs and project work (Google Drive, Google Sheets, Notion, Confluence, Jira, Linear, Asana, Figma), engineering (GitHub, Datadog, PagerDuty, VS Code), data (Snowflake, BigQuery, Amplitude), payments (Stripe), the browser (Chrome) and the systems of record for IT service management, HR and finance (ServiceNow, Workday, ADP, SAP, NetSuite).

The agents page adds Gong for sales, Zendesk and Intercom for support, and Microsoft Teams. Every connector reads and writes, so agents pull data and push updates across CRM, comms, support, docs, code and data, updating CRM records, creating tickets, sending follow-ups and drafting reports, and the published run drafts into Gmail, updates Salesforce and posts to Slack.

Agents inherit the permissions already in place, with no new logins and no new SSO maps, so there is no parallel access model to drift. Chrome and VS Code appear in the OAuth connector list as ingestion paths feeding the graph, not as interface control.

Sourcecoworker.ai/platform integrations section and /agents connector listread 2026-09-12

Hundreds of named enterprise systems are connected under one layer, across seven classes, and the Assistant takes action in them, from resetting access to updating CRM records. Service desk and ITSM tools include ServiceNow, Jira, Freshservice, Ivanti Service Desk, BMC Helix Digital Workplace, ManageEngine and Cherwell. HR and finance cover Workday, Coupa, SAP Ariba, SAP Fieldglass and Oracle, and Salesforce covers CRM.

Identity and access providers include Ping Identity, Duo and BeyondTrust. Content and collaboration tools are Box, Confluence, Quip, Google Drive, LumApps, Igloo, Interact, Axero and Brightspot. Mail, calendar and chat cover Microsoft Outlook, Exchange Online, Gmail, Google Calendar, Google Chat and 8x8, and knowledge and data sources include Databricks, Upland RightAnswers, ComAround and BrainStorm QuickHelp, with DocuSign for signatures.

The Assistant is linked to thousands of action plugins and resolves requests end to end, resetting access and provisioning tools for IT, updating CRM data for sales, and automating expenses, purchase requests and approvals for finance. Those are authenticated writes into systems Moveworks does not own, and the Reasoning Engine chooses each tool call at run time rather than having it wired in advance.

Sourcemoveworks.com/us/en/platform/ai-assistant and /platform/integrations; moveworks.com/us/en/platform/integrationsread 2026-09-12

The Agent Builder is the authoring surface, where customers create custom agents in minutes by defining what they do, which tools they use and when they run, with no code required, and set triggers, approval gates and notification preferences through a visual interface. Agent sequences span several steps and systems, and they branch.

In the account agent's published run, it drafted outreach for six accounts through Salesforce and Gmail, escalated one strategic account to an AE through Slack, and posted an expansion summary to Slack, so one of the six accounts went to a person based on the state of the case. The Incident Orchestrator routes incidents, enforces escalation timers and tracks resolution, which means making a routing decision, holding a timer across a gap the agent does not control, and following an incident through to resolution.

State persists across runs, agents run 24/7 in the background without anyone stepping in, and Coworker describes orchestrating several agents from a single control plane. A workflow involves the agent, the approver at a gate, the AE an account escalates to, and the connected systems each step reads and writes. Agents carry work through to the end, updating the CRM, creating tickets, sending follow-ups and drafting reports. Coworker does not describe retry, failure handling or what an agent does when a step fails.

Sourcecoworker.ai/agents capabilities, agent examples and FAQ, with /platformread 2026-09-12

The Reasoning Engine plans each request at run time, breaking it into steps and choosing the tools that carry them out across enterprise systems. It is an agentic AI system that orchestrates enterprise-ready LLMs and built-in tools for AI agents.

It identifies the employee's overall goal, works out the steps needed and breaks complex issues into smaller parts, then selects the tools for each, automating processes with many steps under strict security protocols and real time governance. Moveworks describes this as automation across the enterprise that plans, executes and adapts as it goes, and the Assistant handles complex requests in depth with extended thinking. Plans are built at run time, not coded in advance.

An employee asks, the Reasoning Engine plans, and agents built or installed through Agent Studio and the Marketplace carry out the work, while admins govern from a central console and plugins act in the systems of record. Developers can extend the sequence by building and deploying agents that plan, reason and execute securely across enterprise systems, and one example covers IT, HR and finance in a single conversational request. ServiceNow, which acquired Moveworks, adds orchestration across departments on its own platform.

Sourcemoveworks.com/us/en/platform/reasoning-engine, /platform and /platform/ai-assistantread 2026-09-12

Agents start on a schedule, on real time events or manually. Scheduled triggers run agents for daily briefings, weekly reports and hourly monitoring. Custom triggers start agents on new Slack messages and Jira updates, CRM changes and calendar events, four event sources in four systems. Agents work where the team already works, running in Slack, joining meetings and updating boards instead of living in another tab.

The Coworker Native Apps (Work, Chat, Build, Meetings, Agents, Artifacts) are Coworker's own surfaces, and Coworker MCP puts the same agents inside Claude, Cursor, ChatGPT and Windsurf. Email appears in the agent examples, which draft outreach through Gmail. Agents run 24/7 in the background without anyone stepping in and send a notice when done, and none of this is held to one tier. Coworker does not say whether a customer can define a compound or conditional trigger beyond the four named event types.

Sourcecoworker.ai/agents capabilities and FAQread 2026-09-12

The Assistant reaches employees without being asked, through nudges and broadcasts, on web, chat and mobile among other surfaces, in over 100 languages. It anticipates what comes next and sends proactive nudges for recurring or time-sensitive tasks. Employee comms, a separate capability, lets internal communications teams broadcast timely, targeted messages to all or some users so they never miss a reminder to act. Each broadcast is a scheduled send to a chosen audience.

Employees can reach the AI Assistant on web, chat or company portals, as well as intranets, browsers and mobile. The Conversations API embeds the Assistant in applications Moveworks does not own, and a dedicated AI Assistant on web ships as its own release. The Reasoning Engine acts on requests from any of these surfaces, and nudges key on recurring and time sensitive conditions.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform and /platform/internal-communicationread 2026-09-12

OM2 reads every connected tool continuously, with no uploads or re-syncing, learns backwards over historical data at setup and keeps evolving as it sees more each day, whereas most assistants, Coworker says, fetch document chunks at query time and forget afterward. Knowledge is stored as connected facts about people, projects, customers and decisions, with customers, projects and deals, as well as people, as first class nodes rather than raw text. Recall is synthesized ahead of time rather than found at query time, relevancy-ranked by proximity, recency and centrality, with sub-second graph traversal.

Retrieval is scoped by permission-aware traversal built into the graph, with access policies on every fact and connection. Every answer traces back to its source, and agents get permissioned context across Slack, CRM, docs, Jira and 50+ apps. The corpus covers messages, tickets, deals, docs, sheets, calendars, CRM, emails, meetings, transcripts, code, wikis, boards, PRs, recordings and contacts. Coworker's comparative figures (84% preference, 20% faster, 66% cheaper) are its own unaudited benchmarks.

Sourcecoworker.ai/platform OM2 section with /blog/introducing-om2 and /agentsread 2026-09-12

Answers come from the customer's own connected systems, filtered to what each asker may see, and a dedicated authoring product keeps that corpus up to date. Enterprise Search gives instant, context-aware answers across business apps, tailored to role, region, language and access level without relying on exact keywords or rigid filters.

The AI Assistant connects to the systems and content sources the customer uses, and a grounded knowledge system ties answers to the most up-to-date and trustworthy documentation available, with fact verification among the AI safeguards. Knowledge Studio generates grounded knowledge articles to fill content gaps and improve self service for FAQs, so the content grows over time, with gaps found from what employees actually ask. Retrieval respects permissions, so two people asking the same question can get different results. This is a retrieval structure over the customer's own estate that lasts between runs and scales far past any context window.

Sourcemoveworks.com/us/en/platform/enterprise-search, /platform/ai-assistant, /platform/ai-knowledge-management and /platform/securityread 2026-09-12

OM2, which replaced OM1 as the headline layer, is built by reading the customer's connected tools continuously, with no uploads or re-syncing, and learns backwards over historical data at setup. Agents use the graph to track progress, learn from corrections and continuously improve, and memory compounds with every interaction, so learning from corrections is written by the agent as well as absorbed into the product.

Scoping rests on isolated single tenant infrastructure, access policies on every fact and connection, and permission aware traversal, with permissions per user in the native apps. Coworker states no retention period, expiry, purge or deletion path for the memory. The only published retention figure is 90 days for recorded meetings on the Enterprise tier.

Coworker MCP is one connection, read-only by default, so the graph can be read and inspected there and in the native apps, with permissions on each fact, but nothing lets a customer or an outside caller edit, correct or delete a fact in it.

Sourcecoworker.ai/platform, /agents and /blog/introducing-om2read 2026-09-12

The Assistant uses four kinds of memory, and none is a lasting store per user, since conversation context is cleared every 24 hours. Semantic memory is knowledge of the content, entities and terminology the organization uses, shared across the organization rather than kept per user.

Episodic memory is billed as recalling past conversations with the user, but it is defined as awareness of the current conversation, meaning what questions and answers have been exchanged and what decisions have already been made. Context is automatically cleared every 24 hours from the reasoner, so anything older than a day is gone.

Procedure memory is knowledge of the tasks that can be performed and the business processes or rules to follow, meaning the plugin catalog and the customer's configured rules. Working memory is awareness of which operations are in progress and at what stage, with a framework that tracks variables such as business object IDs, which is run state inside a single execution. The context window is assembled fresh on each turn and the engine reads everything every turn, so nothing is carried in from an earlier store.

Sourcehelp.moveworks.com/agent-studio/agentic-ai/memory-constructs, /assistant-behavior-framework and /agentic-reasoning-engine/how-the-reasoning-engine-worksread 2026-09-13

Customers can add approval steps to any agent workflow, where a reviewer can review, edit or reject the agent's proposed action before it executes, so the hold sits on the agent's own action and the reviewer can amend it as well as approve or deny it. Both modes are supported, with agents running fully autonomously for routine tasks or with approval gates on any workflow so a person reviews and approves actions before they execute. Background runs work the same way, notifying the team when done so they can review the output and approve actions before they go live.

Permissions, approvals, credit limits and escalation logic are named together as controls, and a credit limit is a hard spending stop on an autonomous agent that does not depend on anyone noticing. Escalation logic appears in the products too, with the Incident Orchestrator enforcing escalation timers and the account agent escalating one strategic account to an AE. Agents inherit the permissions already in place, with no new logins and no new SSO maps, so an agent cannot go beyond the authority of the person it acts for.

Sourcecoworker.ai/agents capabilities and FAQ, with /platformread 2026-09-12

Guardrails surround what the agents do. A content moderation system filters harmful or inappropriate content, prompt protection guards against prompt injection attacks, and query risk assessment identifies and mitigates risks in user queries. Fact verification and identity validation add further checks, with authentication and authorization handled by deterministic systems and source-of-truth methods rather than LLMs. The Reasoning Engine operates within scoped action boundaries enforced at the infrastructure level.

Each of these limits what the agent may do, but there is no person in the loop. There is no approval queue, checkpoint or escalation on a risk threshold, and no human role is named, so no one signs off before the Assistant resets access, provisions a tool, updates CRM data or completes a purchase request, all actions it takes end to end. Enterprise permissions and scoped access govern who can reach what, and governance from ServiceNow belongs to the acquirer's platform.

Sourcemoveworks.com/us/en/platform/security and /resources/blog/why-autonomous-ai-agents-need-new-enterprise-security-modelread 2026-09-12

Coworker holds SOC 2 Type II, GDPR compliance and CASA Tier 2, shown as three badges on the platform page that each link to a Secureframe trust portal at village-labs.secureframetrust.com. Identity and access controls include SSO, RBAC, and encryption at rest and in transit, and SSO is part of the Enterprise entitlements.

Permissions reach down to each fact, since Coworker is permission-aware by construction, with access policies on every fact and connection, so everyone sees only what they are allowed to see through traversal of the graph that respects permissions. Because the graph pulls Slack, CRM, email and HR systems together, that authorization on each fact governs what every user can reach. Agents inherit the permissions already in place, with no new logins and no new SSO maps, so there is no privilege elevation and no parallel access model to drift.

Isolated single tenant infrastructure and complete audit trails across the platform add to this, along with a commitment never to train models on customer data and published legal agreements, namely a privacy policy, terms and a Master Services Agreement.

The agents page says agents tap into 100k+ deployed agents' learnings, which reads as learning across customers and sits against the statement that customer data is never used to train models, and Coworker does not say whether the shared learnings are behavioral patterns rather than customer content.

Sourcecoworker.ai/platform enterprise-grade section and FAQ, with /pricingread 2026-09-12

Moveworks publishes ten certifications with their scopes and auditor marks. The ISO/IEC set covers 42001 for AI management, 27001, 27017, 27018 and 27701, SOC 2 Type 2 spans security, confidentiality, availability and privacy, CSA STAR Level 2 is held at Gold, and FedRAMP, GDPR and CCPA complete the list.

Controls cover access to how user data is processed and stored, encryption at rest and in transit, masking of sensitive PII, and identity validation that uses deterministic systems and source-of-truth methods for authentication and authorization, securing access to systems and data without LLMs. The design follows zero trust, never trust and always verify, with least privilege access and responses scoped to each person's permissions.

Assurance work includes application security reviews, vulnerability scanning and external penetration testing, red team exercises against enterprise and AI systems, and a HackerOne bug bounty open to all researchers at every severity level. The certification reports sit behind a Whistic profile reached through a demo request or an account executive. Security that ServiceNow's trust and controls add belongs to the acquirer.

Sourcemoveworks.com/us/en/platform/security and /platform/ai-assistantread 2026-09-12

Every action is logged and every decision auditable, with guardrails the customer sets and audit trails the customer owns, and the agents FAQ says every action in autonomous runs is logged for full auditability. Complete audit trails across the platform are listed among the enterprise controls beside permissions and identity, and logging every action records what the agent did, not only what it produced.

Answers are attributed separately in OM2, where every answer traces back to its source, so a conclusion can be walked back to the fact and the connected tool it came from. Coworker gives no detail on the audit trail itself, with no stated retention period and no word on whether it can be exported or filtered, whether it captures reasoning as well as actions, or whether it exists below the Enterprise tier.

Sourcecoworker.ai/agents and /platform enterprise-grade section, with /blog/introducing-om2read 2026-09-12

Every system access and data event is logged for full visibility and can be reviewed to support compliance and incident response. The Reasoning Engine works within scoped action boundaries enforced at the infrastructure level, with detailed audit trails for compliance, so the agent's actions leave a retained, reviewable record.

Reasoning can be inspected per interaction, not only in aggregate, because the AI Assistant shows its work and a reader can follow how a request became an action. Employee Experience Insights gives program owners tools to identify issues, track metrics and improve the assistant with governance and analytics, and a self service admin console centralizes configuration and monitoring. Analytics that ServiceNow adds belong to the acquirer.

Sourcemoveworks.com/us/en/platform/ai-assistant and /resources/blog/why-autonomous-ai-agents-need-new-enterprise-security-modelread 2026-09-12

Isolated single tenant infrastructure is offered in four forms, cloud, private cloud, on premises or air gapped, and on premises and air gapped installs sit in the customer's own environment, so the customer decides where data rests. Coworker is SOC 2 Type II, GDPR and CASA Tier 2 verified, with SSO, RBAC, encryption, audit trails and air-gapped deployment support.

Single tenancy is the baseline, and the OM2 memory runs on isolated single-tenant infrastructure in Coworker's cloud or via VPC. VPC peering and bring your own model on the customer's own infrastructure are further options, so a customer who cannot send data to a shared service has three published routes.

The homepage says routing is all hosted in the US and the OM2 announcement leads with cloud and VPC, while the platform page states the full range. There is no named region list for the hosted option, no residency selection for cloud customers, and no page on what an air gapped deployment costs, excludes or requires.

Routing across twelve providers is hard to square with an air gapped install, and bringing your own model on the customer's infrastructure may resolve that, though Coworker does not say so.

Sourcecoworker.ai/platform OM2 security line and FAQread 2026-09-12

Hosting is on AWS across seven named regions, with a commitment that customer data never leaves its region and a dedicated GovCloud environment for federal clients. The regions are US Commercial, US GovCloud and Canada in North America, EU Commercial and the UK in Europe, and Australia and Japan in Asia Pacific. All customer data remains in its region and is never transferred elsewhere. Moveworks GovCloud is a dedicated, secure environment built for government agencies and federal clients, backed by FedRAMP authorization. There is no on premises deployment.

Sourcemoveworks.com/us/en/platform/security and /solutions/ai-for-federal-governmentread 2026-09-12

A catalog of agents is published, each described and tagged by role. Expansion Pipeline, for Account Management, finds accounts hitting usage ceilings and generates upgrade outreach, and Revenue Recovery, for Finance, processes payment failures with segment-specific recovery playbooks. Pipeline Cleanup, for Sales Ops, enforces CRM discipline on stale deals, past due dates and missing data.

Incident Orchestrator, for Engineering, routes incidents, enforces escalation timers and tracks resolution, and Data Analyst, for BI and Analytics, queries data, builds reports and surfaces insights automatically. Three more are named in the deployment section, Post-Meeting Actions for Sales, Contract Review for Legal and Bug Triage for Engineering, and the agent picker offers Account, MCP, Engineering, BI, Legal, Meetings, Finance and Sales as classes. Each agent works on its own and serves a different function on different objects for different teams in the same company.

Once a tool is connected, the product learns in minutes and suggests agents suited to the user's role, so the catalog proposes agents from what a customer connects. OM2 carries shared skills and artifact templates that travel across models and do work when selected, and use case pages by function, one each for Sales, Engineering, Customer Success, Support, Product, Marketing, People, Operations and Industries, make the catalog browsable. The named agents each appear as a card with no page of their own, and no count of the full library is given.

Sourcecoworker.ai/agents agent set and role suggestions, with /platform OM2 skillsread 2026-09-12

An AI Agent Marketplace at marketplace.moveworks.com offers a curated library of ready-to-use, pre-built, production-proof AI agents that are customizable and free to install, with quick connector setup and MCP. Each agent does work once selected, installs on its own through a stated path with no added license, and can be removed without affecting the rest.

Next to the catalog, Agent Studio lets developers build and deploy AI agents that plan, reason and securely execute actions across enterprise systems, and Knowledge Studio, Quick GPT and Brief Me ship as separately named units. Specialized AI Assistants, which create expert agents, are marked coming soon.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform/ai-agent-builder and marketplace.moveworks.comread 2026-09-12

Coworker routes each task to the optimal model across closed, open-source and self-hosted providers, balancing cost, latency and accuracy, with every task routed to the cheapest model that meets the quality bar. It names 12+ model providers, among them OpenAI, Anthropic and Google, plus open source Llama, Mistral and MiniMax. With BYOM, a customer can bring its own models and run them on its own infrastructure.

As better models ship, teams get them automatically with no migration and no vendor lock-in, and OM2's memory and skills travel with the customer whatever model it chooses. Coworker MCP, on the same page, lets the customer's own assistant reach Coworker's memory. Coworker does not say whether an administrator can pin a specific model per agent or can only rely on automatic routing.

Sourcecoworker.ai/platform routing section and FAQread 2026-09-12

Several language models are routed by the Reasoning Engine on the customer's behalf, but no provider is named and no choice is offered. The engine orchestrates enterprise-ready LLMs and built-in tools, so routing is plural, done by Moveworks and disclosed. Safeguards protect the LLMs against hallucination, data poisoning and prompt injection, and no customer data is used to train global generative models. Moveworks historically ran on its own reasoning stack.

There is no model picker, admin setting or bring your own key path, no model assigned per agent and no individual provider named. Orchestration is Moveworks' decision, made per task, and Moveworks presents that as value on day one with no model tuning, prompt chaining or advanced engineering required. Support for any model on the ServiceNow AI Platform belongs to the acquirer.

Sourcemoveworks.com/us/en/platform, /platform/ai-assistant and /platform/securityread 2026-09-12

Coworker MCP, a product with its own page, puts org memory, 50+ tools and dedicated agents inside any MCP client through one connection that is read-only by default and uses the same SSO and permissions, with Claude, Cursor, ChatGPT and Windsurf named as clients. OM2 also connects through MCP or an API, so Coworker's memory can be used outside Coworker in any MCP-compatible client.

Through it the customer's assistant calls Coworker, and because dedicated agents sit inside any MCP client, an outside assistant can invoke a Coworker agent that updates CRM records, creates tickets and sends follow ups. The agent picker lists MCP as one of its surfaces alongside Account, Engineering, BI, Legal, Meetings, Finance and Sales.

The connection reads by default, and the wording implies write access can be configured, but Coworker does not say how or what a write scope covers. Permissions and SSO come from the same identity, so the surface does not widen a customer's exposure. The memory is sold as one memory for every surface, with skills traveling too. Coworker publishes no tool list, endpoint reference, SDK or OpenAPI document, and the API named in the OM2 post has no published reference.

Sourcecoworker.ai/platform portability section and FAQ, with /blog/introducing-om2read 2026-09-12

Outside applications can call the Assistant through the Conversations API, which extends it into another application, portal or intranet. Developer resources sit on four hosts, with a Developer Hub at moveworks.com/us/en/developers, help documentation at help.moveworks.com that includes a Moveworks Setup admin reference, a community at community.moveworks.com and training at academy.moveworks.com.

Agent Studio is a build surface where developers build and deploy agents and plugins that act across enterprise systems, and the Assistant is linked to thousands of action plugins. MCP ships as part of quick connector setup on the AI Agent Marketplace, so an outside assistant can reach Moveworks. The Conversations API is described on a product page, and Moveworks names no public reference for it.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform/ai-agent-builder and the developer estate linked in the site navigation; moveworks.com/us/en/developersread 2026-09-12

There is no sandbox, dry run, simulation or staging workspace, no holdout, A/B comparison or versioning and rollback of an agent configuration, and no evaluator, scored result or regression surface. In the deployment lifecycle the agents FAQ walks through, a customer builds an agent in the Agent Builder and it runs, with no test step. The platform is organized around five layers, OM2, Routing, Portability, Integrations and Enterprise Grade, and none of them covers evaluation.

The Optimize and scale step says memory compounds with every interaction, which describes the memory layer growing. Agents are said to get smarter with use, observe the team's patterns and suggest new automations, and get smarter every week as they learn how the team works. Approval gates let a person review, edit or reject each action before it executes.

Sourcecoworker.ai/agents and /platformread 2026-09-12

Output is checked for accuracy at run time and admins get tools to tune the Assistant, but there is no way to test a change before employees see it. Fact verification improves the accuracy of generated information as a standing safeguard, alongside query risk assessment and a content moderation filter, all of which check what the agent produced.

Around it sits a tuning loop for the Assistant, as Employee Experience Insights lets program owners identify issues, track metrics and improve the assistant, and cutting-edge optimization tools let admins track metrics, resolve issues and make enhancements. There is no test environment, sandbox, holdout or simulation, and no versioning or scored result to compare.

Fact verification gives the customer no verdict to compare across versions, and nothing runs a new or edited agent against a known set before it reaches employees, though these agents reset access and provision tools.

Sourcemoveworks.com/us/en/platform/security, /platform and /platform/ai-assistantread 2026-09-12

Data comes in through OAuth connectors feeding the graph, actions go out as connector writes that update CRM, create tickets and send follow-ups, and the outside surface is an MCP server. Coworker presents OM2 as replacing work at the interface, using sub-second graph traversal in place of brute force tool calling. Nothing operates a screen, and all fifty connectors are OAuth APIs.

Chrome and VS Code appear among the OAuth connectors on the platform page, in the list of connectors feeding the graph alongside Slack, Snowflake and Workday, and what is read from them includes code, PRs and recordings, all ingested into the knowledge graph. Coworker has no hosted or local browser, desktop session or remote computer control, and no RPA, recorder or extension that acts on a page.

Sourcecoworker.ai/platform integrations list and /agents context listread 2026-09-12

The browser is a place the Assistant lives, not an interface it drives. Browsers are among the access surfaces alongside chat, intranets and service portals, and an AI Assistant on web ships as a destination employees open. On every path the employee opens the surface and types, and the Assistant answers and acts. Actions run through code, as the Assistant is linked to thousands of action plugins and the Reasoning Engine selects the right tools across hundreds of connected systems.

Resetting access, provisioning tools, updating CRM records and submitting purchase requests all run through those connectors and the Conversations API. Nothing clicks, fills in or advances a page, so a change in a target application's markup has nothing to break. There is no hosted or local browser session, desktop control, remote or local computer use, or RPA fallback.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform and /platform/ai-agent-builderread 2026-09-12