Daniel Dines

Instead of going to see what kind of roles do you have in your company? Like you have a BDR person and so on. We go and ask, what kind of processes do you run today? How does your procure-to-pay process look like? What are the rule-based parts? What are the parts that are non-deterministic that are good use cases for agents? And let's go and deliver those.

It's the same approach that we did with RPA. That can lead to immediate successes because you actually look to smaller tasks. In a healthcare system, you are doing something more like processing denials or prior authorization. We'll focus on these types of tasks and we'll create agents specifically for

It's the same approach that we did with RPA. That can lead to immediate successes because you actually look to smaller tasks. In a healthcare system, you are doing something more like processing denials or prior authorization. We'll focus on these types of tasks and we'll create agents specifically for

It's the same approach that we did with RPA. That can lead to immediate successes because you actually look to smaller tasks. In a healthcare system, you are doing something more like processing denials or prior authorization. We'll focus on these types of tasks and we'll create agents specifically for

this and we will connect them with the robots that do the the rule-based task in the in this orchestration layer what do you think is the biggest misnomer that people have about the non-rule-based agent layer that they think but they're wrong about the biggest misnomer is that agents will be good at doing rule-based tasks which they are not for sure

this and we will connect them with the robots that do the the rule-based task in the in this orchestration layer what do you think is the biggest misnomer that people have about the non-rule-based agent layer that they think but they're wrong about the biggest misnomer is that agents will be good at doing rule-based tasks which they are not for sure

this and we will connect them with the robots that do the the rule-based task in the in this orchestration layer what do you think is the biggest misnomer that people have about the non-rule-based agent layer that they think but they're wrong about the biggest misnomer is that agents will be good at doing rule-based tasks which they are not for sure

So let's say your success rate is 0.99, right? At every step. If you'll do 100 steps and you multiply 0.99, you will get to a very small number.

So let's say your success rate is 0.99, right? At every step. If you'll do 100 steps and you multiply 0.99, you will get to a very small number.

So let's say your success rate is 0.99, right? At every step. If you'll do 100 steps and you multiply 0.99, you will get to a very small number.

that means that the error rate is huge for every step that you you are taking in the process so they are not good at this and llms will yield a different result every time you ask them even the same questions because they in a way they work like our mind works i'm blunt

that means that the error rate is huge for every step that you you are taking in the process so they are not good at this and llms will yield a different result every time you ask them even the same questions because they in a way they work like our mind works i'm blunt

that means that the error rate is huge for every step that you you are taking in the process so they are not good at this and llms will yield a different result every time you ask them even the same questions because they in a way they work like our mind works i'm blunt

Because it's early. The agentic, it's really early. And we have to deliver on the roadmap that we have. We have the orchestration engine, but we need to deliver the agentic orchestration workflows. We have to deliver the agent builder. By the way, we have just launched it in private preview. It's the early innings of a huge movement to adopt agents.

Because it's early. The agentic, it's really early. And we have to deliver on the roadmap that we have. We have the orchestration engine, but we need to deliver the agentic orchestration workflows. We have to deliver the agent builder. By the way, we have just launched it in private preview. It's the early innings of a huge movement to adopt agents.

Because it's early. The agentic, it's really early. And we have to deliver on the roadmap that we have. We have the orchestration engine, but we need to deliver the agentic orchestration workflows. We have to deliver the agent builder. By the way, we have just launched it in private preview. It's the early innings of a huge movement to adopt agents.

Gen AI was not so successful in enterprise so far. I think within next year, we are going to see a lot more use cases, particularly in the agentic AI space.

Gen AI was not so successful in enterprise so far. I think within next year, we are going to see a lot more use cases, particularly in the agentic AI space.

Gen AI was not so successful in enterprise so far. I think within next year, we are going to see a lot more use cases, particularly in the agentic AI space.

Because we will put it in the context of an agentic workflow and we will surround it with rules. And we will limit the non-predictable aspect and we will put humans in the loop to validate the outcome. It's not going to be like a chatbot. It's going to be the conductor will be this enterprise workflow that can be triggered by an external factor.