GS: Just so we make sure, because as I think I mentioned, I have another podcast which is Decoding AI for Marketing. So are you able to comment, how big a deal are agents? For the uninitiated listener here who maybe hasn't really spent a lot of time on AI, what's going on with agents? Can you give perspective on that?
AK: Yeah. I'll call the marketing tagline because we're on a marketing podcast, we're inside the boat here.
GS: Yeah, yeah.
AK: This is what AI was meant to be. And what we mean by that is what do people want from AI? They want to automate, they want the AI to do things that previously required humans.
And there's a lot of ways we can think of how that would make it easier. And as I said, the difference between an agent and a co-pilot or just like a ChatGPT type thing is that it will work autonomously and proactively. And then secondly, that it can take action and actually do things.
And the thing that we found that week at Dreamforce and having over 10,000 customers create their own agents is that by combining Salesforce and an LLM — we'll let them use OpenAI or whichever ones they've used — that they can build these agents really easily and quickly. They don't need any new skills because all the really sophisticated stuff of taking action, it's already built into our platform. So let's take my example of ordering the new part and checking inventory. Well, our platform that billions of customers are using, if you want to let a sales rep or a customer service agent check parts inventory, you would let's say build an integration to an SAP inventory system.
We have this MuleSoft integration technology that a lot of our customers have used. Now, how do you give that functionality you've already built to check inventory to the agent? All you do is you say add an action, and then one of the types of actions is integrations. You pick this integration you've already built, which is an API, that's it. Done. So you have to do nothing different to let the AI agent use all of the workflows, all of the automated actions that people have created on our platform. And so they're like, "Whoa, that's amazing." As opposed to if you're going to go build your own agent from scratch, all of that taking action, you're all custom coding, you're writing your own stuff. And by the way, once you've built all that, then you go back and say, how do I make sure the right people see the right data? If you're a bank and you put all your customer information into, say, a custom-tuned OpenAI running on Azure, it's not going to know that I'm not supposed to show this data about Sally to someone that's not her financial advisor. Then you've got to go rebuild the whole sharing model and all the security rules. We have that all built in our platform already.
GS: But how is an agent different than a rules-based approach? You could set up the rules, say, do this, then do that, do this. Why is AI...
AK: Oh, yeah, yeah, no, that's important because in customer service for years we've had chatbots and we create these rules that go, if someone says this, do that. It's the fact that it's inflexible, it can't handle lots of scenarios.
GS: Can we agree on something? Again, we're in the cone of marketers, right? Just here for this one, right? Because I asked this question to a group of marketers the other day, they started talking about chatbots. There's never been a chatbot that anybody's ever liked.
AK: Yeah, correct.
GS: Yeah. Okay, good.
AK: People hate working with the chatbots because if the customer says, I want to return, and then the customer says, I want to give back this product to you, and it's like, "Oh, I can't help you with that. What would you like next?" Whereas that's the magic of you add an LLM in. Since all of our friends that have built these massive large language models, they've trained it on the internet, it knows that a give back, a return, however they call it in Australian, it knows all that stuff. And so you don't have to program it on that. You can basically, so you create these actions on our platform on Agentforce to say, I'm going to create a return.
And you'll say, well, what can returns do? You'll assign it that look up inventory, ship new parts, give a refund on their credit card. But the way that the Agentforce knows to initiate the return business process is based on how you describe it. So when I create this action, I just said, here's all the actual mechanical things it needs to do, but then there's a description. You'll say returns, and you'll write a paragraph or two on what returns are. And if you go like, "Hey, guess what? Everything I've described works for everywhere except for New Jersey. If they're from New Jersey, tell them we don't do returns in New Jersey." You're writing it in plain English in there, so you don't have the flexibility and the rigidness of these linearly, programmatically built bots.
GS: And nothing against New Jersey, by the way. The agents don't know to go against New Jersey.
AK: I love New Jersey. It's great.