Zuora: What's New, What's Next for May 2026

Perfect. And so before we get started, and before we get into today’s content, I wanted to ground us in our strategy. Obviously, you know, AI is changing the way in which we all do business. Zuora’s included in that as well. And we’re really looking at our AI strategy in three folds. Right? The first is helping our customers monetize AI, right? We’re seeing a lot of different revenue models that you all want to be able to go to market with, both on the sales assisted as well as the PLG side. Right? You want to be able to capture every token, every credit. You want to bill for any model, right, and have the flexibility to iterate and change. That’s what exactly what we’re doing. We’re launching a number of different revenue models, whether that’s on the prepaid side that includes

tokens and credits and units, as well as things like commitments to be able to support those revenue motions. But AI for the sake of AI is not enough, right? We know that there are a number of different customers and personas that operate day in and day out in Zuora. And so as we look at that middle bucket, we really want to supercharge your roles. We want to be able to power the quote to cash pros- process. You know, being able to not only utilize AI in app, but also build agentic workflows through our MCP. You’re going to see, you know, a whole lot more innovation today as it spans the platform. Agents that are built within the quoting process, within revenue, uh, within our product catalog,

as well as the skills that we’re building within the MCP, to really power your teams to move faster, to automate more, and to be able to really supercharge, right, the entire quote to cash process. And the third is, how do we utilize AI to accelerate that time to value, right? We’ve have products that and, and continuous iterations that you all have when you are working inside of our product… front and center as well as our customers, and all of this built on, you know, trust, right, a platform that’s enterprise grade, that’s auditable at the end of the day. Right? And so with that, and s- we go through today’s innovations, you’ll see a lot of these themes pop up.

You’ll hear from Luning and John about how we’re supercharging, you know, our revenue motions to be able to monetize AI. You’re going to hear from Kevin and Richard, um, on what those agents bring and how we’re doing, um, on the, the revenue side, bringing some of those platform capabilities to really extend not only, um, workflow, but deployment manager, um, be able to help with revenue reporting, um, to help you go live in weeks. So with that, um, Sabrina, if we can go into our solutions that were released in Q2, I will invite Errol on stage. Um, we can just move forward and get into the content. Sabrina, um, I’ll invite- So I’m excited to kick us off and actually

cover the first enhancement that will enable you to more effectively handle AI tokens, credits, and units themselves. So, as we previously shared, actually on the last what’s new, what’s next, uh, we are currently in beta with features and entitlements. So again, for reference, a feature is a product capability, such as seats, tokens, or even premium support. And then, as you associate that feature with a plan, it becomes an entitlement. So for example, bronze, silver, gold may allocate five, 100, or 550, or 100 seats. Or if you think about tokens, it could be a million, five million, and 10 million tokens.

So the key update that we’re covering today is that we’ve actually updated this capability with even more advanced metrics, uh, as well as the associated polic- as well as managing some of the associated policies. So again, when you think about tokens and, and, uh, AI utilization, when you ach- hit the end of that specific tranche or allocation, exactly how are you going to manage that customer experience? You can throttle them as they go over. Uh, you can jump your customers into an overage policy. You can even give them a little bit of a grace period, uh, so that they have an opportunity to actually update, uh, some of their entitlements and feature policies.

So again, we’re currently in beta. We’re working with several of you already, but we would like to understand and work with more of you. Uh, what are some of the granular policies and entitlements that you would like us to in- include? And again, this isn’t just about AI. Uh, if you’re using it for, say, IOT ecosystems, um, we look at events at a sensor level, uh, or even more granular, uh, just allocation and tracking of your individual features. Uh, so please reach out to us. And with that, I’m now going to hand it over to John. Hey, thanks, Errol. All right. So we’re gonna pull up the CPQ slide here. Um, so everyone, we’ve been… These

are four highlights that we want to share. Uh, so the first one being calculated charges, you may have heard about this in the last webinar regarding, uh, billing’s ability to define a charge that is based on other charges with a percentage, uh, as well as min and max. So that will now be brought into the CPQ space. Uh, as well as a, a commitment feature, which we’ll hear more about from Luning in a minute. Uh, but the ability to do both post-paid and prepaid commitments, uh, within CPQ is going to be supported.Uh, and fully aligned with the billing process and how the commitment gets evaluated downstream. We’re a- additionally, we’re introducing opportunity product sync, a long-requested feature that is native to CPQ. No customization, no custom code required. Your admins will now get a, uh,

a settings page configure exactly… We seamlessly integrated with the existing quoting experience and the native object, uh, for opportunities and opportunity product line items in Salesforce. Lastly, all of this with the Quote Studio UI refresh, giving new color, new styling, as well as, um, a more seamless experience around selecting and manipulating charges. Uh, all of this is already available. And then we’re releasing some additional features that aren’t included in this, including suspend/resume, uh, CPQ AI, which you’ll hear more about a little bit later, as well as support for pending charges in CPQ. So with that, I’ll pass it off to Luning to talk more about commitments. Thanks. Thank you, John. Um,

hi, everybody. Uh, this is Luning from billing team. Uh, the first feature, uh, we want to talk about is, uh, a new revenue motion, um, we introduced. This is a new capability for you to manage and for you to create and manage the commitment. A commitment is a spend obligation, so it’s designed to secure a revenue because our, um, because the companies would like to sell everything, for example, the seats, tokens, and services in a bundle, and, but the, the consumer, the customers, they would like to pay what they use, but their consumption can go up and down. This makes the revenue forecasting really hard because it’s unpredictable.

So this feature is designed to secure the revenue because the customer can sign a minimum spend obligation, and this, um, commitment can be either a prepaid, meaning you generate a prepayment invoice and ask and collect the payment from the customer upfront or over a instrument, or it can be post-paid, meaning the Zora will automatically, during the bill run, the Zora will automatically evaluate the actual bi- billed spend versus the committed amount and then generate the true-up invoice, if any. Um, and we also allow you to manage the full, uh, commitment lifecycle,

and so you can do a price up- update, cancellation, et cetera. And you can also set the priority, uh, and you create multiple commitment, you set the priority. So we will, uh, follow the priority and to contribute each commitment one by one. And you can also track e- the, the spend against the, the commitment and, uh, choose to send the threshold notification, um, for, for you to make the call to either cross-sell or upsell or notify the, the end customer. And you can also adjust the commitment balance through the credit memo, uh, in a credit-back scenario. And this, uh, new object is sitting directly under customer account with the full audit

trail supported, and this commitment, uh, as said, is cross, um, all different type of charges. For example, one-time, recurring usage, the prepayment charge, including, also including the dynamic usage charge. So you can define this, uh, on the, on, uh, a- at the account level, and it can apply across multiple account and multiple different charge types. Um, and we provide, uh, both API and the UI and all kinds of queries to support you to manage this. Sabrina, can we go next slide? Yeah, this… The next slide, it’s… The

next slide is… Because we need to catch up with the market and offers, uh, the, the latest, for example, the customer want to sell the token and credit packs, and they have really flexible contract with their end customer. So we made the following enhancement to the existing… Totally decouple the fund, a validated period, with the service charge billing period. For example, you can make the validated period longer, shorter, and it’s not, uh, it, it… Then the billing period, it can also, uh, it’s not i- it can align or not align with the billing period. Those are fine. And if you add the prepayment

