Zoomin, knowledge, and Agentforce grounding

A team drops a folder of PDFs into a brief and asks for the customer golden record. The folder holds manuals, policy notes, and a few documents nobody can date. The request treats that pile as a person. It is not a person. It is knowledge, and only some of it is current. Zoomin manages unstructured data for knowledge. The announcement tied that work to Data Cloud and to Agentforce grounding. Grounding lets an answer cite material you have accepted. It does not turn a document into a unified customer, and this page will not say that it does.

The close came before the rename. SynconAI records the rename as its own sentence, because the dates differ. As of 14 October 2025, Data Cloud is Data 360. The acquisition itself sits earlier. The line you can date for Zoomin is this one. "Salesforce completed its acquisition of Zoomin on November 1, 2024." Use Data Cloud when you are quoting what that announcement tied the work to. Use Data 360 when you are talking about the product name after 14 October 2025. They are the same product across a rename. They are not a new promise about documents.

#A source needs an owner before it needs a model

Take one document a service agent might cite. A shipping policy, two pages, last reviewed by a person you can name. The quote starts there, not at the folder. Who may change the policy. How often they review it. Which channels may cite it. Which must not, because the words are for colleagues. What the agent should do when the policy and the order record disagree. The order record wins for the date the order system returned. The policy may explain the window. It may not overwrite the date.

That disagreement rule is the point of keeping documents and records apart. A golden-record claim would say the document and the profile have become one truth. You do not have that, and you should not buy it under this name. Profile unification, where you run it, has its own rules and its own owners. A PDF is evidence you might cite. A unified profile is a key across sources you have already decided to match. Mixing the two in one statement of work is how a policy file starts writing fields on the account.

List sources as systems, not as a drive. The knowledge base you already publish. A file store your security team has accepted. A product-documentation set with a publisher. For each, name the owner and the refresh. A source with no owner will be cited after it is wrong, because nothing in the build marks it stale. Stale is a status a person sets, or a review date a person misses. Put the review on a calendar you already keep.

Languages and locales are a scope choice. A policy in one language cited to a caller in another is a confident error. If you operate in more than one language, say which sources exist in which language, and what the agent does when the match is missing. Transfer is an acceptable answer. Invention is not.

#What the agent may cite

Write an allow list. Article types that are published. Document sets that are current. Fields from the CRM that may be quoted beside the citation. Then write the deny list in the same sitting. Drafts. Internal-only notes. Anything that names an employee in a complaint. Contracts your counsel has not cleared for a customer-facing answer. A folder called "final" is not a clearance.

Grounding should show its source in a way a person can check. If the answer cannot point at the document and the passage, you cannot accept it. A fluent paragraph with no citation is the failure, even when the paragraph happens to be right. The next one will be wrong in the same voice. Make the citation part of the acceptance test, not a nice-to-have in a later phase.

Data 360, if you have it, is where the announcement's Data Cloud tie now sits under the new name. Connecting a source there is a licence and a design question. This page will not tell you that the connection is included. Look at the contract. Some features are add-ons. If you do not know, leave the cell blank and make the blank a question for the partner. A quote that assumes the connection because the announcement mentioned Data Cloud has spent money you have not confirmed.

Agentforce grounding is the use, not a second copy of the library. The agent may cite what the allow list permits, for the running user who is allowed to see it. A document the running user cannot open should not appear in the answer. Sharing still applies. A knowledge project that widens access so the demo can cite a restricted policy has opened the policy. Fix the user or the document, not the sharing.

#What cost means before anyone prices it

Cost is the list of sources, owners, reviews, allow and deny, the connection you have confirmed, and the hours your people spend checking citations. Licences already on the contract, named, with prices left in the contract. Partner time to connect the sources you listed, to set the review, and to test a handful of questions against the citation. Internal time for the owner who must say a document is current. Legal time if any source is a contract or a policy with a duty of care. Those hours are the cost even when they never appear on an invoice.

Out of scope: building a golden record from the folder, merging unstructured text onto the account as if it were mastered data, a full rewrite of every article, a data migration of CRM records that happens to share a programme name, a search project for a storefront. Each can exist. Each is another quote. The Zoomin line is knowledge and grounding.

