Before you buy a partner, turn on the switch you already pay for, if it covers the job. That sentence loses us work. It also stops a six-week build wrapping a checkbox.
Platforms have shipped the easy half. Zendesk agents can set ticket fields and take CRM actions. Salesforce ships Agentforce with Apex actions and a published pattern library for agentic integration. NetSuite’s 2026.1 Bill Capture moved onto a generative document-understanding model and added a scripting module for document capture. Those are real products. Pretending they do not exist is how implementation firms used to talk, and it is why IT stopped believing them.
Helpdesk
If the job is “set the group, the tags, and a priority on new tickets, in Zendesk, using intents we can already name”, start with the native agent and your existing triggers. Inventory the rules that already touch those fields so you do not get two writers on one priority.
The native path usually stops at the helpdesk boundary. It will not look up an order in the ERP you did not connect, apply a refund policy that lives in a spreadsheet, or own an exception type that belongs to billing. If your leak is tickets bouncing because the system of record is somewhere else, a Zendesk-only agent will classify faster and still be wrong for the same reason the macro was wrong.
Public replies are a separate decision on every platform. Do not turn those on because the demo looked fluent.
CRM
Salesforce can draft, summarise, and, with Agentforce, take actions you define in Apex. Einstein Activity Capture still does not reliably fill the fields your forecast depends on, which is the complaint we hear from RevOps, and it is not a reason to give a model write access to StageName.
If the job is “capture the email and put a plausible next step on the record”, try the native tools, with proposal fields rather than canonical ones. If the job is “enrich, score, write the CRM, and prepare the next conversation, without silently overwriting a rep”, you are into a write path, conflict detection, and an exception list. That is sales operations work, and it is also where we still earn a fee.
We are an Official Salesforce Consulting Partner. That is evidence we can build the write path. It is not a reason to skip Agentforce when Agentforce is the whole job.
Documents and ERP
If accounts payable is typing invoice headers into NetSuite, Bill Capture is the first experiment, not a partner statement of work. Extraction is largely solved, including inside the ERP.
Validation is not. Matching the line to the purchase order and the goods receipt, deciding the variance you will tolerate, and giving each exception type an owner: those stay yours. Native capture that dumps everything into one review pile has not removed the pile. It has renamed it.
The recurring stopping point
Cross-system checks, and someone who owns the items the model cannot finish. Platforms sell a feature. They do not sit in your exception queue in month four.
Turn the native feature on when the workflow is single-system, the action is one the product already documents, and you can name the intents or document types without a workshop. Call us when the next step is a write into a second system, or when the native queue has become a second manual process.
The assessment is free. Bring the feature you already tried. If it is enough, we will say so.