in the middle of the subscription term, meaning the, the fund start date is not aligned with the subscription start date, that’s fine. We will, we have the built-in proration option for you to prorate the partial period. It can also support, um, natively the overlapping multiple fund and, uh, manage the drawdown priority, and we also enhanced the, the rollover options on the prepayment, and we also, uh, improved the, the cancellation handling. For example, through the cancellation, you can-I

think loading may be just froze for some folks, so apologies for that. Um, y- what, uh, I think where, where we left off and what we wanted to convey is that there is a number of, uh, enhancements that are coming to the prepaid drawdown feature that sits within our advanced consumption billing product. That includes things like decoupling the validity periods and the billing periods so that they’re not… the validity periods are not tied to the billing th- itself. We also have s- are going to be supporting more flexible proration options, right, and that includes options for prepayments. They have a number of user enhancements as well that are coming. That includes being able to track that fund balance, uh, through our APIs, as well as being able to see a lot of that

within their given, um, balance, right? And so these enhancements are coming in the, uh, June and July timeframe, right? Um, it requires you to have the, uh, the advanced consumption, um, billing module, and we’re really excited to be able to support more flexible, um, tokens, units, as well as, um, the number of ways, as I mentioned earlier, of customers being able to monetize AI. Um, and with that, um, I believe my next transition is to bring up Jonathan to talk about a really, um, exciting release of customer experience. And so, thanks, Jonathan. Thank you,

uh, Nat. All right, so do you want to go to the first slide? Yeah, so, um, l- let me walk you through Zoro Experiences. Um, I’m just going to do top level. At the core, uh, Experiences is a, a platform, uh, for you to build subscription commerce experiences that really let your customers, your internal teams, maybe your channel partners, um, uh, do business, uh, you know, wherever they’re already working. Um, there, there are two ways just to frame up, um, uh, how these experiences materialize. There, there are two ways you can, uh, use Experiences. The first is, uh, is embedded. Uh, you build, uh, and drop in components straight into the systems

your teams already live in, s- you know, Salesforce, uh, Zendesk, uh, HubSpot, for example, whichever CRM or service desk, uh, your agents have, uh, open all day. Uh, they get live Zoro data, live transactions right inside their existing u- uh, UI. I’m going to talk about how that happens in a demo in a second. Uh, the second mode is standalone. You can spin up full customer portal, check out, uh, back office view, uh, by composing co- components, which are the building blocks, into a template. Uh, things, for example, like, uh, view, amend, uh, and buy, all running off, um, a Zoro context, in this case ca- that would be catalog. So you get a complete storefront or a customer portal

without needing another vendor in the mix, and you can host it anywhere or you can let us, uh, host it for you. So going to the next slide. Okay, so let me, let me just dig in a little bit more, uh, into what does a subscription commerce experience actually, uh, look like in practice? Uh, I guess you’d think about, um, two axes that I’ve put here. O- on one side, you’ve got who’s using it. Uh, at the top, you know, subscriber doing self-serve. You’ve got a support agent helping a customer, um, a channel partner managing, uh, their own book of business. And on the, on the left-hand index, or the left-hand side, you’ve got, um, what they’re trying to do. Uh, they want to view and update something. Uh, they want to amend something in, in billing terms,

that’s when a contract is… the subscription contract is changed, or they want to do a purchase. So, for example, a subscriber on a- on self-service might log into, uh, their subscription portal, check their invoices, look at their usage, update their payment method. Uh, they might want to add on or increase usage limits, pause, uh, downgrade, renew. So all of the kind of actions that you would expect the customer to be able to do. Or they want to buy outright, so a full commerce product display page. Uh, you know, buy credits, buy… uh, take out a brand new subscription. Um, a support agent does the same set of actions, but on behalf of someone. So they see billing data inside Zendesk, they amend, uh, the contract, for example, while they’re on the phone. They take a card, they sign someone up while,

uh, customer’s still on the line. Uh, and I guess a- another example might be a channel partner, uh, sees their customer’s order history. They manage those accounts and subscriptions. Um, it runs embedded, um, uh… you know, you can run embedded shopping flow for resale. Same components, different audience, different context. Um, so next slide, please. So Experiences isn’t just a, a builder. Um, it’s an impressive builder, which I’ll show you in a second, but it’s also, um, a platform. And this is, this is the difference I think that really matters. Platforms what actually gets you to enterprise grade. So this is everything around the builder, and there are four things that we, we focus on here. First is governance. You know, identity, role-based access, uh, page and element level gates, server-side

checks, role-level security. And the focus here is on, um, your compliance team. The second is scale, and by scale, I’m, I mean many teams shipping into one production environment without standing on, uh, each other’s toes. Uh, Git-style branching, conflict rev- resolution, multi-environment release, et cetera. Designers, content teams sh- can ship in parallel, which is important for large, uh, teams, uh, in go-to-market. And the third, um, area is measurement. Uh, key for these types of front-end experiences, everything’s traceable, analytics, A/B multivariate tests, custom segments.Every change that you ship inside that experience is with its own trace. So you have the auditability that you need. And then actually, th- the other

thing that we think a lot about is velocity. Uh, and I’m gonna show you a little bit about velocity in a second. But, you know, how do you build templates that are reusable across business, uh, units? Uh, AI augmented authoring for fast, uh, delivery. And, and so business users can go from idea to a live page, uh, in a very short period of time. Your engineers stay focused on product instead of building out, uh, checkout flows. Um, so let me just go to the next slide. So ju- just where this lands, uh, and how we think about experiences enabling, uh, you know, more growth, uh, better business processes for you, um, and more efficiency. So four things really. One is less custom development. Uh, no more bespoke, uh, portals. No more one-off CRM screens. Engineers stay,

as I said previously, on the product, not rebuilding stuff. Uh, two is less data syncing, so Zuora stays the source of truth. You’re gonna see something in a minute where a component is building itself reading live data, which means fewer, you know, pa- pipelines to maintain, less, less drift, uh, less audit risk. Uh, nothing gets out of step. Three is faster iteration, which is kind of table stakes today, minutes from idea to live page, especially when you kind of pair templates with the experience, uh, builder agent. You can build very rich, uh, customer experiences, both for your internal and, and, uh, end users, uh, in minutes. Business users can ship, uh, importantly without the IT bottleneck.

Um, and then the last is, is, um, you know, it replaces th- th- this idea of legacy portals, um, other vendors in the mix, uh, you know, more stuff on top of Zuora. And so, uh, and it gives you this, this kind of craw- crawl, walk, run, um, mechanism where you can start with My Account, um, but evolve into, you know, full, uh, self-serve, uh, if that’s the flavor you’re looking for. Uh, let me just go quickly onto the next slide. Uh, identity, I’ve just called this out because identity is a core part of any experience. So experiences, it, it quietly does a lot of lifting under the hood. Every experience, uh, you build inherits a complete identity access and, and lifecycle layer. You don’t have to rebuild, um, kind of authentication on every deal. You get registration

and activation built in, account creation, um, activation of emails, email verification, all the richness around MFA that you would expect and s- and session, uh, management and sensible lockouts, password, uh, self-service, which is, um, key, multi-account context. You know, what… for example, one user could be linked to many Zuora accounts. The active context persists in their session, and, and the switching that they, they’re able to do is instant. This is good for, especially for the CRM use case. Um, role-based access with policies, uh, is key, um, and things like admin user management. Admins create, deactivate, assign roles, link accounts. Every action, uh, is audited, and, and, and that obviously is, is, is, um,

