Name: How Salesforce Agents and Doc Gen Transform Workflows
Uploaded: 2026-03-17T17:31:10.793Z
Duration: 52 min 16 s
Description: How Salesforce Agents and Doc Gen Transform Workflows

Transcript for "How Salesforce Agents and Doc Gen Transform Workflows": Good afternoon. How are you all doing? I saw a couple comments in the chat already. From Houston, Belgium, Coconut, Paris, London, Colombia. Look at that. Look at that, all around the world. Alrighty, everybody. Thank you for joining me today. So, we're gonna have a brilliant webinar today talking about how Salesforce agents and document generation can transform workflows. We've the Document team, which I'll introduce to you in a second. Beautiful. So, if you're sort of new to the Salesforce Ben team, we we do everything under the sun. So, we've we've had the blog up for for an eternity now doing articles. We've got a weekly sort of newsletter as well that goes out. We do in person events. So, TVX is coming up. You can meet the team there. Also, we've the YouTube channel which you can go and subscribe to, of course. And we've got the podcast. We've actually got a new podcast as well called The Picklist Podcast which you might want to listen along for. That's on YouTube, Spotify, and Apple Podcasts as well. Alrighty. So, getting into it. I'm sure you don't wanna see my face or hear my voice this whole time. So, I've got the team from DocuMill joining me. I've got Mark, I've got Anthony, and I've got Flockhart joining me today. Team, do you wanna jump up on stage and introduce yourselves to our wonderful audience? Here we go. Good to have you guys here. How are you? Very well, and good afternoon to everyone who's joining the webinar. Yeah. Thank you, Tim. And I'm quite happy to listen to your voice for the the next hour or so. Oh, man. I'm I'm sure you got a lot better information to share than I did today. That's for sure. I'm I'm very excited to see what you guys have got to show us. Absolutely. Should we do, like, a little round of intros from the DocuMill team before we kick off? Absolutely. And I'm like. a plan. yeah. I'm more than happy to to dive in first. So as you can see, my name is Mark McGinn. I'm one of the account managers here at DocuMill. I've been within the organization for quite some time now, actually, three years. And I'm primarily responsible for ensuring that our customers make, you know, most efficient use of our tools as well as work very closely with other ISVs and SIs in the ecosystem, primarily within the DACH region as well as The US. And I'll hand over to Anthony. He can provide an intro to himself. Thanks, Mark. Yeah, Anthony Montgomery, Enterprise Sales Manager. I'm based out of London and I basically look after the financial services for DocuMill as well as The UK. I've worked with financial service for the last thirty years for my since and still enjoying it. In the document automation space, I've been in that space for the last ten years. So I've seen a lot of evolving, changing, and how we get into workflows for the last ten years now. And I joined DocuMill last summer, so relatively newbie. So go easy on me. Yeah. Thanks. Flocker, how about yourself? Do you wanna say a couple of words? Yeah. Thanks, Mark. Sorry. My Internet was sort of crashing there for a second. But, yeah, hi, everyone. I'm Flockhard all the way from Finland. Very nice to be here. I'm a solution engineer at Docomo. I'm here to answer any technical questions you might have or any questions around the solution in general. So, yeah, I'm looking forward to this. Good stuff. Just in terms of questions as well, viewers, we've got the chat in the sidebar to your right. And we've also got a Q and A section. So if there are any questions that pop up during the session, please don't forget to pop them into the Q and A section. The team will be able to get to it during the Q and A. But without further ado, Mike, I'll hand over to you. On. on myself, fact Mark, I'll I'll take on that. A little bit of confusion there already. So just gonna run through the agenda. We're gonna look at why it matters now. We're gonna then talk about how dopGen is involved, and I've seen the evolution myself into the work workflows. And then we're gonna talk about agent force and doc gen workflows. And then we're actually gonna show you what it looks like with agent force and document itself in action. And then we're gonna end with a q and a session. Before we start though, have a little bit of interaction. I can't have you coming all this way and and not not talking to us. So we're gonna run a poll, and you'll be able to click on the poll screen, which go to now. And what we're asking here is what is your biggest challenge in document workflow today? And to make it easier, we're giving you multiple choice. There's always gonna be options which you haven't got on there. But we're gonna look at, is it a, too much manual work in your workflow, b, managing templates and document versions, c, well, see a lot, document spread across sorry, data spread across multiple systems, and then d, approvals and collaboration delays. So if you can go ahead, choose a, b, c, or d in the poll, and, we'll give you the results right at the end. So just to keep you teasing, we'll let you know what happened right at the end of the webinar. Right. So gonna talk about why it happens sorry, why it matters now. Particularly pertinent today is already today we saw Close Brothers, a bank in The UK, Financial Services, lay off 600 people and a move to sort of AI more generative workflows. So what we're seeing at the moment is investments have been made in AI, and we're seeing results need to be delivered at cost. And with Close Brothers and Close Brothers themselves, they were involved in a commission scandal over in The UK, which ruled out financing. And they've had to pay out, and they've been using solutions to actually help handle that whole claims process. And so what we're seeing at the moment is we're seeing sort of generative AI, which and it feels like yesterday, we were discovering ChatGPT shifting to AI agents. And then with that shift, we're going from that basic generative AI creating emails, creating documents, and so forth with with that generative AI to actually looking at triggering workflows, being more interactive with the CRM, and sort of retrieving data and sending communications. So it's becoming a more integrated part of the workflow using the agents rather than just that original generative AI. And then we're seeing the business need, productivity gains that have made the investment, and we're really looking to capitalize on that investment, particularly as we've just seen today with Close Brothers. I will stop saying Close Brothers because, hopefully, there's no one on the call from there. But, yeah, it's just a real pertinent example of how the world is changing. There's a shift of that need for productivity gains. And then if we look at data itself, everyone started to have a single source for truth, get the data into one area, hopefully, and really take benefit from that enterprise data which is available to companies now through actioning the AI agents. So what this is doing is actually enabling a digital labor workforce. That sounds great, in principle, but, obviously, there's a knock on effect with that. But this enablement is allowing AI agents to go through, particularly in sales areas. Mark, I don't know if you've got any comments on this. Yeah. Absolutely. I think anyone who's worked within sales as a as a role has dealt with the frustration of kind of arduous tasks, I would say. And this could be anything. This could be from updating the CRM. It could be manually creating documents, like copying information from x y z areas. So, yeah, there's a lot of kind of efficiency gains that can be really realized using a combination of of ourselves as humans as well as AI agents. Excellent. Thanks, Mark. I can rely on you. So what does this mean? So what this means is you actually start getting AI agents, but they still need to work along human teams. Just on Mark, if you just move forward. So we know agents are great for detecting gaps and signals and so forth and really handling those repetitive processes, which can take a human time to keep going and going and so forth. So what we're seeing is this clear divide with the AI agent taking over these processes and triggering these workflows and so forth, but there still needs to be that human intervention. Why? Because there still needs to be exceptions dealt with, especially things like claims and so forth, approving sensitive content and decisions. Can't leave the machine to make really complex decisions and so forth. And in a relationship context, there's the whole negotiation side which needs that human element. So it's a combination of two things. You've got the the agents, which are almost being managed by the human side. And we're seeing this evolve last year, and we're seeing a lot more happening this year and putting into place. So it's not just the digital labor. It's a combination of both. And with that, you get efficiency, cost savings, and so forth, and you still need that human element to drive forward. So where does this leave us? Mark, if I just didn't work. So I said at the beginning, thirty years financial services, almost since. But the doc gen side, I've seen it evolve completely in the ten years I've been. When I started, doc gen was all about creating a document, I e, probably for legal, a contract, something simple. Well, not necessarily simple, but it was all about creating that document. And what happened around that document was everyone else doing different things and different workflows, but not around the document itself. And when I made into my sort of last role at HotDocs, we started to realize that the document generation piece was becoming the linchpin into that workflow. And it was sort of be the center, particularly in lending, particularly in insurance, particularly in manufacturing, these sort of areas. That whole document generation suddenly became that linchpin to the workflow. And then joining DocuMill this year sorry, last year, I joined six months ago, you see that process even further where the document generation actually becomes the workflow, which is absolutely fantastic because what it means is you have control and it becomes part of the business outcome for that workflow. So what we're seeing with document generation is you've got the curation part, which is what we've always done. But more importantly, you can start to review with peers and so forth, collaborate inside and outside of Salesforce, negotiate externally with clients, put in an approval process rather than having a separate approval system. You can bring in that approval process. And then for that business outcome, you can get the signature with that, so with esignature and so forth. And then you can manage the governance and everything around that process and workflow. And then simply put it, it's there. You've done it once. You can then repeat that process with renewals and so forth and link that dot gen to that agent force to trigger those workflows automatically. So rather than just basic generation documents, the whole document generation becomes the workflow and the business outcome. So for us, we can see ourselves working with Salesforce, and we push everything back into Salesforce at the end. But we also enable our clients to collaborate outside that space as well as the document generation is part of the bigger picture and the bigger workflow working with the different teams and departments. Okay. Mark. So when we talk about workflow, that's great. We've got this workflow. Everything's there. But like everything, you have to start at the beginning. And what we see with a lot of projects is getting it right from the start will make it easier right way through to the end. And that starting process still in document generation works around the templates itself. And the way we look at this is it's like a Lego building stack where we start off with the first layer, which is the outline, the design of of the templates themselves. Then we move into what data's gonna bring in from Salesforce or third parties or data lakes and so forth. Using things like JSON files, we can bring data in. So we've got the design. We've then got the data coming in. And then we've got the dynamic elements, the text blocks, the bits where people have to edit and so forth and actually can put in their own what they wanna put in. So we have the input fields. And then we have to look at the workflow. And this is the the important piece. What is the business trying to achieve from the very start of the generation right away to the completion and signature of that business outcome. So we have to map that workflow and actually look at each area approvals where needed, if there's approvals to be needed and so forth. And then we then finalize that with the screens to look at and review and so forth and and the input screens at the end. So that whole piece around the template size becomes the linchpin for the project and for the start of that workflow and document generation and business outcome. Okay. Mark? Yeah. So, over. to you, Mark, on on the agent force and doc gen workflows. Thank you. Yeah. Thank you, Anthony. So before diving into the content, I'm actually gonna pause and ask, has anyone in the webinar or anyone's organization, in the webinar actually implemented a Salesforce agent process that's customer facing and then includes a customer. So I think there should be a couple of answers for this. Yes and no, and perhaps maybe. So I'll give you all, some time to have a look, through. Mark. We're maybe is currently in the implementation process. That's, but it's not yet finalized. Excellent. So I'll give everyone a a couple of seconds, to answer the question, and I'm really looking forward to seeing what the results are. Particularly because from the conversations that I've had today within the industry, many of the the actual use cases for agents have been predominantly for internal purposes. That being said, I've heard some fantastic applications. So last year, I went to a number of different agent force world tours and heard from organizations, such as Carl Storks about how they're implementing agents to save their team's time internally so that they can access information more easily. So there are some really, really positive, kind of applications of agents, and we're seeing also recently this week, the news around Adecco as well, which is phenomenal. Now what I would really like everyone on the webinar to take away is that, while predominantly from what I've seen is that, the application of agents has been for internal purposes, we can easily extend these to include our customers in a very safe and compliant manner. Now the way that we'll look at this is across two different avenues. One is looking at sales workflows, and the other is looking at service workflows. So the first thing that I'd like to kinda bring to your attention, if we think about sales workflows starting in the prospect stage, agents could be used to create and send personalized emails or even one pages based on Salesforce data. Anyone who's worked within a sales remit has had to do this manually. Now I'd actually build on this, to expand to the next type of sales documentation, that you would use in a in a SaaS kind of workflow, which would be, a more personalized presentation for a specific client. And this typically, will use data from Salesforce, but could also extend to include recent insights, on the company's challenges that's been generated by AI and kind of linked into the document using Salesforce agents. Now after we've, sent our one pager and after we have provided that presentation to the the prospect or potential client, what we're looking to do is actually get to the proposal stage. Now at this point, agents can be used to generate branded proposals or quotes, and this could use the right clauses based on record context. Now one thing that came to my mind when putting together this presentation is, some of the work the salespeople do well out in the field where they may be in a meeting. It's went very, very successfully, and the client has asked for the proposal to be sent over to them. Velocity in sales cycles is of utter most important, and that particular salesperson wants to get the document, out to the client as soon as possible. Simultaneously, they may also be very busy and have to run to their next meeting. Now in this context, I'm leveraging Salesforce agents alongside document generation within the sales workflow makes complete sense. It enables the user to generate the document compliantly and professionally and have that sent over to the customer immediately while they can focus on that more human kind of aspect and relationship and go into the next meeting and starting to discuss business problems and challenges with other prospects. Now one of the key things and the main concepts that we've highlighted today and discussed so far is this notion that agents are really great for conducting repetitive tasks. That being said, human element, in a variety of different forms is essential when dealing with exceptions and edge cases. So to this point, the notion of routing documents for approval, by a human is key. Now how can we conceptualize this from a sales perspective? Well, generating documents for esignatures such as n d n NDAs are pretty much standardized, and this can be completed with an agent. It's a repetitive tasks or even the creation of a low lower value sales offer. Now when there are anomalies, outside of this repeatable process, that's when the approval can be extremely useful, and this can be triggered by a variety of different, means. So for example, if the ARR of a particular deal is exceptionally high, naturally, you'd want a human to review that, approve the document before it's been sent out to the client. Now I'm pretty sure that everyone in this webinar has heard at some point in time when it comes to the application of Salesforce agents, data hygiene is key. And in order for agents to work effectively, the data that you have within the CRM needs to be maintained and kept up to date. So we're gonna kind of flip that on its head a little bit today by saying that, yes, it is correct. But simultaneously, we can also use Salesforce agents to ensure, that our information within the CRM is actually kept up to date and that you have better data hygiene. And we can do this by creating onboarding documents as an example that will help organizations, collect missing details and have that written back into Salesforce. So I'm gonna kind of just pause on that point just now because we will have a little look at this in a couple of minutes. But lastly, in the final step of the the sales process, is our renewals. Now one application of Salesforce agents and, the renewal process is if you are managing or if your sales team, individually are managing hundreds of accounts, which isn't outside of the norm. They may need to quickly have a look at which accounts are expiring in the next month, two months, this quarter. You can ask your Salesforce agent those types of questions, and you can trigger renewals based on that information, sending out, compliant and professional renewal offers to the respective, customers. Now we're gonna kind of move from one side of the customer journey, which is the sales part, into the other side, which is the service part. And, really, the the concept is somewhat similar. But naturally, within Salesforce, the objects that we're talking about are a little bit different. So we're thinking about cases. We're thinking about work orders and service appointments. Now when it comes to correspondence, naturally, the agent can respond to simple informational cases. That being said, for approval required cases, document all routes, reviews, and sends compliant emails. Now this is quite an abstract thought if you aren't overly familiar with DocuMill's technologies. And it is important to note that, when it comes to emails, DocuMill treats these as documents from a technical perspective, meaning that we can bring in a lot more information that's readily available within Salesforce into Salesforce's emails. But this can be extended to include other nuances such as editable and non editable areas, within the email itself. So what we have here is this, complement, really, between agents handling simple repetitive tasks and allowing the human, to actually focus their time in more complex, cases. And really, ultimately, this benefits their their customers across the board. For dispatch, I'll keep this quite high level, but essentially been able to generate and send appointment confirmations and their required documents from the work order. But lastly, when it comes to field reports, and this is something that we are seeing more and more, from a document perspective, is really enabling the technician to upload photos. At that point, the agent can draft descriptions, and the workflow generates a formal field service report and actually sends that immediately to the customer. Now afterwards, that can be linked to the specific case as well as the work order. And we can even go a step further as Anthony kind of highlighted on one of the previous slides, is that with these field service reports, they can actually be finalized with electronic second share as well. And that's all within one workflow combining Salesforce agents, DocuMill's technology, and, of course, the field service agent as well. We'll pop over into the kind of demo flow as well. So this is really what we're going to see today, and this is having a look at an example of where, an organization may be missing some information within CRM. Now the way that we are going to use our Salesforce agents is to detect any missing fields, as well as intent. The second step will be to decide, to use a policy to decide which field will need to be updated, as well as which contacts need to be contacted, as well as the language that we need to actually communicate to that specific contact in. Our third step is the execution. So this is the creation and sending of that customer ready email, document, as well as interactive form. And lastly, but by no means least, is the write back. So that's actually the ability to collect information directly from your customer within an interactive form and have that updated within the specific record or field in Salesforce itself. Now what this means is, typically, these processes, and I alluded to this at the very start, of this webinar, when it comes to arduous tasks, updating the CRM can be one of those from a sales or a service perspective. What we can do is actually enable our customers to do that. And longer term, it means that there's more positive business impacts. If we think about a situation where we're missing invoice and details, within our CRM, or they're out to date, whatever it may be, and we have to collect revenue from that specific customer, that becomes a very big business challenge that we need to address. So having this, automated process, really makes life a lot easier for, the people within an organization, the organization, as well as their customers. Mark, just on that. So correct me if I'm wrong, but you're talking about clients external who obviously haven't got access to Salesforce, and they're completing forms and so forth and bringing the data back in. But also that means, as well as external, you're looking at possible teams who, again, don't have access to Salesforce who are internal to the business, and I get this a lot in insurance, where, like, an underwriter or a claims may not have what the distribution teams have. So they could actually collaborate on the documentation as well and push that back into Salesforce and capture anything from there. Yeah. Exactly. So what we can do is for people and I'll condense this into the most simplest of of sentences. Sorry. Excuse me. For people that that might not have access to Salesforce and whether that's, like, an internal person or someone external to the organization. If there's a need to collect data from them, they can use this within an interactive form, and there isn't a need for them to have a Salesforce license. Excellent. And that means that the information can be updated directly within our CRM. So your CRM is always gonna be continuously updated with the more current up to date information. Exactly. Yeah. And I I really think this is like a it's a really cool, use case to say it plainly because what we're doing is using agents to maintain data hygiene within the CRM. And, yeah, that that makes me pretty happy, to be honest. Not me. Hand closed. And clients. And our and our invoicing team as well because they know who to send their invoices to. So what I'll do is I'll just do a quick f 11 and jump over into our recording. And, Anthony, if you can just let me know that you can see everything can. see everything. It's all gone black. No. Joking. It's it's clear. Thanks. And I'll I'll basically just click play. So what we're doing and actually, just to preface this a little bit, what we're doing is quickly having a look to see which of Chrissy's accounts is actually missing data within Salesforce. So we're narrowing this down to the specific user. And I just want individuals to think about, like, what this would look like if we didn't have the automation and the Salesforce agent as part of this workflow. At every step, just think about, like, sifting through accounts. How long would that take? The creation of documents, how long would that take? Following up with customers, etcetera, etcetera. So really, the the gain here or the efficiency here is is time saved, I would say. And I would love to hear everyone's thoughts about this as well. So please, like, leave comments or ask questions in the chat. But, yeah, to to continue with the demo, I'll just press play. And what we can see is I'm interacting with our agent. Show me all the accounts owned by Chris with missing billing information. Our agent is able to respond to us after it connects the dots. And here are a list of all of the accounts owned by Chris with missing billing information. That in itself would take a lot of time to kind of sift through and find if Chris has multiple accounts. The next part, send a data collection form to all of them. So the data collection form has been sent. So I'm gonna pause here. This is one thing that that happens to me, kind of in a day to day kind of role, because I interact with customers through the dark region as well as further afield. But what we're actually what we've done in this instance is provide a level of localization to each of our clients. By sending the form, you can see at the top here, we have the first document generated in French as well as the email in French. The second one to Rachel Patel, that's in English. And we have our third one here, and we can have a little look at what this is. Naturally, it's in German. And lastly, our Finnish email as well as we're a Finnish company. And the client just clicked into the link there, and they're presented with this interactive form. So in this particular instance, we are seeing the contact at Northwestern Memorial Hospital. So there wasn't a need for them to to log in to a particular system. And within here, they can update the relevant information. So we need the VAT number, the billing street number, the postal code, etcetera. And then from there, they can simply just submit the form. Now one thing I would highlight, and we didn't include it here in this demo, but you can also build in, validation rules or required fields that make it mandatory for clients to fill in a specific box before they can actually submit the document. We have our landing page, and that can be dynamically selected. Within an instant, the document itself has been generated and delivered to the specific client. And if I go back into accounts, we'll have a look at Northwestern Memorial Hospital. We can see, actually, as part of this automated workflow, the document has been automatically saved within Salesforce, so we have a record of that. And if we go into details and we have a look at the billing information, you can see that that's now been filled in. So the customer themselves has submitted the information within the interactive form. As soon as they hit submit, the billing information is now updated within our CRM. Mark, I'm amazed there's only four clients which need to be updated. Knowing Chris, I hope there'll a lot more. We had we had to truncate the amount of client that had to keep up on the the string. So, yeah, I really hope that that's a kind of it's a short demo, and I suppose that's the intention in so much that the main kind of driver here is time saved, enabling people to focus on what may be more complex tasks. So in this instance, for Chris, he he'll be off speaking to other clients, and getting them onboarded and leaving some of the more arduous tasks, to the Salesforce agents. So at this point, I'll go back into the presentation. And, yeah, I'll I'll open up the floor for some questions, and we'll endeavor to answer them as best as possible. Well, we've already got we've already got some questions through. oh, fantastic. And I would say, like, please, leverage Flockhart's expertise. He is he has so much, experience working with our customers, so please ask him, and myself and and Anthony, any questions that you have. Should we should we go the first one, which was from Kurt Stall, which was very early on at five plus four? What does DocNor offer that Omni Studio doesn't? Yeah. I think that's a a great question. I can answer this or Flockar if do you want to answer this? Feel free to go ahead, Mark. I put my answer in the chat, but I'd love to hear your perspective. as. well since I think you get this question way more than I do, on on the sales front. But, yeah. So from my perspective, I think the the thing that we offer most is the ability to really manage templates in a more effective way. Rather than building out templates across multiple languages, we can actually condense them into one singular template. One of the things actually or a case that comes to mind is we've been working with a manufacturer. Before working with Document, they had over 800 templates. So across, you know, different MSAs, quotations, proposals, whatever it may be. And using DocuMill, we're actually able to condense that around the the 40 mark. So I think easy to build templates, first and foremost, and the ability to manage templates more effectively, especially if you're working, across multiple languages. At Flocker, out of interest, I didn't see what you put. So what would you how did. you answer that? Very, very similar to to your answer. I would say, I think we excel on the template building side, and we're also constantly updating the template builder. So we're always making it easier to use, and it is what you see is what you get type of editor. So you don't necessarily have to be extremely technically inclined to to use our template building as opposed to in the chat with OmniStudio. That technically does require some more knowledge, and and, like, there are more prerequisites to set it up, especially. But with us, I think you can easily set it up in a couple of hours, never having it seen before. You can start to generate some documents and at least, like, get a feel for the tool and then eventually, like, work up to to build your your full scale and launch your templates to the production. I think. sorry, Ma. I think what stands out for me a lot is the collaboration piece, negotiation piece as well as the esignature, that whole workflow around that, enabling people to work outside and inside Salesforce. So I think we're adding a lot more value to what's already an excellent CRM and bringing out the more value. Sorry about interrupting. That and that's that's absolutely fine, and it's a it's a very good point. But, yeah, I was just gonna echo and block our sentiment there. And one of the to answer that question actually or or direct you to the AppExchange and have a look at the reviews, Yeah. from some of our customers as well as, like, the various SIs that we work with. Because we've had people that don't have, like, code and experience in the past. And and I'm an example of this as well, actually. I'm late. Actually, use our and Anthony as well. Use our template builder to build out documents, and we are kind of business operations type individuals. So, yeah, I think that's a very good point, Flocker. So thanks there. Excellent. Just question two from Darren Carpenter. Do you work with other Salesforce agent solutions, for example, or two agent? And I'm gonna take that. It's very simple answer. Yes. In particular, we work quite closely with or two as well. We love the fact that they can actually help with the routing process or routing, as Mark actually said in the presentation. And that process can be driven by sentiment. So I I came up with a a really good great use case around, well, the commission claims case with with automobiles, where they wanted to really prioritize which claims were more important, where where there's a sort of a sentiment required to work out if there's a real struggle with this claim. Using something like OR two, that could be done very nicely. So, yeah, good question, and we do work with other agents as as as well. Then the third question, are we able to, summarize the document using agent force? No? Yeah. I can maybe be briefly. go go over that, unless unless you wanted to touch upon that as well. Off you go, flock up. Yeah. Thank you. Yeah. So, essentially, during the generation of the documents, we have the capability to, like, stamp, let's say, different HTML markup throughout the document. That would essentially allow a tool like Ordos agentic solution to scan document and potentially summarize it. Then, of course, it it very much depends on on the the prompt that you're training and and the data you're feeding it to train. So it can definitely be done. But, yes, it does require some more, thinking about how to best achieve it. And it obviously differs from business to business. So Excellent. And Sankara, sorry, Sankara, Shesh came up with another question as well. Are we able to use voice assistance for agent force? Yes. So, I answered as well. And, I I mean, as long as it's supported by Salesforce Agent Force, it could, in theory, code it into the the prompt template. And and then with with the voice over, I think there are some solutions as well which are specializing in this also. You can essentially speak to the agent instead of typing to it. But then at at the back end, what's happening is that there are Salesforce flows and then API calls that are making the generation of the files happen. So, yes, in theory, yes, it can definitely happen. Excellent. And then we got Felix, who's said, is the agent able to see which fields are missing from the account and adding? Yes. So the the the prompt, the prompt template within the agent can be trained to essentially scan, let's say, agents that are missing certain data, and and then that could be, populated, either automatically. We could also, scan those missing and, like, fields and and input default values that can then be used in generation to decide whether we show the field or we add default value, etcetera. Okay. Excellent. And then Felix again, is the agent translating the templates on the fly, or do you need to maintain them? Yeah. So so, currently, the templates, work basically with the with the manual, translation, and and Felix actually is is rather familiar with Docomo, solutions. So hi, Felix. But yeah. So, currently, we don't have, like, an out of the box, agentic, like, translation module. I'm sure that will come in play later on for, let's say, translating documents. But, again, that would be slightly outside of the scope, I would say, of of the current, agent that we're providing. Could I just add a little bit to that as well, Flockhart? Yeah. So, yeah, I think your your answer is absolutely spot on, and it's one of the things that we need to be a little bit cognizant of when it comes to AI translations, especially if we think about, like, the manufacturing industry as an example. And if to dive a little bit deeper into that, like, if you think about gym equipment and what they're kind of called, like, stair masters and things like this, I'm not sure if we're at the point where we want to leave responsibility for AI to to be able to determine whether they should translate specific words or not. And if you did make a mistake there, it could be a bit of a brand issue. So I think as things stands, in my in my opinion, the best practice at the moment is to have that human element still for the translations within our matrix. And that just really ensures, that you have the correct meaning within your documents. And I I. could actually talk about this at length, because it is something that I'm particularly passionate about. Words and their semantic meanings can range depending on the context of of what they're used. So, yeah, I think it's good that we do have manual, checks still in place, and that's via our, translation metrics. I agree with what he said. Thanks, Anthony. No, excellent. No, completely. At least someone does. Yeah. Excellent. Any more questions coming through? Okay. In case anyone didn't realize, there is, like, a a giant QR code in the middle of your? screen. So please, like, feel free to scan that. And if you want to to chat with us a little bit more about the applications of Salesforce agents and how they can affect not only sales processes, but service processes and beyond. We would really love to to talk to you about that. as just got how they interact with, document processes. But let's see if we have some questions. So keep them coming in. yeah. In can the agent be used for on-site observation at a client where the user can and then it stops. So so the rest of that. question is is. oh, Oh, that's you see it to your mic? yeah. I've I've got it. Yeah. So in Baloo, I really hope my pronunciation. was well. there. I haven't studied French in almost two decades. But, yes, it can. And I actually have a recorded demo of this. So what I can do after this session is I can send that across to you so you can see what that looks like where Actually, the user, the field service agent is actually taking pictures in combination with Service Cloud and linking that into the the document. So yeah. Nice use case in real estate for that, doing the valuation reports on-site. Excellent. So I can't see any more questions. Shall we get the results of the poll? Yeah. I think that may require me to stop sharing my screen. Okay. I'd I'd. like I'd like a confirmation of that. Yeah. Yes. Okay. Yeah. That's correct. Yeah. Yeah. Cool. However, before I stop sharing my screen, the last thing that I would like to say, is thanks for taking part and and for joining the webinar and chatting with us. But I'll stop sharing my screen now, Tim, and I'll hand over to you. Beautiful. Thank you so much, Tim, for that. That was I particularly really like to see it in action, the demo. That was that was really, really good. Beautiful. Are we for those poll questions, are we able to show the poll results on screen? Here we go. So what is your biggest challenge in document workflow today? So we got number one was managing templates and document versions. So that was a perfect demonstration and a perfect, you know what was it? Eight was it did I hear you correctly? Sorry. Was that 800 templates down to 40? That's a 20 times reduction. Is that right? Yeah. Yeah. So one of the cases that we've been working on is really reducing the number of templates that organizations use. And you're right. It was for this specific organization, we were able to reduce from over 800 down to to 40, and that's based on how we actually can create our templates. It's using conditional logic. So yeah. So it's a fantastic application of our technology. Beautiful. Beautiful. There you go. Well, 60% of the audience will be able to benefit from that, I reckon. That's significant reduction. That's what we like to hear. And then second place, too much manual work followed by handling higher document volume as we scale and approvals or collaboration delays. Beautiful. And then in terms of the agent creation, think was the next question. There we go. Move. So have you implemented a Salesforce agent workflow before? Majority have not. There you go. Okay. So I would ask one or two things. And the first thing is for those five people that have said yes, if you could send me an email and just share a little bit about what the use case is. I would love to know more about how you're currently interacting with your customers using agents. And then for the the 18 plus people that have said no, yeah, I would urge you to go back to the QR code scan, and then we can set up time to talk about how we can actually encourage you to do so and and what steps need to be taken there. Beautiful. I think I saw one comment in the chat that said not yet. Oh, Yeah. beautiful. There we go. I'm also gonna send the next thing is the email. oh my go. god. So, the email's in the chat now if you wanna be able to reach out to Mark directly. Beautiful. Fantastic. There you go. Was there anything else, Tim, that you wanted to say before we wrap up? From my side, be worth, just from my side, as echo Mark's sentiment about thank you, and please reach out if you need any help. We've got an excellent team, primarily headquartered out of Finland, and we'd be happy to help you wherever we can. Beautiful. I was gonna say, Mark, did wanna briefly show that QR again potentially? And there's also I've noticed. in the chat that Mariam has pinned the link as well. So if you wanna jump into the chat, there's a pinned comment that says here's the link, which has the same link from the QR code if you were interested in following up with the documentation. Let's see if I go back. Yeah. There's the yeah. Beautiful. There you go. Well, team, thank you so much for joining us. That was a really, really insightful presentation, and that demonstration here was brilliant to see it in action. And thank you everybody who joined us as well. I really hope you've gained a lot of value. Know I certainly have. We highly recommend you sort of reach out to the Document team as well and follow-up. And. with that, I think we will call it. Yeah, thank you so much. Appreciate it. Cheers, guys. Thank you. Thanks, everyone. Thank you. Take care, everyone.