Credal AI, Inc.

etc, and then potentially hundreds of rows per day. We need to make sure that data is represented properly: as something that can be used in a prompt, both for this usecase, and for future cases which may need to touch this data. In order to run that

The goal was to empower business users to use Salesforce data without needing Salesforce architecture expertise. When there are ambiguous fields, custom objects, legacy data — AI will silently choose for you and often get it wrong, leading to risk for our business in time and accuracy.

and are usually prepended to the prompt in classic RAG style, sometimes paired with the description depending on the query. For example, if you’re just asking the agent to assess a single business, you can just put everything into one prompt. You can see an example of this workflow below in Credal: Challenge 2: Data governance, permissions, and access controls Regulated enterprises very often have to be able to defend decisions to their regulator, so a well governed system, that’s compliant is vital. That means careful audit logging of every request, easy deletion when customers ask for their data to be deleted, and easy observability that’s exportable to companies’ existing systems for storing audit logs in case regulators come asking for details in the future. Equally important is the need to think through the permissions of who should be able to access the data we’ve connected from internal systems. Most large enterprises will have a lot of teams which operate on the basis of the