you know, partly what I was referring to in the, in the platform. Um, let me just, uh, finish up on the last slide, and then we’ll go into the demo. Um, I just wanna, uh, talk, you know, talk about time to value, uh, the experiences agent. This is the same shape as our Zuora agents. You’ll becoming familiar with these persona based agents. This is specialized for the experience pillar. It does three things. Uh, it designs, actually understands what’s possible across, you know, storefronts, portals, embedded back-office views, um, you know, user aware flows like checkout, and, and it picks the right patterns and components for what you’re trying to build. Um, it translates, um, uh, you know, you give it a, a business ask, which is again, table stakes today. I want a self-service storefront plus a My Account area, for example. And it

will run, build, uh, run the build to release it, um, things like data sources, the templates, the widgets, integration points, and it will execute that, uh, guide you, um, it’ll tell you what it’s doing. So it guides you through what the steps that it’s taking, um, does a best practice implementation, um, with… uh, uh, and that means less trial and error, and you go from kind of storyboard to live in a very, uh, short period of time. Um, so what I’d like to do now in just the last two and a half minutes is just show you a demo. I’ve asked one of our engineers to r- to narrate this. Maybe if you wanna just expand that as well, so that everyone gets a good view. Can you hear the, the volume on that? Do

you wanna, do you wanna maybe go back, and I’ll narrate this as we go? Can you… can everyone hear that? No. Okay. Let, let, let me narrate this as it goes. Just go back to the beginning, if you would. Thank you. Alright, so what you’re seeing here is the engineer’s dropped in a, a, a simple wireframe. Uh, I think expand this as well. Come up with a, a simple prompt that says, “Listen, build me this thing,” um, uh, given these, given this wireframe. Um, and it will, uh, go off and execute that. You can see what’s happening here. I know it’s a little bit small, but it is, um, uh, running through a bunch of decisions. The first thing that it does is go off and look for the Zuora docs. It knows what you wanna build. In this case, it is a, uh, an invoice, uh, history component. So it’ll go off, uh, do a little bit of work in

the background, understand the context, uh, of the request, and start to plan out, um, the columns. So you can see here the request was for, uh, to have, uh, five columns, and that’s been built. Unfortunately, it’s a little bit small. Um, it also in the request was listed to handle any overflow on the data that comes in. And actually what’s happening in the background, um, is it is running through, checking for the live data, and in a second it’ll begin to bind, um, the UI to that live data in Zuora. So what we’re actually seeing here is the agent take a request, run through…. what that request is, and then start to identify what needs to get pulled in. And so it’s got the, kind of the base template. In the background now it’s going off,

uh, looking for the APIs, running through the API validations, making sure that everything, uh, is working. So it’s not just, um, thinking it’s completed the action, it’s actually, uh, checking whether the action is, uh, completed. And this is all obviously within Zuora AI. Uh, you can see the steps that the agent has taken. Um, and in a second we’ll see… Yeah, this is a switchover to a persona, so you can pull in a different persona and see different account. This is all coming live from your billing, uh, data. Um, actually, what the, the request is now is, um, add a, an additional column that says, um, whether or not the balance has been paid or not. So a simple request goes in, uh, the agent goes

off and starts to build a bit of logic in the background, and the logic is, you know, if the balance, uh, is zero, then it’s paid. And if it’s not paid, uh, then it’s obviously unpaid. Um, unfortunately it’s slightly small, but what you’ll see is that in the top row it’s unpaid, and the agent goes in and validates, double-checks that the, uh, math is right, and then completes the action. Um, and then that component, as I said, can be dropped in anywhere, um, and obviously accelerates time, uh, to value significantly. Um, we’d love you to, uh, reach out to us and, and join the, uh, Experiences EA program. Um, it is a white-glove program. Uh, we’re happy to, uh, sit down with you, understand use cases, um, and, um, see whether or not the EA program is going to be right for you.

Um, it is, uh, active at the moment, and we’d love to get your, uh, feedback on, uh, if you’re interested. And if you are, we will, uh, definitely reach out and, uh, start a conversation. Good, and I’ll, I’ll leave that poll up a little bit. I’m going to go backstage and hand over to Komal. Thanks. Thanks, Jonathan. Um, so my focus will be on what’s new in e-invoicing in Zuora. I’ll start with a very simple distinction, because it matters. E-invoicing is about the digital invoice itself and it’s e- it’s exchanged between, you know, the trading partners, with or without a compliance authority sitting in the middle. So that gives you your PayPal and clearance models. E-reporting is about providing transaction or payment data to tax authorities,

often for transactions that are not covered by the core e-invoicing workflow, but this varies by country. Like, for Mexico, the reporting or clearance layer is essential to the e-invoice process itself. So the simplest way to say is, e-invoicing is a document exchange, while e-reporting is a regulatory reporting layer around sales and payments. This distinction is essentially becoming important because the market is moving quickly. Zuora’s roadmap shows around 40 countries already having e-invoicing mandates, and eight more are expected to enforce them soon. So this is no longer a niche requirement, it is becoming a broader operating requirement for customers who bill across multiple countries and need a scalable compliance model. This brings me to what is new in Q2 in e-invoicing. The headline is broader e-invoicing coverage through the Zuora-Avalara partnership,

but the real story is essentially the connector. Our 2026 strategy is to deepen coverage through Avalara rather than spreading investment across many vendors, so customer get, customers get a more scalable compliance backbone instead of a patchwork of country-specific solutions. What we are launching is not just a set of templates. We are strengthening the Zuora-Avalara connector as the operational layer that moves billing documents from Zuora into Avalara, appliers, applies country-specific mappings, validates payloads, and handles submissions and response flows through a consistent integration pattern. For customers, that means less custom build, faster time to compliance, and a more repeatable way to expand country by country using the same core integration model. Configure the connector,

enter your business identifiers in Avalara and Zuora, set up your business regions, use default templates or modify them as you please, set which customers should receive e-invoices, and when you post the e-invoice documents, the e-invoice workflow will automatically be triggered. For Q2 specifically, we have extended our Avalara e-invoicing coverage to include 17 more countries like Spain, Belgium, Poland, France, Germany, et cetera. That matters because it shows that we are moving from a limited country story to a much broader connector-based coverage story across markets that the customers care about most. Now, on what’s next? France is one of the clear- clearest examples of where the market is growing, going. France requires both e-invoicing and e-reporting as part of its broader mandate

model. Starting September 2026, all companies must be able to receive e-invoices, and large and medium-sized companies must begin issuing e-invoices and performing e-reporting. Um, so for domestic B2B transactions, the obligation is for e-invoicing, and for B2C and cross-border transactions, the obligation shifts to e-reporting, and over time, payment and, uh, uh, payment reporting as well, which becomes a part of a broader model. Uh, France is important not just because of the date, but because it shows that compliance is no longer just about generating a valid invoice. It is increasingly about the structured exchange, lifecycle status handling, and broader reporting obligations over time. That is exactly why the connector matters. Zuora remains a system of record for billing, while Avalara, Avalara handles the country-specific

regulatory layer. And France is not the only deadline customers are preparing for. Belgium’s B2B mandate is slated for January 2026, uh, Germany moves into a mandatory B2B issuance for larger companies in July 2027. Spain and UAE are also joining forces. Um, so if I had to summarize the message in one line, I’d say this e-invoicing is becoming a multi-country operating requirement, e-reporting is increasingly part of the same compliance journey, which is coming next in Zuora’s, uh, framework…. uh, Zora’s Q2 Avalara Connector Extension, uh, gives customers a more scalable connector-based foundation to prepare for the next wave with less custom work and a clearer path to exp- expansion. And with that, I’ll hand it over to Bharath, uh, before… Uh, and before that, uh, you’ll see a poll coming

