{"id":3072,"date":"2026-09-16T07:55:50","date_gmt":"2026-09-16T07:55:50","guid":{"rendered":"https:\/\/dmarketertayeeb.com\/blog\/salesforce-koa-crm-reasoning-model\/"},"modified":"2026-09-17T06:59:09","modified_gmt":"2026-09-17T06:59:09","slug":"salesforce-koa-crm-reasoning-model","status":"publish","type":"post","link":"https:\/\/dmarketertayeeb.com\/blog\/salesforce-koa-crm-reasoning-model\/","title":{"rendered":"Salesforce Koa: CRM Reasoning Model, Access, Deployment and Benchmark Boundaries"},"content":{"rendered":"\n

Short answer:<\/strong> Salesforce Koa is a CRM-focused reasoning model for Agentforce, built by post-training NVIDIA Nemotron 3 Super rather than by releasing a new general-purpose base model. Salesforce says Koa uses simulated CRM work, tool-use training and its trust boundary; a Salesforce-authored technical preprint now gives more detail on the method and benchmark results. The evidence is useful, but it does not establish that Koa is universally available, independently evaluated or better than every frontier model.<\/p>\n\n\n\n

There is also an important access qualification. The current Koa product page contains language that sounds like a managed model in the catalogue and \u201cavailable to all customers out of the box.\u201d The same page\u2019s FAQ, the launch release and the announcement\u2019s rollout section describe select pilots now, with general availability expected in U.S. regions in winter 2026. Until your Salesforce org or written account confirmation resolves that contradiction, treat Koa as an entitlement- and pilot-dependent capability, not as a generally downloadable model.<\/p>\n\n\n\n

This guide keeps the practical question in view: what can an enterprise buyer verify about Koa\u2019s lineage, training, controls, evidence and access before allowing it to reason over CRM workflows?<\/p>\n\n\n\n

What the new evidence adds<\/h2>\n\n\n\n

Salesforce announced Koa on September 15, 2026, then published \u201cWhy We Post-Trained Our Own Reasoning Model\u201d on September 16. A related arXiv record for Salesforce Koa: An Enterprise Language Model for Agentic Tool Use<\/em> lists version 1 as submitted on September 14; the PDF title page is dated September 15. These are related first-party accounts, not independent audits.<\/p>\n\n\n\n

Buyer question<\/th>What the current evidence supports<\/th>What still needs verification<\/th><\/tr><\/thead>
What is Koa?<\/td>A Salesforce CRM reasoning model for Agentforce, post-trained from NVIDIA Nemotron 3 Super.<\/td>The exact serving checkpoint, API\/model identifier, context and quota for your org.<\/td><\/tr>
How was it trained?<\/td>Salesforce describes supervised fine-tuning and GRPO over public and synthetic, CRM-shaped simulations with tool-use rewards.<\/td>Whether your use case matches the simulated task coverage and which policies\/tools are enabled.<\/td><\/tr>
How good is it?<\/td>The Salesforce-authored paper reports results on Tau2Bench, BFCL and CRM Bench; results improve on the base model but are mixed against frontier baselines.<\/td>An independent Koa evaluation on your records, permissions, languages, latency and escalation rules.<\/td><\/tr>
Can I use it now?<\/td>Salesforce publicly describes select pilots now and a winter 2026 U.S.-region GA target, while another product-page section uses broader catalogue language.<\/td>Tenant entitlement, region, pilot terms, model visibility and current release status.<\/td><\/tr>
What does it cost?<\/td>No Koa-specific public SKU was found. Agentforce pricing is adjacent context only.<\/td>A current quote, credits\/conversation terms, edition requirements and contract treatment.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What Salesforce says Koa is<\/h2>\n\n\n\n

Koa is positioned as the reasoning layer for CRM agents: it should decide which tool or workflow step is needed, keep track of multi-turn context and stop or ask for help when the required tool, parameter or permission is missing. Salesforce\u2019s September 16 account describes examples such as lead qualification rules and a missing-tool situation in which the model should say what it cannot do, ask what it needs, and then resume or hand off.<\/p>\n\n\n\n

That is a design objective, not proof that every Koa deployment will behave that way. The result depends on the Agentforce agent definition, tools, records, permissions, guardrails, human approval steps and model configuration. A model\u2019s reasoning capability cannot grant access that the surrounding system does not grant.<\/p>\n\n\n\n

Post-training: the useful technical distinction<\/h2>\n\n\n\n

NVIDIA Nemotron 3 Super is the open-weight starting point. NVIDIA describes that base as a 120-billion-parameter model with approximately 12 billion active parameters in its hybrid mixture-of-experts design. Its model card and technical report cover the base checkpoint, licence, general-purpose evaluations and deployment requirements. They do not establish that Koa itself has public weights, the same licence or the same serving interface.<\/p>\n\n\n\n

Salesforce says it controls Koa\u2019s post-trained weights and runs training and inference in its own infrastructure. The Koa paper describes supervised fine-tuning followed by group relative policy optimisation (GRPO). Its simulation-to-reward pipeline creates persona-conditioned, multi-turn CRM tasks, executes tool calls in a deterministic sandbox and rewards grounded task resolution. A helper model simulates a customer, emulates tools and judges coverage; this keeps the training loop repeatable without using customer records.<\/p>\n\n\n\n

The paper also describes constrained decision turns. The model can be rewarded for deferring, asking for a missing parameter, requesting elevated permission or handing off instead of taking a wrong action. This is the most useful new reader-facing detail: Koa is being trained for controlled tool use and enterprise task boundaries, not merely for a larger chat answer.<\/p>\n\n\n\n

Koa, Nemotron and the surrounding Salesforce layers<\/h2>\n\n\n\n
Layer<\/th>Role<\/th>Do not assume<\/th><\/tr><\/thead>
Koa<\/td>Salesforce\u2019s CRM-focused reasoning model for Agentforce.<\/td>Public weights, a standalone download, or a generally available API.<\/td><\/tr>
NVIDIA Nemotron 3 Super<\/td>Open-weight base model used as the starting point, according to Salesforce.<\/td>Base-model licence, benchmarks or hardware results transfer directly to Koa.<\/td><\/tr>
Agentforce<\/td>Salesforce\u2019s agent platform, tools, permissions and orchestration environment.<\/td>Choosing Koa changes the agent\u2019s permissions or approval policy.<\/td><\/tr>
AIforce<\/td>A Salesforce interface for working with multiple AI systems and enterprise context.<\/td>AIforce is the Koa model itself. See the AIforce access and controls guide<\/a>.<\/td><\/tr>
Trusted infrastructure<\/td>Salesforce\u2019s boundary, controls and data-handling commitments around the service.<\/td>A trust-boundary statement answers every residency, retention or audit question. The enterprise AI controls guide<\/a> gives the wider control context.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What the Salesforce-authored paper actually measured<\/h2>\n\n\n\n

The paper compares Koa with the Nemotron base model and several external model baselines. It reports rollouts and evaluations from a Salesforce research setup, including Tau2Bench, BFCL and a CRM Bench. That makes the numbers more useful than the launch slogan, but it remains a vendor-authored preprint and uses simulated environments. It is not an independent production evaluation.<\/p>\n\n\n\n

Evaluation<\/th>Koa<\/th>Nemotron base<\/th>GPT-4.1<\/th>GPT-5.5<\/th>Claude Opus 4.8<\/th><\/tr><\/thead>
Tau2Bench weighted average<\/td>69.41<\/td>68.64<\/td>54.48<\/td>83.99<\/td>74.00<\/td><\/tr>
BFCL<\/td>66.63%<\/td>64.73%<\/td>53.96%<\/td>67.63%<\/td>78.18%<\/td><\/tr>
CRM Bench weighted average<\/td>0.86<\/td>0.84<\/td>0.81<\/td>0.90<\/td>0.87<\/td><\/tr>
CRM function-call accuracy<\/td>0.77<\/td>0.71<\/td>0.85<\/td>0.82<\/td>0.83<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The paper\u2019s own interpretation is bounded: post-training improves on the open-weight base, Koa can surpass some strong baselines on some measures, and it remains below the strongest frontier results in the reported comparisons. The table does not prove general superiority, lower total cost, higher revenue or safer behaviour in a particular org. Reproduce the task definition, tool schema, permissions, language and success criteria before using a benchmark to choose a model.<\/p>\n\n\n\n

How to read the \u201c3x fewer errors\u201d and product-page metrics<\/h2>\n\n\n\n

The September 15 release says Koa matched or exceeded leading performance on CRM benchmark tasks with three times fewer errors. The product page additionally advertises 11% higher precision for right-action calling, 2.1x reliability for recalling context and 15% better context handling in long conversations. These are Salesforce claims. The pages reviewed do not expose enough denominator, baseline, task split, error definition, confidence interval or independent evaluator detail to treat them as universal performance guarantees, and the paper\u2019s published tables do not provide a denominator that maps cleanly to the \u201c3x\u201d wording.<\/p>\n\n\n\n

Use the claims as hypotheses for a controlled evaluation. A fair comparison should run the same anonymised or synthetic cases, tool definitions, access policy, temperature, model version and escalation rules across candidates. Record both a correct action and a correct refusal; a confident action on a forbidden or under-specified record is not a success.<\/p>\n\n\n\n

Availability and rollout: resolve the public-page conflict<\/h2>\n\n\n\n

The public surfaces do not presently form one clean availability statement:<\/p>\n\n\n\n

Surface<\/th>Wording or evidence<\/th>Safe interpretation<\/th><\/tr><\/thead>
Koa product page, main availability section<\/td>Describes Koa as a managed LLM in the generative AI models catalogue, selectable org-wide, and uses \u201cavailable to all customers out of the box\u201d language.<\/td>A broad product-surface claim that must be checked against the actual tenant.<\/td><\/tr>
Koa product page, FAQ and rollout copy<\/td>Says select pilot customers can use Koa now, with GA expected in U.S. regions in winter 2026 and an open beta shortly after; another section says Salesforce is moving into pilots.<\/td>Operationally conservative pilot\/entitlement treatment.<\/td><\/tr>
September 15 press release<\/td>Says select pilot customers are using Koa in Agentforce now and general availability is expected in U.S. regions in winter 2026.<\/td>Current launch boundary until superseded by an authenticated release notice.<\/td><\/tr>
Supported Models developer documentation<\/td>Lists beta NVIDIA Nemotron models with Amazon Bedrock API names, but no Koa row or Koa API name was found.<\/td>Do not infer a public API or BYOLLM identifier from the base model listing.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Before planning a rollout, ask the account team or administrator to show the current model entry in the intended org, the applicable region, pilot or beta terms, API\/model identifier, quota, logging behaviour and fallback path. A product-page phrase alone is not enough to establish entitlement.<\/p>\n\n\n\n

Training data, trust boundary and permissions<\/h2>\n\n\n\n

Salesforce says Koa\u2019s simulated training work used no customer data and that Koa training and inference stay within Salesforce\u2019s trust boundary. The paper likewise says its public and synthetic training data did not use customer data. Those are important vendor commitments, but they are not an independent audit. They also answer a narrower question than runtime retention: Salesforce\u2019s Trust and architecture material explains that prompts, responses and trust signals can be logged or stored in Data 360, while zero-retention terms and provider handling can vary by service and contract.<\/p>\n\n\n\n

Ask separately about: what leaves the org, what is stored and for how long, whether session traces are enabled, who can inspect them, how deletion and export work, which subprocessors or regions are involved, and whether the same policy applies to fallbacks. Keep least-privilege permissions, approval gates and audit review in the Agentforce design. Koa cannot make an unauthorised record safe to expose.<\/p>\n\n\n\n

Pricing: no Koa-specific public SKU<\/h2>\n\n\n\n

The current Agentforce pricing page shows adjacent commercial units such as Flex Credits at $500 per 100,000 credits, Conversations at $2 per conversation, a $5 User License that requires Flex Credits, and add-ons listed at $125 or $150 per user per month. It also lists Agentforce1 editions from $550 per user per month. The page says examples are illustrative and information is subject to change.<\/p>\n\n\n\n

None of those figures is a Koa price. They cannot be multiplied into a Koa forecast without the org\u2019s edition, actions, conversation volume, model entitlement, region, contract and overage rules. For broader Salesforce edition context, see the Salesforce edition and pricing guide<\/a>.<\/p>\n\n\n\n

A bounded Koa evaluation before adoption<\/h2>\n\n\n\n

Use a small, reversible evaluation rather than a production switch:<\/p>\n\n\n\n