Volume belongs as a band you supply. How many published articles. How many document sets. How often they change. This page will not invent a count. A partner who prices "all unstructured data" has not asked you what you are willing to stand behind. You should not be willing to stand behind a folder you have not opened.

The acceptance test is a set of questions you write before the build. Ten is enough for a pilot if they are real. For each, the expected citation, or an expected refusal. Include one question where the document and the CRM disagree, and one where the source is on the deny list. A pass cites or refuses. A pass does not average the PDF into the account field.

#Migration services, without pretending the files are records

If you are moving a documentation set from one store to another, say which store, who can read it, and how links in old articles will be kept or retired. That is a migration. It has a file list, a permission map, and a check that a sample of links still resolve. It does not have a matching rule that creates a person.

Retire sources on purpose. A document that contradicts the current policy is worse than a gap, because the gap transfers and the contradiction answers. The owner marks it retired. The agent stops citing it. Keep the file if your retention schedule says so, in a place the agent cannot treat as current. Archive and allow list are different locations. A quote that loads everything it was given, so nothing is lost, has lost the distinction.

Duplicates need a rule. Two shipping policies with different windows cannot both be current. The owner picks one. The other is retired or merged by a person. An embedding will happily sit near both and the answer will pick one on a given day. That is not a merge. It is a coin toss you cannot explain to the customer who received the other window yesterday.

When a document contains a fact that belongs in a field, the work is to type the fact into the field under the field's owner, not to point the agent at the PDF forever. Warranty length, if your business states it as data, belongs on the product. The PDF can explain it. The agent should read the field for the value and the document for the words. Write that split for the facts you already trust as data. Leave the rest as prose.

#The hiring test

People search for the best zoomin Salesforce integration agency. The test ignores the ranking. Hand the partner one current policy and one stale document, and say which is which. Ask who owns the current one. Ask what the agent may cite. Ask what happens when the policy date and the order date disagree. Ask them to keep profile unification out of the price unless you have a separate brief for it. Ask which licence they need to see before they assume a Data 360 connection.

A pass names the owner, the allow list, the deny list, and the disagreement rule. The partner asks how you will review the source. The partner refuses to call the folder a golden record. The partner uses Data Cloud for the announcement and Data 360 for the name after 14 October 2025, and does not treat the rename as a new product you must buy to keep the documents.

A fail offers to "unify the unstructured data into the customer." It loads the whole drive. It cannot say who reviews the policy. It prices a profile project and a knowledge project as one fee. It calls itself the best agency. Send the fee back. Keep the two documents. They are enough to restart the conversation with someone who can tell them apart.

A second test: a question whose answer is not in the documents. The partner should say the agent refuses or transfers. If they say the agent will infer the policy from related files, they have authorised a guess. Related files are how a retired window returns.

#Review is the operating cost

After go-live the work is the calendar. The owner reviews on the date they set. A sample of answers is checked for citation. A denied source that appears in an answer is an incident, not a tuning suggestion. Write who reads that sample. Their hours were on the cost list. If they were not, add them before you call the pilot done.

Changes to a policy go through the owner, then the allow list updates, then the questions you wrote are asked again. Skip the re-ask and you will not know whether the new window is the one being cited. The old file, if it is still in the allow list, will keep winning some of the time.

Observability of what was cited, and any later forecast of value, is a different quote. Spindle AI and the forecast you do not print covers that method. Do not bury a return figure inside a knowledge connection. You do not have the figure, and this page will not invent one.

Send two documents and ten questions, including one refusal and one disagreement. Ask for the allow list before the fee. A partner who can mark the stale file, and who leaves the profile work on its own page, is ready to price a pilot. A partner who wants the whole drive first is still collecting a folder.

#The other searches

The project quote is on zoomin implementation cost. That page does not print a figure. Who bought the company is on what happened to zoomin. The connector is on integrating zoomin with Salesforce. Whether to move is on should I migrate from zoomin. The customer fee is on zoomin licence cost. Who to hire is on hiring for zoomin. This page does not rank an agency.