in, uh, to participate in the, uh, e-invoicing EA program as well. And I’m- I’ll move to the backstage and hand it over to Bharath. Thank you. Hey, Komal. Thanks. Thanks for sharing that. We’ll give it some time for this poll. All right. Hey. Hi, everyone. Um, can we move to the next slide, please? Um, so we have two big experience updates here. Uh, unified navigation and the global homepage. So, uh, a small context before we jump into a demo. So, the, um… You know, teams often jump between multiple tenants, modules, pages, and

day-to-day operational tasks. So when that experience feels disconnected, it slows you down, create some extra context switching, and make it harder for teams to stay focused and productive. So this new updates are focused on making the experience more unified and intuitive. So the goal is simple, this helps teams to get where they need to go faster, quickly understand what needs attention, and take action with less friction. Um, so, like we- like I said, like, we have these two, uh, big updates. Um, we can, you know, quickly get inside the demo and see, uh, more about these, and we’ll come back, uh, on the details. Can we move to the next slide, please? S-…

All right. I guess, um, unified navigation. This creates more seamless way to move across billing and revenue. Users can transition between areas more easily, switch tenants with less friction, and personalize their navigation based on how they work. Features like pinned pages and smart suggestions help users quickly access the places they use most often. Second is the global homepage. Starting from scattered pages or reports, users now have a single place to see what matters most. It includes ready-to-use billing templates or pre-built views for billing ops and developers, and flexible widgets that can be customized to fit each tenant’s needs.

In addition to the default widgets that’s available, you can also add your custom widget into our homepage dashboard. Let’s see, how can we add our own custom widgets into our global homepage e- from our new reporting homepage? Let’s navigate into the new Zora reporting. Now, let’s see an example of how can we add a new widget, uh, into our homepage for, um, tax amount trend, maybe. So, to create a new tax amount trend widget, uh, let’s choose the invoice, um, data here. Let’s choose the invoice date, and let’s set it up

as x-axis, and let’s choose the tax amount with an invoice for the value fields, and let’s choose it as sum. Let’s see, how can we visualize this query inside a chart? You have this chart settings, and you have these fields set for x-axis and y-axis. And most importantly, you have to choose this option to make these widgets available in our global homepage. Let’s save and run this report. Let’s give it a name so that it appears. This name, what we are saving here, will appear inside our global homepage as well. Let’s save and run. Now let’s go back to our homepage dashboard.

Let’s search for the new report type or widget that we created, and let’s add it. The manage templates feature helps you to share your own dashboard within your team within this current te- tenant. Let’s create a new template, and let’s create a couple of widgets, uh, custom widgets, that we created from our reporting homepage. Now we have this couple of widgets inside this new dashboard. Let’s publish this. Everyone who have access to this tenant now can see this new template that we recently published. Within our existing dashboard, let’s search for the template, and we have this new

template that we just created. Let’s add all widgets. All right. So yeah. So, like, we have these, uh, new templates feature which you can, you know, create your own dashboard and share it with your team, and, you know, you can, uh, play more around with our, uh, data query and reporting setting to add custom widgets. So quick update, uh, we’ll be rolling out this, uh, feature into all of your sandboxes soon, and we will be sending out customer communications for this. Uh, with that, I’ll hand it over to Kevin for more updates on reporting. Great. Awesome. Thank you, Bharath. Hey, everyone. Kevin here. Uh, okay, next up, we have some, some exciting enhancements for reporting administration.

So, let’s start with why this matters. As your teams grow and people move around, uh, report ownership naturally shifts. So, maybe someone leaves the company, maybe they change roles, and until now, managing the reports they left behind did require some extra steps. Uh, with this release, admins now have the tools to proactively manage reports from deactivated users…. uh, using, uh, transfer ownership. And, uh, you can clean up stale reports directly from the reporting UI. So, no need to involve, uh, Zuora global support, um, and your reporting environment stays organized and current on your own terms. So, what this act- so what’s actually new here? Uh, first, we’ve added an All Reports

Admin view. If you have the Report Admin or Manage All Reports permission, you’ll now see a dedicated All Reports tab that gives you visibility into every report across the board, not just your own. Uh, second, there’s ownership transfer. Uh, you can now go in and reassign reports in bulk, including reports from deactivated users to any activated user, all directly from the UI. Third, we’ve added, uh, bulk delete, uh, which means you can now remove obsolete reports and their associated schedules in one action, and everything is fully, uh, audit logged. And finally, we’ve redesigned the Manage Report Runs and Schedules pages. You’ll notice, uh, clearer labels,

active and inac- active status indicators, rich filtering options, and an overall refreshed look that, uh, aligns with the unified reporting home that you’ve already become familiar with. Uh, so what’s the impact for you? Uh, this is really about self-service. You can handle owner, uh, ownership transfers and clean up without having to file a ticket. Uh, you can get full visibility and control over scheduled jobs across all users in your tenant, and your whole experience is cleaner and more intuitive, uh, designed to scale as your organization grows. Uh, we’re really excited about this one, uh, because it puts you in the driver’s seat, uh, for managing your reporting environment day-to-day. Uh, and with that, I will hand it over to Errol.

Awesome. Sorry about that (laughs). Thank you, Kevin. Uh, so first of all, if we jump to our next slide, please. So, as we opened, as part of Zuora’s monetization strategy, we’ve been focused on giving you the flexibility to innovate how you go to market. So again, in November of last year, we introduced dynamic pricing, which enables you to customize pricing for each of your segments. In February, we introduced hard or fixed bundles, and as we covered earlier, we provided features and entitlements. So today, we’re actually re- releasing the next capability, uh, in our monetization journey,

and being very specific, uh, if you look at the problem that we’re solving, many of you rely on static merchandising or even a sales rep’s judgment to decide when and how to cross-sell, upsell, substitute leads, et cetera. So, as we get into intelligent merchandising… Did we lose the screen? It looks, it looks like we did. I think Sabrina maybe, um, lost connection for- there

for a second, and it’s coming back on. Oops. So, so Errol, do you have a good, do you have a good joke for us now that you’re getting put- put on the spot? (laughs) Well, I’m, I’m not a very funny guy. (laughs) However- (laughs) Uh, let’s just keep going. Yeah. And, you know, one of the things that we’d love to hear about in the chat is, as you think about how you’re innovating how you go to market, regardless of what industry you’re in, what are some of the key challenges and some of the changes that you’re thinking about? Uh, so how are you… What, I’ll say, packaging strategies are you using to grow revenue per user? Uh, what are some of the, I’ll say, tactics and strategies that are most important to you?

Uh, are you considering bundling? How are you optimizing how you sell products, uh, throughout that customer journey and life cycle? Uh, so with that, uh, that’s really what we’re here to help you with. And so, back to intelligent merchandising, instead of just relying on your reps, uh, and more of that institutional knowledge on exactly when to recommend a product, how to manage churn or mitigate churn, uh, how to upsell, uh, again to existing customers, or even when you have a new customer in and they present a complex problem to you, you know exactly what solution to recommend.

So, intelligent merchandising really uses, uh, a lot of what we’ve already built. So, first and foremost, it takes that business context into consideration. Uh, first really understanding maybe what channel, who, what segment, what geography is that customer in, what subscriptions or solutions do they already manage or already own? And then based on all of that information, we’re then able to make the optimal recommendation on some of the other elements, which is, what do you recommend, how do you manage them through this life cycle, uh, or even very simple scenarios, which is, when you end of life a product,

