Good morning. Thank you for joining us today. I'm Mike Spencer. Today's session is going to be focused on providing an update on our customer momentum and customer success. As you heard yesterday on the earnings call, we're bringing humans, data, and AI and apps together to build the agentic enterprise. And today you're going to hear an update on how this is translating into accelerating our customer momentum and fueling our relentless focus on customer success. I want to add that this is a webinar in the series of webinars we've been doing for the past several quarters with the intention of giving you more visibility and more insight into what's happening with the business. Some of our comments today may contain forward-looking statements that are subject to risks, uncertainties, and assumptions, which could change.
Should any of these risks materialize or should our assumptions prove to be incorrect, actual company results or outcomes could differ materially from these forward-looking statements. A description of these risks, uncertainties, and assumptions, and other factors that could affect our financial results or outcomes is included in our SEC filings, including in our most recent report, Form 10-K, 10-Q, and any other SEC filings. Except as required by law, we do not undertake any responsibility to update these forward-looking statements, and with that, let me introduce our leaders that have joined me today. Miguel Milano, who's going to start. Obviously, you all know Miguel Milano, our CRO, and then Srini, sitting next to my left, Srini Tallapragada, leads our engineering and customer success organization. I'm super excited.
Prior to handing the floor to them, I'll encourage you to submit your questions online into the chat windows, and we'll make sure and try and get to as many questions as we can once Miguel and Srini are done with their opening remarks. And with that, Miguel.
Yeah. So thank you, Mike. Thank you, everyone, for tuning in today. I wanted to use my time, Mike, if you're okay with it. First of all, trying to summarize at a high level what the quarter looked like, Q3. But as far as I'm concerned, a quarter is a quarter. Check. Amazing. Epic. But where we are mindlessly focused is on the huge opportunity that is coming ahead. It's in front of us. It's the agentic enterprise. And I want to double-click with some slides, if you don't mind, to walk you through how we're thinking about it. So the quarter, Q3, was pretty epic. The reality is it was the best Q3 ever in the history of the company. It was actually the fastest growth that we did in bookings, but also in net new AOV since pretty much fiscal year 2022. And obviously, this is the output.
This is the result of what is really happening underneath. Very important, net new AOV, net new AOV, which is the purest measure of customer success, grew significantly more than the AOV, and as we shared in Investors Day, Robin and I, when net new AOV grows more than AOV, then AOV accelerates, and ultimately revenue accelerates, and this is what we all are obviously very focused on, subscription and support revenue to reaccelerate, so we are very confident H2, net new AOV, is going to be several points ahead of the AOV growth, and we feel also very comfortable looking at the pipelines, looking at the capacity, looking at the momentum of the business, that the net new AOV growth, several points above the AOV growth, is going to continue, so you're seeing the CRPO numbers, which were amazing, well net new AOV grew more than that.
Bookings for the quarter also grew more than that. Pretty exciting. The most exciting thing is that the agentic enterprise opportunity is right here. Now it's very real. It's been rambling for the last, I would say, months. We started feeling it in the demand, in the bookings, in the deals during Q2, but Q3 became very real. Let me explain to you what the agentic enterprise opportunity is, because for 26 years, we've done a pretty good job selling into the CRM SaaS market. We became the leaders in that market. We have 20% market share. We have more market share than our next four competitors together, next five competitors together. But in clouds, like sales and service domains, like sales and service, we actually have 40% market share. It's pretty unbelievable.
But this is a multi-hundred million, multi-hundred billion ton market. All of a sudden, there is a new market coming at us, which is the agentic enterprise market. We define it as agentic enterprise, but it's the digital labor market, the agentic market. And this market is probably an order, potentially two orders of magnitude bigger than the SaaS market. And we've been invited to participate there. We happen to have the software infrastructure that is required to be successful in this new opportunity. And every company is knocking at our door saying, we want to become an agentic enterprise. We've been experimenting for 12, 18 months, particularly the large enterprises that have the resources. They've tried to do it yourself in many different ways.
And every single one of them, most of them, get to a point that they get frustrated because for enterprise scale, for enterprise AI to scale, they need the last mile. And the LLMs alone don't give the last mile. And we can, by the way, do this slide, the two of us, because we see it very clearly. What enterprise AI needs is you need the context. You need the data, what is happening in the company around your customer, but also the metadata, why that data is important. Then you need the AI that is able to do the probabilistic reasoning, not the deterministic reasoning. Of course, everybody has AI. We have it embedded in our platform.
But then you also need the apps, because you want the AI to do smart decisions based on the data and the metadata, but then you want the AI to trigger some execution, some workflows. And you want them to be as deterministic as possible, because you don't want big corporations to rely on AI, an agent, an LLM, to decide how to return a good that was broken to a customer, or how to correct a billing that was mistaken. You want that agent to follow the standard operating procedures that the customer has defined that have been codified in the apps. The apps, most of the customer-facing apps happen to be on Salesforce. That's a huge advantage. And then finally, humans. We all have come to a realization that AI is not replacing humans. AI is augmenting humans.
And humans with AI, humans with agents are going to deliver new levels of productivity, new levels of customer satisfaction. You need them working together on the same workflows, on the same platform. And this is our moat. We bring the last mile. And this is what companies are realizing. They've been experimenting. Many of them, I was in a conversation yesterday. Somebody said, "Miguel, I've been talking to some customers of Salesforce that are building the agentic layer outside Salesforce." I'm like, "Yeah, there are many of them that try to do it, try to get the data," because you can do it yourself, anything. They get the data out of Salesforce, then they build the logic, then they decide that they want to take some actions, but they don't have the capability to execute the thousands of workflows that the customers have already built on Salesforce.
So basically, by doing that, and by the way, the humans are working here, and they built this agentic layer here, trying to build a cool, interactive, conversational UI, but a UI that is disconnected from the humans, and it is disconnected from the execution, and is semi-disconnected with the data, because the moment you move the data out of Salesforce into other data lakes, et cetera, it just becomes obsolete. You can do it, but it's expensive. So most of these customers have realized that they need the last mile. And they turned to us and they said, "Let's do it together. Let's start the agentic transformation journey." So if you go to the next slide, what we've done over the last six months is train our teams to know what we call the agentic enterprise playbook, to know how to capture this opportunity.
And then we make them think in five steps. The first is present an industry point of view, because ultimately, the industry point of view is the demand plan. It's, "Mr. Customer, Ms. Customer, we try to go as high as possible," because the agentic enterprise is a board decision, is a C-suite decision. You want to transform. You want to be more conversational. You want to be more intelligent company. You want to be more proactive. You want to augment your employees. You want to increase revenues. You want to increase margin. You want to make your customers happier. Okay, you need to become an agentic enterprise. How do you do it? That's our industry point of view. If you go to the next slide, this is what we've done.
And this is like a night chart on purpose, because we believe it's such an IP differentiation for us that we didn't want to openly share with everyone. But essentially, what we're doing is for every industry, we started with our top 10 industries. But by the end of January, we're going to have it for the top 24 industries. We've created a very detailed point of view on exactly for every industry, what are the key domains, what are the key workflows in those domains, and for those workflows, how those workflows are going to be reimagined with agents. And typically, for every key workflow, we have four or five agents.
How those agents work together, we described it in our point of view, who is the human manager for those agents, and how the agents interact with the human manager, how those agents impact specific business metrics of the company, and then how those agents are going to be deployed over time. We've defined the agents. We've created not just a value calculator. We've created a database of thousands of agents that have all the definition, the role, the actions that they need to take, the data that they can access, the guardrails, the things that they cannot do, the channels where they surface, where we will surface the agents. This is really a very rich IP. When we put it in front of the customers, they say, "Oh my God, we want to become an agentic enterprise. Let's start." We come in with Horizon One, Horizon Two, Horizon Three.
That's the demand plan. And at that point, they look at me, they look at our teams, and say, "Okay, but wait a minute. This could be expensive, because you guys have all these sort of metrics and consumption of data, ingestion, conversations, seed base. How are we going to make this work?" And this is one of the parts of our methodology to sell the agentic enterprises. We present to customers all sorts of pricing options to meet them where they are. Some customers, so if we go, I think there's a next slide. So I got asked this question in the earnings call yesterday. And essentially, we didn't have any of that nine months ago, a year ago. And we realized we'd listened to our customers.
We realized that different customers are in different stages of their transformation journey, and they need different commercial frameworks to work with Salesforce. If you go to the right, that's my favorite one. Okay? That's the agentic enterprise license agreement, AELA. You're going to hear a lot about AELAs, because AELA is essentially, when customers are determined, they see the 150 different agents that they needed to deploy across their 20 processes. They just want to make sure that they have a flat fee, that they have predictability on the spend, that they don't have to worry about ingesting data or conversations. We are all aligned. It's a risk-sharing model between us and the customer, where we say, "Pay me a flat fee for the next three years." Typically, it's a multimillion-dollar incremental to what they're paying. And just let's start deploying.
Many times, we add FDEs and professional services resources just to help them drive success very rapidly. And this is becoming one of the favorite commercial frameworks, Mike. And we basically put it together at the end of Q3. We sold 16 AELAs, pure AELAs. Then we had versions of AELAs, like maybe dozens or hundreds, but 16 AELAs of 16 customers that went all in and said, "Okay, next three years." And in most cases, we doubled, tripled what customers were already spending with us. But you can go to the left side, which is, "Okay, I still want predictability. I still want predictability, but I like the seed-based additions that you have.
I just want to make sure that my employees that use a seat-based license for you, they have unlimited access to all the agentic power to be augmented." So all unlimited employee usage of Agentforce is included in the new additions, the Agentforce for Sales, Agentforce for Service, or our, I would say, magical SKU, our top SKU, which is A1E, which is the Agentforce One Edition, which includes pretty much everything: Agentforce, Data Cloud, Slack, and many other things. In the middle, you have the pay-as-you-go. If you're not sure, okay, let's start with pay-as-you-go. There are some customers that, like in the hyperscaler world, they like that kind of relationship. They pre-commit, and then basically, they can consume those credits over a period of time.
We have the flex agreements, which essentially, if customers believe that agents are going to take the place of some humans and they may need less seats, which, by the way, we are not seeing in our customer base yet, but it gives them the reassurance that they can move seat-based licenses into flex credits for Agentforce and Data Cloud. So anyways, all these pricing mechanisms are really resonating very well. AELAs are resonating incredibly well. We are approaching now 100 AELAs. Every week, there are 10 or 20 more AELAs that are added into the pipeline. And just so that you know, we do AELAs in the low end of the market, mid-market, and then the top of the market. But for my team to ask approval for an AELA, the size needs to be more than $500,000 in the low end of the market.
More than 1.5 million, I think, is in the mid-market and more than 5 million. This is net new incremental. I don't know if I have more things. Yes. Next slide. Yeah, the next slide is the net new ACV, which was also a key message of the call. So one of the key messages, again, the quarter was amazing, but let's focus on the future. One of the key messages of the future was humongous agentic enterprise demand coming at us. This is like nothing we've seen before. Second message was we are uniquely positioned to win in this new massive TAM, which is multi-trillion TAM. We are uniquely positioned because we have the last mile. The last message of the call was something that we already shared with you in Investor's Day is the lines have crossed.
I told you when I was on a stage in San Francisco, I told you the lines are crossing. I see the lines crossing, and when the NAUV is above the AUV, AUV accelerates, and this is what you need to think about as we move into the future, because we are confident that in fiscal year 2027, NAUV will continue to be a few points ahead of the AUV. We want to make those few points be many points, but that's our goal. We are very confident. If we were confident, hopefully we sounded confident in the investors' call. A month later, we are even more confident. Now, the AUV growth acceleration will translate into revenue acceleration, subscription support. Robin said it very clearly, 12 to 18 months from last month.
I kind of joke with her and I say, "Well, then it's got to be 11 to 17 months," but it's coming, and I mean, I think we have a reputation of being reasonably clear and conservative on how we guide. If we all are saying from the CFO to the CRO that the subscription support revenue acceleration is going to happen between 11 and 17 months, you could be confident of that too. There's a lot of reasons why bookings are accelerating. The capacity, I have 15. Today, I have like 13%-14% more ramped capacity. In total, I have 23% more capacity. At the end of the year, I'm going to have 20% more capacity than a year before. I'm going to enter the year with 20% more capacity, of which more or less 15% growth in ramped capacity.
Ramped capacity is productive capacity. The innovation that Srini and Steve have delivered, I mean, I'm probably the luckiest CRO in the world because I've never seen so much. It's not just Agentforce. It's even across our core clouds. We also launched ITSM. I think we're going to have a lot of good discussions in our next earnings around ITSM. It's booming already. We just launched it. We won dozens of customers. Life Sciences Cloud was a great example. It just quadrupled, or I don't know the specific statistic, but it grew a lot during Q3. And I just want to mention that this is pretty big because we were doing a lot of business in life science and also medical devices, et cetera. But as you know, for many years, we had this great partner that we basically partnered in capturing that opportunity.
We were capturing the outside commercial side, the opportunity. They were very focused on the commercial side and the clinical side. And then a year and a half ago, they decided to compete head-to-head with us, and we decided to build solutions to compete with them. And the results have been incredible. I mean, we announced yesterday Novartis. We had announced Pfizer of the top 20. We've already won five or six. And I say five or six because there's one that is in embargo, but I think there's going to be a press release later today where we're going to announce another major pharma company going to us. So we are gaining market share from Veeva like there is no tomorrow. In addition to the big 20, which there are still many in the air and they are reviewing, they all want the Salesforce platform.
That's why they were happy with Veeva. They want our agentic capabilities. They want our Data Cloud to unify data across all the different domains in their business. And they are afraid to move with a small player that is going to build a new platform for them. So many of them want to stay and are staying. There's more than 100 life sciences customers that have selected Life Sciences Cloud and are moving off Veeva. And we are just getting started. So that's an example of innovation. Anyways, I'm excited about the future. I'm pretty sure that we're going to continue to show this slide because I like this slide so that you see that NAUV is above AUV. And that's my role.
That's also my partner in crime role here, Srini, because he has all the resources for customer success, and he's obsessed in making sure that actually we both are responsible for the NAUV line. So that's what I wanted to share with you, and I'm looking forward to the Q&A, and I'm going to hand over to here to my peers, Srini.
Thank you, Miguel. I think as my role, first of all, thank you, everybody, for joining, and I appreciate the time commitment you have given us. My role is, again, as head of engineering and also customer success. So I think when the industry is changing so much, this is a period of transformation. And what we want to be very sure is when things are changing so much, we're very closely tied because the products are moving, the underlying tech stacks, the models, everything is changing.
Key is to be very tight feedback loop with our products, with our customers, and really feedback that loop. And even the pricing example you saw, we are listening very hard. We are going to fight very hard because I think a lot of things are changing, and we don't take anything for granted, and we are very hungry. And some of the examples, I just want to give you a couple of examples quickly on some customers and what they are seeing. And a lot of these customers have gone through this journey with us. And one example is Falabella. Falabella is a Latin American retailer. They're a very big company. Now, what they did is they were having this problem that a lot of their customers were calling their regular call center, but they wanted to redirect to WhatsApp.
And one of the things they used Agentforce was Agentforce can work in any of the channels the customers are in. They turned on Agentforce, and really right now, they've increased. They're doing about 216k monthly WhatsApp conversations, 60% questions auto-resolved. And the real interesting thing is the adoption increase they're seeing. As I said, the stated goal is to move more and more to WhatsApp, and then they've got a 440% adoption increase just from August to October. And they're live in three countries, in Colombia, Peru, Chile, and they want to go a lot more. And that's a great question of somebody who's really seeing a retailer, a consumer agent, which is really answering questions.
I think, on Falabella, I know them very well. Actually, I met the CEO a while ago. This is the sort of the Nordstrom for Latin America. Correct. All corting glass for you.
And I think what is pretty impressive is they started with a proof of concept, and they've refilled the tank, as we say. They come back to us twice. And now it's a multimillion-dollar relationship just in the agentic part of the business. Super successful, super growing.
And most of their things is in Spanish. They want to add more languages there. Now, that's one sort of retail use case. Then if you look at Smarsh, Smarsh is a global leader in communication, data, and intelligence for regulatory industries. Very complicated use case with a lot of complex queries they get. They use Agentforce. This is where a lot of our advanced RAG and reasoning systems and how we do vector indexing. This is not like to make these answers very sophisticated answers. Again, this is the other example in the telecommunication industry.
They're seeing a 20% increase in customer success rates. They also tried to do it by themselves a couple of times. They tried it. They saw our system. Because there is a complexity that we can handle at an enterprise scale, and they're really seeing 20% increase, faster resolution, 30% increase in service productivity. This is like one another different industry, different case class of problem statement. So if you go to the next slide, Bouygues Telecom, French Telecom company, major French telecommunications company. They've been a Salesforce customer for 10 years. They have 10,000 field service contractors. They use our Service Cloud, our Field Service, Marketing, Data 360, MuleSoft. Existing Salesforce customer. Then imagine they all have all the data already in Salesforce. They really say, "How can I now change my thing?" Their average call handling time was two minutes before. They really want to improve that.
They used Agentforce for Service in the line of flow, and then they reduced from two minutes to 12 seconds. And then their accuracy, again, these are complicated use cases. And then they found a 95% use case. And then one of the things we also measure as a leading indicator is how many of their workflows that the customer has are agentified. So they're running about 3.5 monthly agentic workflows, and they call their agent Iris. By the way, this is another thing we are seeing. All of our customers, especially who are public-facing, they name their agent. Williams-Sonoma, we talked on the earnings call multiple times. They call their agent Olive. Almost everybody gives it a personality which is tied to the brand of the company. I personally think just like people have a website, going forward, they'll always have an agent which represents their brand.
It starts with one use case in customer support. Pretty soon, it goes to other use cases. And for all of this, again, to bring it back, the underlying platform is important. The context is important. Then you see another in the financial services industry. The financial services, PenFed is a credit union. They got 2.8 million members, $25 billion in assets. They wanted to do their loan underwriting reviews, AI-driven loan underwriting reviews, because that's, again, a complex regulated industry use case. And then they are finding that they can handle 10% faster handle time for reports, 75% of ITSM cases auto-result, and 30% projected cost in call centers. This is an example, again.
Now, if you really look at it between all the four examples, I just want to highlight a little bit of the last mile that Miguel has referred to is to do that, you need an underlying platform. You need the context, and context has to come from different data layers, different ability to access data, structured and unstructured, really reason it, tie it to the deterministic and non-deterministic workflows, really understands the jobs to be done, able to do not just getting live. Now, these are all public-facing, so they need their compliance, regulatory concerns, address. They need a lot of security, prompt defense injection, and all of that. And then day two operations. How do you monitor the agent? How do you eval? We call evals, but basically, it's testing and ensuring that the agents work they are. How do you observe them in production?
So this is what is happening. So I just wanted to give you a sense of how we are very close to the customers. And some of these customers work with our own FDEs. Sometimes they implement it themselves. Sometimes they're implementing mostly with our partners. So we're taking the feedback. And based on these early customers, we almost added 120 features in the product. So we are learning very fast, iterating into the product, and that's the journey we are in. So with that, Mike, back to you.
Great. Thank you both. So we are going to move to Q&A. We've got a number of questions coming in that we'll try and get through.
For those that joined maybe shortly after we started, if you do have questions, please submit them into the chat, the Q&A button you see there on the screen, and we will do our best to get to as many questions as we can. With that, let me first start. Miguel, this one's going to be for you. It's coming from Kirk Materne, and he wants to double-click a little bit more into AELAs and give a little bit more color on, and we've been getting this question quite a bit, on the impact of AELAs that they're going to have on net new AOV, how it translates from agreement into net new AOV and AOV. Then more importantly, or just as important, what you see coming on the horizon.
As you think about the second phase of the agreement, so they sign an initial two or three-year deal, what does that look like? And then what's the shape of AELAs looking like in the pipeline as well? Because you guys have talked a lot about the pipeline.
Perfect. Yeah, we're getting this question a lot. I'm very excited because I think people are understanding the power of the AELAs. AELAs pretty much cement the relationship that we have with our customers. So it's going to have a big impact on any attrition risk. Many of the clouds that they had disappear. Typically, it's a significant increase, step change increase in how we are monetizing the customer because this is the very important thing. In the SaaS world, in the CRM SaaS world, customers are using our product like a CRM.
It's a SaaS CRM and the typical use cases, and we've been growing nicely, and we added field service. We added Marketing Cloud, and we add 10%-20% to the way we monetize the relationship with our customers as they add new clouds. The Agentic Enterprise world is totally different. It's a time that is multi-trillion. And then when customers choose the Salesforce platform to transform all the processes to become the digital labor platform for all the transformation, the impact, the ability that that gives us to monetize relationship is a step change. It's a multiplier effect. It's not anymore 10%-20%. It's times two, times three, times four. In the investors' day, we talk to you about times three, times four. We're already seeing it with a lot of customers.
Obviously, an AELA is already, in most cases, double or tripling the business that these customers have been doing with us for 20 years, and all of a sudden, in one year, because they want to become agentic enterprises, we put in front of them 10, 15 use cases, they go in, and then they double the spend with us, or they triple the spend with us. I mean, I presented Vivint as an example, or Finnair as an example at the investors' day. Those customers started, solid customers that were in the single-digit million relationship with us, with multi-cloud, very happy, and then agentic enterprise came. They thought, "How can I transform? Should I go to this vendor? Should I go to this vendor?" They all realized that they needed the last mile that Salesforce provided. I already explained the last mile, the differentiation.
That's our moat, and they all bet in on us. They started with the proof of concept. We came up. I mean, I love the names of how our customers are giving personalities to these agents, but in the case of Finnair, Sisu, Sisu, which means resilience, is the agent that they put in production, and now many travelers that are stuck in airports and have issues, they call Sisu, and Sisu resolves all the problems, and Sisu has been so successful that the volumes of actions that Sisu is taking per week has multiplied by, I think the number is by five just in the last few weeks, so they went into an AELA with us, and Finnair, which was a stable company, in just a year has more than doubled the relationship with us, and this is just for a few use cases.
So they have many more to come. Vivint is the same example, home security, smart home solutions. Randy was with me on stage. He's the head of engineering. He's really technical. He baked us off against all the possible agentic enterprise layer competitors. They chose us because he said, "I'm going to choose you because you have the data, you have the humans, and you have the deterministic workflows that we want to execute on." He piloted. He launched three agents with 20 or 30 use cases for every agent. Mega successful. Again, another 10 times increase in volume of actions taken by the agents. And he said, "Okay, I'm going in." And then he did an AELA, and we more than doubled a very large relationship that we have with him. Over 10 years, we doubled it in just 12 months.
This is happening to every single one of our customers. The second part of the question is, "Okay, now that you have the AELA, you have the visibility." It's a partnership. It's a shared risk. Okay, we take some risk because I really want the worst case that can happen, the worst case scenario for us in an AELA is that the customer is so successful that they deploy 100 agents, that they consume a lot, that we have to hit the LLM a lot, that we have to ingest a lot of data, and that the cost to serve of those agreements may be high. Guess what? The renewal comes. The customer has already developed 50, 20, 70 agents. It's consuming a lot. Those agents will need to consume even more in the future, and there will be another 50 or 100 agents.
So we will recut the agreement, and we will make it, again, shared risk. But we are very confident that the profitability of these agreements are going to be very high. So this is going to be a cornerstone of our strategy. For me, the message is this new time that we've been asked to participate in is a new sport. We are now playing into a different field, and it's significantly much larger. And every time that we get one of our customers, SaaS CRM customers, into the agentic enterprise, a new sport, essentially, they double, triple, or quadruple the business that they were doing with us, which is very exciting. By the way, they are very excited because they use our software in incredible new ways. I mean, the conversations that we have with these customers when they talk about their Vivint is Ava, then Sisu, then Olive.
It's very exciting. You're going to see a lot of household names. In five years, everybody's going to be talking about the names of these agents for every service, and there's significantly more to come. We have 18,000 customers. Nobody, nobody. Please ask other companies, "How many customer-facing agents have you sold? Tell me stories." They will give you two, three, 10 stories. We have 18,000 stories and growing. By the end of the year, we're going to be close to 25,000 to 30,000 stories. Okay, and we're going to start the year with those customers coming back and refilling the tank. I mean, I was in Q1, if you remember, I was very excited because I found three customers. We had at the time 3,000 plus, three customers, obviously. Most of them had bought in Q4.
In Q1, three of them knocked at our door and said, "Okay, I need more credits. I need to refill the tank." And I was very proud. Well, this quarter in Q3, more than 50% of the bookings that we did with Agentforce, but also with Data Cloud, came from customers refilling the tank. There were 362 customers refilling the tank. Okay? So as the install base of Agentforce customers grow, the number of customers coming to us refilling the tank is going to exponentially grow. And this is the, I mean, this is a panacea. This is the world of consumption where, I mean, the sales cycles become very short, where AI productivities go up because they don't really have to do much. The digital labor is already working for them. And then the customer calls us, "Okay, I need more credits.
I need more fuel for the tank." Anyways, very exciting.
Thank you, Miguel. So we've got a flood of questions coming in. This is great. I really like this next question from Terry Tillman, my friend from Atlanta. And this one's going to be for Srini. And I personally, I like it because we've spent a lot of time as a leadership team talking about the importance of this technology as we continue to advance Agentforce. So Srini, could you give a little bit of color and introduce, maybe for the folks on the call that haven't been as close to it, the voice innovation that we've been injecting and recently launched into Agentforce and the relevance of AgentScript as well?
Yeah. Thank you, Terry. Great question. So we've been working on voice for a year. We GA'd. We did a lot of pilot customers. We GA'ed at Dreamforce.
Now we have a lot of customers who are trying it. I think the critical thing here to understand is, one is voice is new, right from day one. We realized when we built the architecture, one of the most important things is the agents have to work in different channels. I gave you a WhatsApp channel as an example at Falabella. It could be WhatsApp, SMS, voice, web, embedded in other agents like ChatGPT. So it has to work on all channels. What customers do not want to do is redo it for every channel. Because do you realize that it's very hard to get all your data right, put all the guardrails, and do it, and then imagine reproducing it?
So one of the big advantages of us on Agentforce is customers, when they try to open up in one channel, it's just switching a switch and enablement, and then it'll work for voice too. Because the same logic, the same prompts you have given, same reasoning, same knowledge bases, everything the voice agent will be able to use. Because what drives the voice agent is the same reasoning engine that drives the chat agent, the WhatsApp agent, and all. So that's why voice is there. Hopefully, we cannot share. We haven't gotten permission from these customers to share their names. But we have a lot of customers. But hopefully, by next earnings call, we'll have customers who we can publicly reference as voice. Tied to that, you asked about AgentScript. One of the learnings that this is important. I'll keep repeating to that.
We are working very closely with the customers. We are working. We are hand in glove. We are trying to learn what they're doing, what they're doing, FDEs are doing, our partners are doing. One of these things, and I think if you'll realize this word I use called, what we have realized is people are writing prompts. They say, "Do this. Don't do this." They keep the prompts keeping longer and longer. And then the LLMs are great until some point, and then they get confused. And so what we saw was our developers, our engineers, or everybody, our implementers spending a lot of time in what I call a prompt doom loop, where it's as though we forgot in engineering the regular programming. So I think it looks like a hammer. Everything looks like a nail because I have a hammer.
So what we said is, "Hey, there are a lot of things. The LLMs are very good. Let's use them. There are a lot of things where they're not good." So if you really want a prescribed flow where you always want to do some authentication, LLMs do it. When you give the instruction, they don't guarantee it. In a B2C scenario, maybe 95% accuracy is okay. In an enterprise scenario, they want 100%, the standard operating procedure. And then what we found is, "Hey, there's a much easier way to do it." So we introduced this AgentScript, which says, "Hey, let's use the power and creativity of the LLMs where you want and the determinism of the regular script or regular programming when you don't want that." And in an easy way so that your time to implementation gets less, your testing cycles get reduced.
So I think it's almost you have to think about it is AgentScript. Just like voice is new channels, AgentScript makes the entire agents much more resilient for enterprise use cases, but also makes your time to test and go live much shorter. That's why it's very powerful.
Great. Thanks, Srini. Next question we have is coming from Mark Murphy and team. And we're going to double-click into the kind of the do-it-yourself dynamic that we've been seeing because I think it's a really important dimension to our ramp of Agentforce. And the question really revolves around customers who may start out down the do-it-yourself path and then end up coming back or boomeranging back to Salesforce in the end to adopt Agentforce. But I'll ask both Miguel and Srini to chime in on this one.
But can you guys provide some color around what you're seeing in the customer behaviors? And then just as important with that, what's the time to value that you're seeing with the customers? And what are some of the things, maybe for Srini in particular, what are some of the things we're doing to help accelerate that time to value?
Yeah. So the good news is, actually, I don't like the word boomerang because it's not that they leave Salesforce and then come back, which is sort of the boomerang. It's just that they believe that they can build the capability without Salesforce. And then later, they realize that they need to do it with Salesforce. So first of all, the good news is, and this is very important, I keep referring you guys to the huge opportunity of the agentic enterprise.
Every single company in the world, I mean, last quarter, I was in 12 countries, three continents. I met 400 customers. I had conversations with 400 customers. Probably it was 100 one-on-ones, and then every single one is experimenting with multiple technologies. In different domains of the company, they use different technologies, so obviously, the one domain where we really want to own and really grow with our customers is the customer domain, but even in the customer domain, there are many customers. I mean, we have 18,000 Agentforce customers out of 200,000, basically, so it means that the other 190,000 customers today, they're experimenting with something else, which, you know what, is huge news because they know what they want. They are going to hit the wall because they're going to realize that they don't have the last mile.
I'll give you a very quick example, and then maybe you can also add to that. Huge bank in Europe. I'm not going to go to the country Europe, otherwise, it's because it's the biggest bank in that country. They're a great customer of Salesforce, 30,000 Financial Services Cloud licenses, 8,000 Service Cloud in the call centers. I mean, obviously, many double-digit, healthy double-digit million of AOV with us. And a year and a half ago, they started experimenting, and somebody had the great idea that they could do this with Microsoft. And then they took all the CRM data from Salesforce. They went to Azure. They put it there. Then they used Copilot to get the logic. And I think Microsoft put like 30 engineers to work on that for one year.
They didn't get anywhere because what they built was disconnected from what their 43,000 employees of this bank were doing every day, triggering workflows. This bank, for instance, they have more than 1,000 different flows that have been codified in the Salesforce apps, which are automations that the humans are triggering every day to the tens of millions of automations triggered by these humans every month. They built something that was disconnected, that was super heavy, that was very costly to maintain. Then at that point, obviously, we have a great relationship. We say, "Guys, we can do this.
It's embedded where the humans are with the best technology, with Agentforce, with Data Cloud bringing all the information from the different units together." And they say, "Okay, let's do it." We put three, not even FDEs, solution engineers, and they built the same but embedded with the humans, with the workflows in one month. And then a month later, we signed a double-digit, double-digit multimillion agreement with them to add to what they were doing. And that was just the beginning. Now we're talking to them again to double that because now they want basically all these capabilities to every single employee in the bank. And by the way, they love this other provider for many other things. But it doesn't make sense to do it yourself when you are in the customer domain.
Now, if you want a solution for some supply chain or whatever, well, we were not a player there. By the way, now we are because we bought Reguerlo. But my point is, there is a lot of experimentation. This is demand that is going to come to us. It's the best thing that can happen. 100% of the customers are going to become an agentic enterprise. Who are they going to choose? Listen, I think most of our customers are going to choose us. And what I said earlier, this is very important. When they choose us, it's not that our business with them is going to grow 10% or 20%. Our business with them is going to triple or quadruple. So do the math. Of course, it takes time. We are first educating our thousands of new AEs that we are adding to our go-to-market.
Then they have to get the face time with them, with the customers, be in front of them explaining the concept of the last mile. And then the customer needs to make a decision. And then we need to pilot. And then we need to find the success. And then they go big with an AI layer. And it takes time. But we are seeing this accelerating like never before. The testimony of that is the pipelines. We've never had this size of pipeline, very healthy double-digit growth in pipeline, in open pipeline in next fiscal year. So things are moving in the right direction.
So I think Miguel answered most of the questions. Just a little bit more specific context is, like I said, some of our most advanced customers, most forward-leaning CIOs, I would say, who are ahead of the curve, they're always innovators. They started two years.
So they went through all the experimentation. They're more clear on what works, what doesn't work, what is the cost. They realize that there are things which are not worth for them to solve. That's why you need a platform. This is the same, why do you buy a platform versus why do you want to build yourself? I think they also got fed up, including me. I'm also an engineer. I'm a practitioner of whatever I do. I'm also writing code with my engineering teams. I really know what works, what doesn't work, where does the limit. I think they learned it. They are much more clear about what works. At the same time, by the way, like Miguel said, they have multiple agentic initiatives. One of the other things which really helped us across the platform, we standardized on open standards.
Right from the data lake layer with Iceberg, right from MCP, different models. And now with AgentGraph, MuleSoft AgentGraph, like where you do, we support A2A. So it allows them to say that, "Hey, I can build specific domain agents." Even including our observability with OpenTelemetry standards and stuff like that. So because a platform is open at every layer, now these customers are saying that, "Hey, for these domains, it's not worth me trying to build. I'm going to use it." But one of the things we want you, Salesforce, is if I want to call your agent, for some reason, let's say I built it on AWS or Azure or my custom Google or something, can I talk to your agent? And that's what MuleSoft AgentGraph is.
I think one of the most resonating things which I found from these enterprise CIOs who are a little advanced is they already see the future, this multi-agent orchestration. One of the most important things they glued on right now is MuleSoft AgentGraph because it allows them the federation. They don't need to do things which they don't need to do. They get out of the box templates and agents, like we said, for each of the verticals with specific domains. So they don't do the heavy lifting when they don't need to do. They will definitely use their teams bandwidth on specific uses which are unique for them. So we enable this multi-agent world with open standards. That's what we are seeing. I think some of the other people who are a little late to the game, they will come in six, seven months.
They'll learn that, "Hey, it's not the day-one problem." When you go show a good demo, it's once it's in production and day one and day two because these things degrade if you don't do it. There's a lot of work. Just like a human, you need to performance manage them. It takes a lot. This is what we are learning with help.salesforce.com too. They realize the overhead is not worth it. I better depend on a platform. So I feel that's what we are seeing. And I can see that going more and more.
Perfect. So we've got a number of questions coming in. I'm actually going to do kind of a twofer here. And I'm going to jump down a little bit and then come back and combine a couple of questions. So this next one is from Tyler Radke, Citi.
I'm going to take the first half of this question where he asked about the net new ACV growth statement of net new ACV being higher than ACV growth in H2 and what the comparison is on Q4 versus Q3. We obviously haven't disclosed Q4 versus Q3. We've been vocal about Q3 being strong. But the forecast and how we come up with it obviously is based on pipeline and our projections around expected bookings in Q4. So that also feeds our CRPO guidance for the quarter. So that's kind of the way I would frame that. The second half of Tyler's question, I'm actually going to combine with Michael Turrin's question from Wells.
It really revolves around the promise or the visibility we gave everyone at Investor Day around the uplift that we're going to see over the long-term horizon AR, AOV, synonymous, and what adoption looks like within customers for Agentforce. We go from first use case, second use case, third use case. Miguel laid out obviously a slide earlier that we consider to be very important to how we land this with customers on introducing a number of agent use cases. Maybe we'll start with Srini and Miguel. I'm sure will chime in. Maybe Srini, can you give some insight into how you approach the deployment for deployed engineers? Obviously, it's become an important leg of our strategy in trying to drive that.
And then, Miguel, maybe if you can expand on that, talking about then what the conversation becomes with the customer and expanding to the second, third, fourth use cases.
Yeah. So, I think, let me also. There's a lot of hype around the term forward deployed engineer, like what it is, what it is not. So, let me just demystify some of this. When a new product comes, we always used to do that. We'll have a small team, which will work initially with the initial we would call them pilot and then have the engineering teams work closely to mature the product. Basically, in the world of agentic enterprise, so much of the underlying swell is happening even in the underlying technologies. We wanted a little bit bigger investment to iterate. So, one key role of our forward deployed engineers is to mature the product. Okay.
So that it's easy for customers to implement, get the feedback, iterate it, which I would call them as product FDEs, whose main job is to give the feedback to the loop, give feedback to the product engineers, what's happening on the ground, really iterate fast to mature the product so that we can scale it because we have 200,000 customers across so many countries, and then part of doing that also is work with our partners, SIs, to really ensure that this agentic transformation is like it's a slightly different model, so I think we are working with standardizing the playbooks and all for our customers, so as you see, now what was interesting for me is of the thousands of customers we have live, initially, maybe eight months back, almost every implementation we were involved.
Now, a lot of times, I'm finding that this customer is live and very big usage, and we are not even involved, which is where I want to be because I want to mature the product so the cost of implementation can be, first of all, A, the customers could implement it themselves, or any of our partners can implement it while we are improving the product. So I think they're structured. And at some point right now, for the initial customers, our aim is adoption and maturing the product and tracking it. Some of this, we are bundling. At some point, if you are in AI layer and all, we are going to be part of the package. And maybe at some point, we will also charge for the FDE motion. We are not there yet, but I think that's what we are doing.
But my main goal is to really mature the product where we can really iterate it, and then we get all our lean on our partner ecosystem. And in fact, we are working very closely with a lot of our big partners like Accenture, Deloitte, KPMG, and others, and across the world, specialist partners to really scale this so that they can take it. Because to really deliver this agentic transformation in the time, we can't do it alone. We really need our entire partner community. And we are having regular meetings. They're part of our training. In fact, we're running FDE bootcamps where the partners are coming with us. So I think this is going to be a whole of not just Salesforce, but their entire partner ecosystem. Another thing I just forgot to tell you is because of these open standards, when we say partners, it's SI partners.
But a lot of these agents, I think if you remember what Miguel has showed on the second slide of all the different agents, a lot of our ISV partners, our independent software vendors partners, they will build just like AppExchange. There'll be an agent exchange. They'll be building a lot of the last-mile agents on the platform. And we are working with a lot of them. And they will build those actions and agents. We already announced at Dreamforce hundreds of actions through our ISVs. And I think as the platform is maturing, we're taking the feedback. And the whole cycle will repeat.
In fact, in the point-of-view slides that you saw, a mini version just copied and the bigger slide. But essentially, when we go to every industry and we show the 150 agents that we need to deploy, we actually codify every agent.
And we said, "These 50 are embedded already in our platform out of the box. These 25 come from our ISV ecosystem that we've already certified them. So they work on our platform. And then these other 50, you need to build them yourself. But this is how you build them. This is the data that you need, etc." So partners are fundamental to really accelerate this revolution. The demand is going to be huge. Every one of our big partners, from Deloitte to Accenture to all of them, they are getting ready with massive hubs with experts. They're getting all certified on the Salesforce platform, the Agentforce, the Data 360, and our apps. And I think one to finalize with the question is how fast people go to double, to triple, to quadruple. It actually depends.
It depends on where the customer is in their mindset, their conviction on how much have they experimented. What I can tell you already is that we've seen dozens of customers, probably hundreds of customers already that they've doubled, but they've doubled a successful relationship that they had with us for 10 years with multi-cloud and in just one year for an initial set of use cases, they've doubled the spend with us, which is a great indicator that probably they're going to go three, four, five times. I mean, there is one, Grupo Ficohsa, for instance, is an example of a financial services company in Central America. They just went five times in the first shot because they saw it. They want to go fast. They want to be differentiated and basically, their relationship with us has multiplied by five.
So this is like a step function for our business, also for our partner business. And my goal, listen, is to move very fast to get as many customers to adopt our platform, to become agentic enterprises, and to do it with full commitment, with an AELA. They can do pay as you go. And then we're going to see the times two, and times three, and times four is going to take longer. And of course, the very big accounts, we have a lot of accounts that pay us more than $100 million. We have a lot of accounts that pay us more than $50 million. Those will take a bit longer to multiply by four or by five.
But some of the wins, when I look at the top 10 wins, and this is a cool statistic that I would like to, if you don't mind, share with the team here. So if you look at the top 10 transactions that we did in Q3, just order of magnitude, those included more or less $105 million of net new ACV. And if you look at the TCV, so what is committed in the contract, approximately more than $1 billion. Okay. The 10 transactions, basically in our RPO, it shows basically more than $1 billion. Well, in those transactions, in the ACV, seven of the 10 transactions were driven by the agentic enterprise transformation with Data Cloud and Agentforce, seven of the 10. There were others that were single cloud that they wanted to expand. But seven of them, which is great because it's seven of the top 10.
When you look at how much did they bought of Agentforce and Data Cloud, actually, they bought quite a bit. 30-35% of the ACV was Agentforce and Data Cloud. The rest were our core clouds. In the total bookings, it was less than 15%. 85% were our core clouds. What this means is, number one is Agentforce and Data Cloud are prevalent in our biggest deals. Customers are accelerating their multi-cloud transformation because of Agentforce and Data Cloud. So Data Cloud and Agentforce make all our clouds better. That's why Marc continues to say, which is true. Sales Cloud is no longer Sales Cloud. Service Cloud is no longer Service Cloud. Marketing Cloud is Agentforce Sales Cloud, Agentforce Service Cloud, Agentforce Commerce Cloud, Agentforce Marketing Cloud.
Yeah. Well, thank you, Miguel. Thank you, Srini. With that, we're at time.
I really, really appreciate the participation today and the interaction. Questions were great. If you haven't gotten enough Miguel yet, we'll have Miguel on stage at the Barclays conference next week with Raimo. And then I do have an ask for everyone on the call. If there are what other topics you all want to hear about, we have a quarterly session of this going on. And so we're always looking for new topics to bring you guys more insights into what's happening in the business.
I know we are up on time. But there was a question about commerce, Commerce Cloud. And I think I want to address it because I want to leave it hanging. Yeah. So we totally transformed our Commerce Cloud offering. And the question was about how are you doing to differentiate it? You seem to have lost market share, deceleration.
So we've actually spent the time innovating and building a stronger Commerce Cloud. And the basis of our stronger Commerce Cloud is we made it headless. Most of the other options are also headless. We've added a very powerful order management platform around it, which is that business is growing very fast. Very important. We made it totally agentic. So it's not Commerce Cloud. It's not Commerce Cloud anymore. It's Agentforce Commerce Cloud. So now you're going to have a shopping assistant agent on everything that you do. We've added a point of sale solution, very modern point of sale solution that is growing now a lot from a small base, but it's growing significantly. And then finally, we have connected it much tighter with the other clouds.
So listen, if you want to just buy a standalone Commerce Cloud for a website, probably we're not the right option for you. If you want to build another touchpoint in your customer engagement, connected with marketing, connected with service, connected with Agentforce, we are the obvious choice. And that's the big deals that we're winning on Commerce Cloud. By the way, Commerce Cloud was one of the fastest growing clouds in Q3, also for net new ACV, but of course, of a lower base than the other clouds. But I'm very excited about the future of Commerce Cloud.
Great. Well, thank you, everyone, for joining. Appreciate it. Have a great one.