Daniel Dines

In the same time, we will reduce actually a lot the human input. We are going to a place where we'll have a semi-autonomous agent that will do most of the job. And humans will just sit, monitor their inboxes. They will get task slides. Please validate this. Please validate this. Answer this. I need this information.

And then feedback to the agents and to an enterprise workflow that will be orchestrating the work. And the enterprise workflow will be rule-based.

And then feedback to the agents and to an enterprise workflow that will be orchestrating the work. And the enterprise workflow will be rule-based.

And then feedback to the agents and to an enterprise workflow that will be orchestrating the work. And the enterprise workflow will be rule-based.

But the orchestration is rule-based. This is how work is done today. You'll have a lot of rule-based workflows that will connect different people to do their job.

But the orchestration is rule-based. This is how work is done today. You'll have a lot of rule-based workflows that will connect different people to do their job.

But the orchestration is rule-based. This is how work is done today. You'll have a lot of rule-based workflows that will connect different people to do their job.

Yes, but we also will integrate with agents built with other platforms. We call a lot of APIs from different platforms, right? An agent to me within the Salesforce platform will be just an API. I will just call an API, I will get an answer back, and I will feed it to a human user, say, what do you think about that answer?

Yes, but we also will integrate with agents built with other platforms. We call a lot of APIs from different platforms, right? An agent to me within the Salesforce platform will be just an API. I will just call an API, I will get an answer back, and I will feed it to a human user, say, what do you think about that answer?

Yes, but we also will integrate with agents built with other platforms. We call a lot of APIs from different platforms, right? An agent to me within the Salesforce platform will be just an API. I will just call an API, I will get an answer back, and I will feed it to a human user, say, what do you think about that answer?

And then based on human response, I will call another action maybe in another, or call another agent in another enterprise. Because we will be the orchestration on the top. And there is also, it makes a lot of sense to have an orchestration technology that is agnostic. We call it the Switzerland of the platform.

And then based on human response, I will call another action maybe in another, or call another agent in another enterprise. Because we will be the orchestration on the top. And there is also, it makes a lot of sense to have an orchestration technology that is agnostic. We call it the Switzerland of the platform.

And then based on human response, I will call another action maybe in another, or call another agent in another enterprise. Because we will be the orchestration on the top. And there is also, it makes a lot of sense to have an orchestration technology that is agnostic. We call it the Switzerland of the platform.

Because an orchestration engine should provide equally good access to different platforms. What's the interest of Salesforce to provide amazing connections to SAP and vice versa? No, it's not. So they will focus on building agents that work specifically for workloads that stay within their platforms.

Because an orchestration engine should provide equally good access to different platforms. What's the interest of Salesforce to provide amazing connections to SAP and vice versa? No, it's not. So they will focus on building agents that work specifically for workloads that stay within their platforms.

Because an orchestration engine should provide equally good access to different platforms. What's the interest of Salesforce to provide amazing connections to SAP and vice versa? No, it's not. So they will focus on building agents that work specifically for workloads that stay within their platforms.

But it's not about what he wants. It's about what customers will actually do. And why would they not do that? Because I will give you a real quote from one of our largest healthcare customer in the United States. I was talking to the CIO and he said, I will never put data from Epic into Salesforce in order to create an agent. Never. There is no chance to do this. It's as simple as this.

But it's not about what he wants. It's about what customers will actually do. And why would they not do that? Because I will give you a real quote from one of our largest healthcare customer in the United States. I was talking to the CIO and he said, I will never put data from Epic into Salesforce in order to create an agent. Never. There is no chance to do this. It's as simple as this.

But it's not about what he wants. It's about what customers will actually do. And why would they not do that? Because I will give you a real quote from one of our largest healthcare customer in the United States. I was talking to the CIO and he said, I will never put data from Epic into Salesforce in order to create an agent. Never. There is no chance to do this. It's as simple as this.

They will prefer to use us to have connectors, feed agents only with the data they really need to make a decision, and then have the orchestration in an agnostic way.