how are you gonna gracefully substitute or supersede existing SKUs with a new package or offering? Uh, so this, we’re actually gonna be entering into beta in the June timeline, and we would love to work with you. And, you know, again, for those of you that think this is easy, like old retail, uh, type merchandising, one of the really unique things about the way Zuora merchandising works is, we can take 10 or even 20 different cont- conditions, uh, triggers or attributes into consideration. The new intelligent monetization engine assimilates all of those, and then is able to make the optimal recommendation.

And again, that uses both rules as well as AI. And the other thing that you can s- if you start thinking about what we’re delivering, we’re also laying the future…. for agentic commerce or agentic interactions. And what that means is when an agent is coming to your site, they’re not gonna ask you a series of questions. They’re gonna give you 20 or, or 30 questions all at once. They are buying on behalf of a complex business, and broop, these are all of the characteristics. Recommend the optimal solution in milliseconds, and this is exactly one of the problems that we’re building the foundation to solve in the second half of this year. So, that’s the foundation.

Now, let’s jump into the next solution. Uh, oh, sorry. So, for those of you that wanna join us, we would love to work with you, uh, understand the types of cross-sells, upsells, own, um, turn, mitigation, and solution merchandising tactics and campaigns, uh, that you currently utilize. And again, if you’re B2B saying merchandising is for B2C, that is absolutely a fallacy. Uh, this is about really optimizing how you, uh, not only improve conversion, but grow customer lifetime value. So with that, we’ll now move to the next element, and that will be configurable bundles. So building on this exact foundation,

uh, we are now, uh, earlier this year, we rolled out fixed bundles, which, again, to remind you, is taking multiple products and turning that into a skewed new solution. Now, we’re produ- providing the ability to essentially enable your sales reps using CPQ, and in the future, your customers to configure their optimal solution for their specific use case. And so, there are many different elements here. Uh, but first and foremost, what this does is utilizes the same foundation that we just introduced, uh, and within f- uh, the specific bundle, select exactly which products can be purchased together,

and then even associated with those products, we’re then able to dynamically assemble the bundle plans and the bundle charges. So, let’s just talk through a very simple scenario. Let’s just say you’re selling CRM sales and marketing, uh, and you want to enable customers in different industries, uh, to dynamically assemble, uh, those elements and the connectors into a new configurable bundle called the Business Suite. So, based on ex- exactly who they are, uh, if they’re an SMB versus an enterprise in a specific industry or a specific GO, you’re able to present the optimal, uh, set of choices, so that they can determine exactly how, which products and integrations

do they want. Uh, they’re then able to determine the bundle plan. Do they want basic or advanced? And then finally, all of those component charges are then essentially pooled and optimized so that you can adjust those prices, exclude prices, and bring those together dynamically on the fly for each customer. So, on the catalog side, we’re enabling you to actually build that, and I’m now gonna hand it over to Manfred and talk about exactly how that’s gonna essentially be, uh, sold within CPQ. All right. So, yeah. So, you just heard, this is Manfred. So you just heard from, uh, Errol

how this is all set up. These configured bundles is very important, uh, because with the fixed bundles, um, sales reps, you know, sold, uh, a product and a plan, and the customer got exactly the content that was in it. Now, um, with the configured bundles, the sales rep can now customize it. They can make it specific to m- meet the customer’s need. And that’s, uh, very important, because often specifically in SaaS and, uh, also other industries, you know, customers they know what they wanna buy, and they don’t have patience if they get, uh, other things that, that they don’t need, or they feel they don’t need. So, uh, there is, uh, on the… And, and while the, the, the sales rep is doing it, the business logic is enforced, so

any compliance rules, any business rules are enforced, uh, through the, uh, rules engine. Now, you see on the, in the screenshot, there’s, uh, you know, what is new is we basically have a, an experience for the sales reps that have two panels. So in one panel, the sales rep’s on the left, he makes his choices. Uh, rules are firing. It’s, uh, the sales rep is guided through the experience, so they provide the input. On the right-hand side, they can see how this bundle is constructed. So, the results are shown on the right-hand side. Prices are all up, and they, uh, understand, uh, on the bundle level what the impact is to the customer from a price point of view. So, on… So, why does it actually really matter? So, I al- already mentioned that, uh, sales rep

now can actually customize bundles towards the needs of the customer, but, uh, studies have shown that with configurable products and bundles, you actually can significantly increase average sales prices, because you have a me- mechanism now that more flexibly allows you to add, as a sales rep, additional products into the sales. Um, there also, and there’s increased customer satisfaction, because customers really get what they’re asking for. They’re not buying, you know, uh, fixed bundles that have a lot of stuff in it that they don’t really need, but they, you know, have to buy it anyway, because they wanna take advantage of a bundle deal. And, uh, the, the last benefit of it is internal. So, having a configurable bundle with appl- you know, where

you, you really configure based on these policies, when you log that into order management, so when that quote gets placed as an order…… it is correct and it is, it can be provisioned and can be built completely. So, all these rules are enforced and that has huge benefits for internal so you do not have any frictions, you know, making quotes into orders. And with that, I’m now handing it over to Sriram, and he’s talking about Deployment Manager. Hey, Manfred. Before you go, when is this available? This is so exciting and I know a lot of customers are interested. Yeah. So, we bring this out in August, uh, so- Awesome…. yeah. And it’s, uh, available in, uh, Quote Studio. Wonderful. Thank you. If you’re interested,

um, please contact, uh, Natalie or me and, uh, would love to talk to you guys. Absolutely. Absolutely. All right. Thanks, Manfred. Okay. Thank- thank you, Manfred. Uh, um, thanks everyone for taking your time joining. Um, so I’m gonna talk about, uh, the, uh, couple of capabilities that the Revenue customer, we are enabling for Revenue customers. So, platform is a suite of capabilities and, and we’re going to unify w-, um, you know, those capabilities for Revenue customers as well, starting off with Deployment Manager. So, unlike, uh, previously, um, the existing process of migrating configurations between tenants was a manual process. It involves several

steps to reach out to support and then, you know, running these scripts, SQL scripts, um, and then leading into error prone and then, um, you know, migration issues, right, uh, which is, which takes time. So, what we are doing is we have, we’re going to offer, you know, integrate the Deployment Manager into Revenue and, uh, which offers a self-serve UI for, uh, admins to actually visually compare the configuration, the settings between two tenants. Uh, it could be a sandbox prod or between two sandboxes. You can compare, visually compare these configurations before you want to actually deploy and migrate them. And you also have these abilities to roll back. You can also track the, uh, migration deployments between tenants and the history of the… and, and the audit of these deployments.

What this means, uh, the key benefits, um, you know, you’re going to reduce your time in, in the, you know, um, bringing your configurations from your production to sandbox. You don’t have to wait on full sandbox refresh, so you can easily bring your, uh, configurations and move your, deploy, migrate your configurations from different tenants. Um, and then this would reduce your repeatable auditable process, um, so we can, we can actually run these through APIs as well. Next slide, please. Um, next one is, um, the workflow. So, we have heard from a lot of our customers who actually, um, are, you know, relying on writing some Revenue customizations, custom jobs, uh, for, for, you know, extending the,

uh, Revenue functionality. And this would require an ex-, you know, extensive domain knowledge and technical knowledge on, on relying on the global services and Zoho support. What we are doing is, you know, we’re going to actually unify, um, to the platform-free capability again, which is workflow. Um, and this would offer a low-code, no-code orchestration engine that you can actually create, um, you know, uh, workflows, um, you know, using Revenue tasks. We’re going to expose, um, um, our APIs on, into workflow as regular tasks and the business admins or IT persons, they can actually create, uh, end-to-end workflows and then they can orchestrate using Revenue tasks. Um, you know, for, for your custom jobs, which is a replacement or you can use the workflow as a,

as a custom job. And then you can also register them inside Revenue as a custom background job. And then you’ll be able to schedule or run this, um, workflow within the Revenue, uh, scheduled jobs UI as well. Um, the key benefits would be on the, um, admins and IT persons, so they can actually manage. You don’t have to reach out to, you know… Uh, this would be available for partners also, so they can, uh, create Revenue custom jobs, um, with a drag-and-drop or a low-code, no-code interface. Uh, they can also, uh, perform, uh, different operational tasks on Revenue contracts, uh, to begin with, right? And then this will completely reduce your man- manual interventions on, on Revenue contracts. You can start automating your workflows and then enabling them into your, uh, um, natural way of running a Revenue

job. Um, that’s all I have, uh, would be Ramesh on Revenue reporting. Hey, Sriram. Thank you. Hey, everyone. I’m going to talk about the, uh, changes, uh, that are going to come in the reporting side of the Zoho Revenue. Uh, a good reporting framework always help to close the book in a fast-paced manner. So, in that aspect, Zoho Revenue have three critical reports. One is, uh, uh, remaining performance obligation, waterfall report, and, uh, uh, roll forward report. In remaining performance obligation report, what it is going to, uh, uh, specify, it’s how much of the revenue which is not yet recognized. Uh, this can be classified… Okay, currently,

we don’t have the classification of whether that, uh, uh, remaining… or whatever the remaining revenue is, uh, unbilled or, uh, billed, uh, long-term or short-term. Those kind of things is not available. We are going to bring those things, uh, in the new report. In that, uh, uh, which help the customers to (clears throat) slice and dice the information of the remaining performance obligation and take an addition. And the second one is on the waterfall report. The s- waterfall report gives the amortization of Revenue on a different period. Uh, what the new thing is going to be, uh, it, it is going to give the visibility of the past period Revenue, how much is recognized, as well as the future, uh, future Revenue. Okay, it all going to give the entire, um, uh, contract lifespan can be, ge- get in the, uh, waterfall

report. Then, uh, in, uh, roll forward report, which typically gives the balances, uh, based on the period, in that, uh, we, uh, add more fields, uh, related to that of a variable consideration netting…. and build, unbuild, and a long-term, short-term. In that way, uh, we know when the cust- uh, the user not required to move, uh, juggle around multiple reports, uh, to do a reconciliation. This will help the, uh, uh, uh, user to close the books, uh, in a fast-paced manner. That’s, uh, these are the things coming in the reporting, which gives the life of the people, which, uh, to, uh, reconcile the number in the fast, uh, in a be- best possible manner. With that, I’m handing over to Sanjana for, uh,

connectors. And Ramesh and, and maybe you can say, uh, can speak to this, all of these great things coming into our revenue, Q3, right? You have- Yeah, I ƒ Yeah, that’s correct. Natalie…. recording, workflow, and, and, um, the deployment manager all within the Q3 timeframe, right? Yes, that’s correct, Natalie. Thank you. Awesome, awesome. Wonderful. I’m gonna pass it now to Sanjana, who also has a exciting Q3 release. It is now in beta. Thank you, Ramesh and Natalie. Yes. Hello, everyone. Um, so the update that I would like to share today is around the data warehousing connectors and, uh, how we are expanding the support for Zora Revenue. Um, so today, we support data warehousing connectors to some of the most widely used destination types across,

um, databases, data warehouses, and data lakes. Uh, this includes the most widely used destinations like Google BigQuery, Redshift, um, Delta Lake, S3, Blob Storage, MySQL, PostgreSQL, and more. Um, so customers are using these connectors to continuously sync the Zora data into their preferred analytics environment, uh, for use cases such as reporting, reconciliations, BI dashboards, and downstream analytics. Um, in particularly to call out, uh, there’s a connector called Delta Lake, uh, connector, uh, which serves as an intelligent destination layer that can directly integrate with your BI and analytic platform for broader reporting use cases. Um, so though, though there are a lot of APIs available in Zora, many prefer these connectors because they provide a governed, scalable,

and managed pipeline into your, uh, warehouse environment without the need to build and maintain your custom integrations or stitching the logics together and maintaining that and all that. So up until now, uh, this capability has primarily focused on building data, and, uh, what’s exciting now is that we are extending the connector-based approach to support Zora Revenue, uh, objects as well as part of our beta rollout. Uh, so this will now allow the customers to bring both billing and revenue data into a common warehouse environment using a single managed pipeline instead of relying on a separate export or custom revenue integrations. So the key value here is enabling a more unified order to revenue analytic experience where you can do analysis across both your billing and revenue together.

Right? So from a timeline perspective, uh, revenue connectors are currently in beta, and, uh, we are actively looking for interested customers to participate in the program, uh, who are submitting the request early on. And, uh, billing connectors are already available as an early access offering. It’s been there more than six months, one year now, and are being actively used by many customers today. Uh, for both billing and revenue connectors, we are also offering a limited free trial for two weeks, uh, for the interested customers who are submitting the request early on. And, uh, we would like to quickly understand from this audience what is the level of interest, um, and you can actually submit a poll, which will come after the slide. Maybe I’ll give a pass now. Yeah, you can actually submit your poll

on your interested destination and if you want to explore more about these connectors. Yeah, as Sanjana said, we are offering a two-week trial. This can be just within billing, this can be just within Zora Revenue, this can be in both, right? And so you can indicate that on the poll. We’ll reach out to you, um, and understand which database, which data lake, which data warehouse you’re using today, um, and work with you to enable this trial. So feel free to indicate that now within the, the chat. If it’s not relevant to you, all good too. And with that, Sanjana, thank you so much, and I would invite- Thanks, everyone…. Kevin back up, um, as we get into, um, all good things

Zora AI. And so Kevin, um, looking forward to today’s update on AI and having Richard join as well in just a few minutes. Awesome. Thank you, Sanjana. Thank you, Natalie. Uh, cool. Well, uh, yeah. So let’s talk about Zora AI. So we launched Zora AI to all customers just over a month ago, and the adoption has honestly exceeded our wildest expectations. In just one month, over two-thirds of all Zora customers are actively using AI in production. Not sandbox, production. And that number is growing every single week. Uh, so what are people actually doing with it? Uh, let’s

talk through a few different, um, categories and examples of, of what we’re seeing. So on the billing and revenue side, customers are using AI to investigate invoice variances instantly, audit credit memos to find leakage patterns they didn’t know existed, forecast upcoming billing with our billing preview tool, uh, and getting plain English explanations of complex charge calculations. Things that used to require writing SQL or submitting a support ticket are now happening in seconds, uh, in conversations. On the subscription and account side, teams are getting instant account health summaries, they’re previewing what a cancellation credit would look like before they pull the trigger, uh, they’re tracking renewals, and even applying

collections logic with built-in guardrails so that AI won’t take unsafe actions.Uh, for reporting and automation, people are building dashboards with, uh… And running reports in national, natural language. They’re exporting data to Excel or PDF on demand. They’re creating work, uh, Zuora workflows through conversations, um, and even connecting their own external AI tools like Claude Desktop and others, uh, through our MCP server. Uh, so the bottom line is this isn’t experimentation anymore. Uh, customers are using Zuora AI on real finance workflows every day, uh, and it’s saving them some serious time. Um, and we haven’t slowed down.

Uh, so since we launched, uh, we’ve been shipping improvements to Zuora AI every single week. Uh, we’ve had nine releases in nine weeks. And, uh, just wanna take you all through some of the highlights of some, some of the coolest things we’ve been shipping. Uh, so one thing is visual summaries and charts. Uh, so Zuora AI has the ability now to generate dashboards, uh, bar charts, uh, structured layouts directly in conversation so that you can see your data at a glance and even interact with it, uh, if you’re in full screen mode. Uh, it has the ability to do file generation now, uh, so you can export in Excel, a CSV, a PDF, a JSON, or even generated PNG charts on demand. Um, and then on the flip side,

you can do file upload, which lets you bring in spreadsheets. Uh, you could take a screenshot of a Zuora page, upload it into Zuora AI, um, or documents and, and use those as context in your prompts as you’re working with Zuora AI. Uh, you can do things like invoice variation detection. Uh, so AI can now automatically flag line item anomalies. I know we had a question a little earlier, uh, in, in the, in the chat, in the Q&A around, um, detecting anomalies. Uh, so it can do that. It can, uh, identify possible missing charges on your draft invoices before they post. Uh, we’ve also added in reporting. So there’s been a lot of work adding in reporting into Zuora AI. You can search and run and retrieve both billing and revenue reports,

uh, through natural language. Uh, this means no SQL, uh, no IT tickets that you have to file. Um, we also added in, uh, just a number of quality of life improvements. Um, we are, we are taking it, um, you know, trying to take the usability of the tool, uh, to the next level. So you have things like voice input, so you can do hands-free interaction with, with Zuora AI if you click the little microphone logo or icon. Uh, we have, um, done some enhancements to how the AI panel is pinned so you can work more easily side by side in the side panel with, with your actual Zuora pages. We have chat sessions sharing, uh, so you can share a conversation. So you have a great conversation in Zuora AI, you wanna share it with a teammate, we now allow you to share that.

Um, and they can, then they can access it. Um, and workflow creation, right? So now you can build Zuora workflows, uh, through conversation directly in Zuora AI. Um, and this is what we’ve been, uh… You know, this is what weekly shipping looks like, uh, and we’re not stopping. So we’re gonna continue these, these weekly releases of, of new, new improvements. Uh, so what’s next? Uh, we’re building specialized capabilities for the roles and jobs across your organization, uh, designed to handle specific high value workflows end-to-end. Um, so not just answering questions, which, which we think it’s really good at, but actually helping you do your work. Um, so today, I wanted to give you all an exclusive look at three capabilities that we’ll be shipping soon.

Uh, the first one we’ll take a look at is SSP analysis, uh, for our Zuora Revenue customers. Um, so this automates standalone selling price analysis for revenue contracts. It pulls the data from Zuora Revenue, it runs comparisons and then surfaces exceptions, uh, that, uh, the AI thinks you need to review. Um, the second thing we’ll take a look at is product catalog health. So what this will do is it’ll actually scan your entire Zuora product catalog. It’ll look for things like misconfigurations, maybe stale rate plans or pricing inconsistances, and then it’ll, uh, recommend a series of specific fixes for you. Um, and then finally, the, the third thing we’re gonna give you a glimpse at is quoting. We’re really excited about this.

Um, this is, uh, AI that will help you generate and validate quotes conversationally, uh, pulling them from your catalog, applying your rules and previewing the downstream billing impact before anything gets committed. And this will all be available from within Salesforce. Uh, so, uh, right there where, where your, your teams are building their quotes, um, they’ll be able to do that there. Uh, so let’s show you each of these in action. Uh, the first one we’ll show is, uh, we’ve got three recorded demos, and we’ll, we’ll start with the SSP analysis. When you’re setting up an SSP analysis, the hardest part is knowing how to group your data in the first place. You can group by product, region, currency or more. This is where the Zuora AI SSP analyzer

comes in. It uses algorithms to automatically generate, test and refine hundreds of stratification combinations instantly. Let’s see it in action. Here, I upload a data set instead of my batch, just like the standard analyzer. I choose the analysis range, value type, determine how to calculate my SSP and set my compliance range. Let’s look at an analysis I ran earlier today. Instead of building each scenario manually, the analyzer tests dozens of stratification combinations for me. Zuora AI then ranks each strategy using a fitness score that balances three things, compliance, simplicity and manageability. Here, there are 56 different combinations, but Zuora AI only shows the top six based on that score.

Compliance is weighted most heavily, but the model also favors setups with fewer stratification columns and a practical number of SSP buckets, so you’re not left with something overly complex to maintain.The result is, I get the most practical, compliant, and maintainable stratification strategy. With the insights that I gain from running this SSP analysis, I can now quickly and easily refine without manual trial and error. Zora AI SSP analyzer helps team find an approach that’s compliant, practical, and easier to maintain over time. That’s AI built for the people who run Quote to Cash. Okay, awesome. Uh, the next, uh, the next demo we’re gonna show is for, uh, product catalog health. Uh, so this will help you scan your whole catalog,

identify those misconfigurations, uh, and do that all through the Zora AI con- conversation interface. The new catalog health agent will enable you to manage your catalog by finding stale or redundant SKUs, while also identifying opportunities for optimization or SKU consolidation. You simply access Zora AI and prompt it to generate a catalog optimization report. The report provides insights on the total number of product rate plans, both before and after optimization, identifying products with high product rate plan counts, as well as providing an overview of the overall metrics.

The most important element is that the report provides you with the exact merge or optimization logic, providing actionable steps on how to consolidate your product rate plans using dynamic pricing, and it even provides you with the exact attributes and values that you should use. The catalog agent will be live in your environments on June 2nd. Awesome. And then, uh, the final demo we just wanted to give you all a preview of is the quoting capability. So, here you can generate and validate quotes conversationally. Uh, so let’s take a look at what this looks like. AI’s new sales agent within the Quote Studio

experiment- experience in Salesforce. So, once you have the feature enabled, you’ll see this new icon to open up the AI window within the, uh, CPQ side- sidebar. The first thing you’ll notice is that this looks exactly like the AI experience within Zora itself. Uh, and you’ll get to see the history of related queries done in this ex- in this current session. And when I put in my first prompt, you’ll see it start to think. I’m asking about information related to this quote’s billing account, so it’s passing in the context of the existing Zora billing account that this quote is being created for. You can see it thinking and you

can kind of understand what it’s looking for, how it’s looking for that information. If you expand that history there, you can see exactly what it looked for. The billing account overview will give you all the information relevant for this billing account, including its own subscriptions, products, recent payment history, and contact information as well. It’ll even prompt you for some additional, uh, options that you can ask. I will go ahead and ask about the other subscriptions again, just to verify that this account doesn’t have any other subscriptions. If it did, it would let me know and I can make sure not to create duplicate subscription products for, uh, products already owned by other subscriptions

on the same account, if that was a use case I had. So we’ll, it’ll think through this briefly and it’ll tell us that there’s just the one subscription on this billing account, including some information about that subscription and the products on this subscription. And lastly, maybe I wanna understand what the account TCV is for this subscription. So I’ll ask that next. And if there were multiple subscriptions on this, it would pull the account TCV for all owned subscriptions. But since there is just the one, it’s giving us the one subscription here, the products with the, for the TCV composition, and lastly, just what the total TCV is for this account. And that is

Zora’s sales agent within Zora CPQX. Okay, great. Well, uh, with that, uh, so we have a lot of exciting things in the product, uh, coming. I’m gonna hand it over to Richard, uh, and he’s gonna take us through all the exciting, uh, things with the Zora MCP, uh, w- where you’re using your own tooling to inte- integrate with Zora, your AI tooling. Thanks, Kevin. So in previous webinars and table talks, we’ve discussed how to enable and configure your Zora MCP servers. If you missed those sessions, just know that MCP server enables your preferred AI client, could be ChatGBT, Cloud Desktop, Cursor, your preferred client to gain Zora superpowers and access to your Zora tenants and datas. It’s how we bring Zora to your,

uh, workspace. Many of, uh, you have been, have been… excuse me. Many of you have been using our MCP in read only mode and creating custom reports and dashboards. The next step when you’re ready is to try it out in read-write mode, uh, and in one of your sandboxes. So you can test creating things, like product catalog items or, uh, subscriptions or managing invoices. Um, I’ll repeat that. Test in your sandboxes first, API Dev Central, but then try some of our MCP tools for managing subscriptions, invoices, and other document types. Our testing has shown that this type of work benefits greatly from what are known as skills. Skills are these predefined text files that capture, that can capture defaults and preferences that you have for how your business works and how your Zora implementation

works. And we’ve got a brief video right here to show you this in action. Sabrina, if you don’t mind starting.Here, I’m using Claude codes SONNET model with Zuora’s MCP server to create a new billing account for Alice. She wants 10 seats of our team’s business starter product. As you can see from the conversation with Claude, it works gradually toward completing the request, but it takes a few detours along the way. For example, it tries to create an evergreen subscription, even though that isn’t my company’s normal business practice. There’s a better way to make sure subscriptions are created quickly and correctly with your business rules and policies, and that is to use skills. A skill is a markdown file that contains a set of instructions for your model.

In my case, that’s Claude, but this works with all models. As you can see from the name and description of this particular skill, z-orders-skill, it’s designed for use with Zuora’s MCP when creating or modifying subscriptions. This skill file defines the default values, expectations, and options I want for subscriptions. Here, we’ve switched to a Claude session that has this skill enabled, and I’ve given Claude a very similar request. Create a subscription for Alice for 10 seats of teams business starter. Without all the back and forth, Claude is able to move directly toward completing the request and creating Alice’s account for 10 seats. When I asked for invoice details to confirm that the subscription had been created correctly, you can see the requested quantity of 10 at

$7 a seat. That produces a $70 invoice for the first month using anniversary billing. Another advantage of skills is that they make it possible to complete tasks using lower cost models. Here, you can see that we’ve switched to Haiku, and Haiku is currently Anthropic’s lowest cost model. But because we have our order skill in place, the same request for Alice for 10 seats of business starter is completed very quickly, and produces a similar invoice, 10 seats for $70 with anniversary billing. With the help of our skill, Haiku was still able to create the subscription. Creating skills takes a small investment of time, and we’ve made the skill used in this demo available for you to download. You should download it and customize it for

your implementation of Zuora. Additional skills are also available, and we’ll continue to share new ones going forward. Thanks for your time. Thank you, Sabrina. Eh, do you mind jumping to the next slide? And so these skills turn the general capabilities off our MCP server into focused useful assistants that you control. I’ve included a second example here. We’re not gonna play the video because, you know, you’ve suffered enough, uh, after nearly 90 minutes to this call. You can watch it in your own time. Em, but it’s a similar type of thing. It shows a scale and operation, making it easier, uh, to create product catalog items in your product catalog. And again, you’d want to modify, there’s a link there to skill.md file. Uh, do you want to modify that file for your defaults?

You know, what’s your default revenue, uh, accounting, uh, practices and, uh, default settings for various pr- um, uh, subscriptions. Anyway, um, anytime we talk about AI, we get asked if AI is permitted to change your tenant. The default, I gotta stress, is read only. AI is enabled in all your tenants, but it’s enabled, uh, read only. And your admin has the option of going in and flipping a switch on a tenant by tenant basis that turns this, uh, switch to a read-write, enabling you to then start creating subscriptions and, uh, product catalog items like shown in the videos. But again, you know, try these examples in a sandbox, test them out thoroughly. And these t- are templates. These skill files are templates that require your input to be effective. Second question we always get asked is about tracking

what the AI does, and here are usual Zuora auditory features, abilities. And any time you ask, uh, your, uh, client to do something, uh, like create a subscription, that subscription will be tracked and recorded in the audit trail under your name, not some generic AI account. Our AI is, uh, configured or instantiated so that there’s no shortcuts. It doesn’t, you know, the human is always asked for approval, and the human is always r- you know, responsible for the results. And so be sure to test, you know, those abilities and, and confirm them and making sure, you know, your security and legal and compliance, et cetera, folks are all happy. Anyway, and Kevin and I are on an AI onboarding table talk tomorrow morning, uh, same time, 8:00 Pacific. I’m

hosting a skilled table talk, which is gonna go over this in the previous example in more detail and show you how to customize and modify these. And there’s, be a follow-up link for you to sign up for either of these table talks. Thanks for your time. Richard, Kevin, thank you so much for, for your time. I very much appreciate it. Um, as Richard mentioned, when you wanna go into depth, right, into some of these features, especially around AIs, we’re doubling down on our table talks to give you, um, really full access to ask those questions poignantly to Kevin, to, to Richard, right? Um, we’re all doing, uh, roadshows, right? Uh, throughout the summer, right? And so if you have questions on, you know, on boarding, right? We have that

table talk tomorrow morning. All of these get recorded as well, right? So you can sign up and get the recording for those as well. Um, we have, um, a revenue table top come, uh, June 16th, as well as, um, skills for agents. So if you wanna learn more about what Richard just talked about from a skills perspective, how to build your own skills, right? He’s, um, he will be available to, to, to sit in the table talk on the 18th. Additionally, we have a number of events as we go into, um, the summer timeframe if you’re based in the Northern Hemisphere, right? Um, throughout EMEA, we have a number of user group events that will span Milan, um, uh, Doc, Nordics, France, uh, London.

That will be happening all throughout May and June. Um, and then we have a number of additional virtual events as well, um, that span not only AI, um, but also revenue. And so you will be seeing, um, invitations for, for those as well. Um, can sign up, um, as a result of the email that we will send out, um, after this event. Again, this session was recorded. You will h- get access to the recording as well as the opportunity to sign up for some of these events. Um, and we hope to see you, uh, this summer. Our next What’s New/What’s ne- next will be in August for our Q3 release. And in the meantime, right, we wanna hear from you, right?

Our stories are only, um, as good as, as being able to evangelize you and what you’ve done with Zuora at your company. And so if you were interested in being an advocate, um, for us, we would love to, to, um, to have you. We’d love to send you some swag and be part of our journey. Um, so if you’re interested in that, you can always reach out to m- myself, um, or anyone on the Zuora team. With that, thank you so much for spending the last 90 minutes with us, and, um, we look forward to seeing you again at one of our events this summer, as well as, um, the next What’s New/What’s Next in August. So take care. Thank you again for your time, and, uh, we look forward to speaking with

you in depth about more of these features. Thanks again.