Name: The fast, simple steps to building document agents
Uploaded: 2025-10-28T16:16:07.016Z
Duration: 1 h 24 s
Description: The fast, simple steps to building document agents

Transcript for "The fast, simple steps to building document agents": As always, John Taniakos, senior principal customer success manager at Templafy. If this is your first Templafy talks, you are probably in the wrong place because this is part three of three in our document agent series. The first two are available on our website, and I think my colleague is gonna post them in the chat now. But yeah. So this is part three. And today, we're gonna show you behind the curtain of Templafide Talks and how to set up your document agents. We're calling today the fast simple steps to building document agents, and we'll, figure out later on if that is true or just a clever title. So as always, we're gonna start with a guide to the rules. So we are partnering with Goldcast for this webinar. On the right hand side, you'll have a chat where you can ask questions. My colleague, Casper, he's, behind the scenes, far too ugly to be on camera. He's gonna answer any questions that you have, and, he's actually gonna be in Copenhagen. So as a test for the chat, where are you coming to, were coming to us from today? Sorry. Trying my teeth in for the dog. Fantastic. In exciting news, we have recently, returned back from London. Myself and a few timber fires, had an event, and the event was all themed around, yes, you probably guessed it, document agents. We did an introduction to document agents, very similar to what you've seen in the previous Templafy talks, and we also had our customer ABB share their Templafy AI journey. And we actually showed the document agent being generated using ABB's template, which is very exciting for those in the room. Our customers and, prospects and guests had a chance to try the document agents out firsthand as well. It was a fantastic day, but don't take my word for it. Let's take a look at what our guests said of the event. The event's been fantastic so far. I think what I've really enjoyed is, one, learning more about the product and the new capabilities. Two, seeing real examples from real customers that are using it, understanding how they're using it, but then also seeing how they've had to think about adoption, how they've had to think about helping their own employees understand what's possible and understand how they can and can't use it. And then the third thing, just kind of really getting hands on with a real demo, hands on myself and seeing how kind of, you know, I could use it in my own work. Thanks for exciting time to be part of the, say, Templafide journey. I think it's got some real positives that would have huge impacts at Turner and Townsend. And my hope is that it will be part of a bigger change towards, using Templafy in ways that are creative and, productive and exciting and liberating for people to give them their time back ultimately. One of the highlights from today was, especially the presentation on the next steps and and the future steps of Templafy in combination with AI, the agents. It's it's next level. It's really exciting to, to see next steps and how it can be, be implemented at, at clients and and at at our own company, of course. I guess you're jealous that you missed out, but don't worry. It's not gonna be the last time we do a Connect. So next time, please keep an eye on the socials, and you'll see, not only highlights from that event, but you'll also, see when the next Templafy Connect is, and you can come along and, be part of the event. Fantastic. Time to introduce my guests for today. So the first guest is returning to Templafy tur talks Templafy Turks. Templafy Talks for the fourth time. He is a, Templafy legend. He is all things product. It's our VP of product, Oscar. Hello, Oscar. Thank you very much. Yeah. I'm, happy to be here. I'm surprised it's all with the fourth time because, time runs runs by fast. It really does. Yeah. And Simplify talks also celebrated his birthday recently as well. So, three years old. It's not about me. Our second guest, was the unexpected star of our London event, and I think if she had a pound for every time she answered a question at that event, she'd be a very, very rich woman. Please welcome senior product manager and all around Tempur five legend, Barbara. Thank you so much for a very, very kind introduction. I'm happy to be here. You wrote it, so no shit. Okay. So as mentioned, you know what document agents do. You've seen that in the first webinar, document agents one zero one, and you know the use cases because we showed some, some real world examples with Christian in the second part. Again, as I mentioned, this part is the fast and simple steps to building document agents. So I guess my first question is for you, Barbara. What should our customers think about when setting up a documentation? That is a good question and a great way to introduce the topic. So when we think about what makes a great presentation, it's barely or solely not just the content itself. It's the way it sounds, it's, how it looks and how it all comes together. And this is very much where, the document agent comes in and how it works. It doesn't just build the slides. It makes sure that it learns your brand and learns how it speaks, how it works, and how to express ideas visually. To be able to do that, it relies on three main ingredients. And as you might have guessed, it's your tone of voice, it's the images that you have available, and the template that is powering behind it. If you think about all those three main ingredients, they essentially create a creative, what we call, a brand DNA of your brand. It lays the foundation to ensure that every document that is created does not just sound familiar, it looks on consistent and polished. So let's walk through every of those ingredients one by one, shall we? Yeah. Starting starting with TotoBoys. So people often think about documents or presentations in particular, as visual tools. However, what makes them stand out and, what kinda, makes them lens essentially is the way they speak. And so the tone of voice is what gives your brand, personality. It was it's what turns the information into communication. It turns every side slide or every deck or set of slides into a storytelling. So when we set up, universal document agents with your tone of voice instructions, we are pretty much teaching it how how your brain communicates. And the setup, it really could not be any simpler. So let me just quickly show you how it's done. As you can see, we are in the admin center navigating to your AI assist. Now we need to sign you in. Good. Well, it's good. Just just tell me to always stop in mind and tell me why. Alright. I shouldn't have prepared so early before this recording. Alright. I'm back in. So now we're back in AI assistant. And as you can see, there is a tab at the top right corner called tone of voice. It it really is that simple. We have already a default tone of voice, but, likely, every brand has his way of speaking, so you would like to adjust it to what represents you and what sounds authentically just like you. So I'm just going to go delete this one and paste my tone of voice instructions that I generated for this purpose and hit save. It's easy as that. So so on the tone of voice piece, so that was quite a short paragraph on how to sound. And some of our customers have, you know, quite extensive text, and they were even down to how date should be formatted and should we use active or passive voice, those kind of things. So, what in that example, why was yours how did why would why did you, opt for such a short tone of voice? I just, took actually, I took Simplify as a way of, how do I wanna sound like. Took our brand, which is Guru, asked you to represent the base, the tone in multiple different ways, asked you to highlight what the differences could be in terms of conversational aspects. So I applied a scenario, took that and then piece and puzzle together, the aspect that I like from one, tone of voice that is still within the brand, but maybe sounded a little bit too rigid or too professional, too formal, gave it further instructions, and this was the final output. So I worked with AI to create those instructions because we might have an assumption of what AI understands when we write it. But if you work with AI, you can visually see how it's represented, what you wrote in and essentially. So that was the output. Fantastic. So just for the purposes of the customers at home, if they have an editorial guideline, how can they turn that into a tone of voice? Is that something that we can help with? Very likely so. Yes. We have the professionals that have have been trained on how to convert custom guidelines into tone of voice and or or else you can use the, approach as I did where I just used AI. ChargeGPT is available essentially to everyone. Upload it there. And just through the conversation with ChargeGPT, it will help you also kind of, get on the right track of what those instructions should be. Perfect. So step one, tone of voice. We can help you with that. Use AI. Perfect. Yes. Thank you. Alright. You're welcome. Now we're going on to the second ingredient, which is the images. And these are far more than just visual tools. Images typically also when you see the presentation for the first time, they introduce the context and provide clarity way before the single word is read on the template. That's why or on a on a deck. And that's why they are very, very important. Luckily, for Templafy, they're also very simple to actually set up. So let me show you how. You go into your image library or, actually, library. You found your image folder. And, essentially, what you need to do is when you have your repository of images, you zip it into a folder, hit the upload upload button, you select the file that you'd like to upload, and up up you go. Now it's gonna finalize the uploading and processing of those images. File has been uploaded. I can close it. And as you can see, it's been added in here. The beautiful thing about Templafy is that we already have AI tagging and AI vision running in the background. So, essentially, it populates all the metadata on the images, without you having to do anything. So as you can see, I already have the name, the tags, they were populated to AI, as well as the alternative text. So as a as an admin, managing that image repository, I really don't have to do anything else on top of that. You might as well want to if you wanna, you know, manage your tags and you have any specific tags or images that need to be tagged in a certain way. You can definitely do that, but you're pretty much on a good set already here. Saves you a lot of time. It does. Awesome. So how do you get the agent then to use the images? Yes. That's also a very good question. So as I said, it was very simple, and, a agent does not pick images randomly when it comes to generating presentations or the final output. So, as we go through creating a presentation, we validate the user input. We create the content strategy for the deck, and then we start creating the content for each individual slide. And only after we have that content for a slide, we then find an appropriate image that, you know, correlates to the text that you have on your slide. The beautiful thing is that we are combining multiple technologies here in the background. So the metadata that I just talked about is one thing, and another is the vision model that processes images and creates a repository of descriptions of what those images are, merges them together, and tries to find the best match. So it's not random. And maybe I would like to also highlight that the agent, as it creates the presentation, also takes users' access rights into account. So you don't have to worry as an admin that, images that are users not supposed to use or do not have access to use because they for any restricted reasons or security reasons, that's not going to happen. We're going to respect that. So as you manage your, image repository, just make sure that the folders or, the folders or the assets are actually filtered for the targeted audience. So just to recap then, so if I've already if you've already got a good folder structure with the filters, set up for certain teams to have access to certain images, the documentations respect that. So the users will not get, you know, images in their presentations that they shouldn't have. Precisely. That's exactly that. Fantastic. So is it is the Templafy Image Library the only image source at the moment? Yes. That is the case for now. We're looking into expanding it further. So we know that a lot of our customers do have, repositories that are residing in done as a digital asset management platform such as binder or frontified. Mhmm. So we're looking into how we can extend the search and compile it in, and extend it for the pool of available images for the final compilation of the presentation. Fantastic. So that's tone of voice, check. Images, check. So what about the template then? How do we know, you know, what's the building blocks for the documentation? Yeah. A template is really, really the last piece of, of where the piece of the puzzle where it all comes together. When you think about your template, think about it as a bridge between, creativity and consistency. So it, by defining that template, you're actually teaching the universal document agent or any agent in particular, what your branch should look like. The beautiful thing about defining that template is that you are in control of it. You define what does the layout all the way to the placeholder names and how they should be styled. So you're essentially, by feeding you that template with a certain type of layout, you're telling the agent what your brand is, how it should be visually represented, how a data should be presented, and how those, ideas should be then, visually expressed. And how how for example, block of context, in different ways. Mhmm. So there's a lot of, tools out there that claim to be able to create, you know, brand documents, for example, but there's a lot of configuration required, and the outputs are very, you know, still very mixed. So what in Templafy's case, what makes a good starting template for the document agent? So good starting template is a representation of your brand. So we have to think about all the branding elements that you would like to have in it. A lot of the tools on the market actually do not have that capability. That's where we also differentiate of, in many of the cases. But, I know it could be a very daunting experience to go and now create a template that should serve a universal document agent that we also claim to help you with any at home document creation. That seems like a huge undertaking. So if you don't know where to get started, essentially, think about the document structure. Any document as a good starting point would be that any document has a title or a cover slide, that it has an agenda slide, and it has dividers or section breaks. So that is the skeleton of your document that is already accounted for. Now, a lot of the documents or even any sort of documents that, you create would have some tip topical themes or, categories of, layouts that you would like to include. For example, a timeline slide or user journey slide. So or a process slide so you can, express that visually, in a more natural manner. Secondly, when we talk about how to divide context, so we have content heavy slides, then you have two slides. So it's a comparison. Could be a three block or four or five block. Mhmm. You would like to also include slides such as team slides in case you need to represent a team in any of the project status updates, or it could be in the the potential pitch decks, when you need to present represent, your team or, somebody introduce someone else. Or even in the all hands. Right? When we have newcomers, you can use the team slide to introduce who joined the organization. Executive summary is also a good example. Typically, you would have that in the document types to summarize what the document is about. So it's it would be very nice to have that included as well. Awesome. So elaborate a little bit on the layouts and so it because a lot of what you're saying is in a lot of customers based templates. Right? If you look at a, you know, a blank, it does contain those slides. Mhmm. How do we make it so that the agent knows which slide is which? Yes. That's a brilliant question, actually. I'm happy you asked that because it's a beautiful version of what I'm about to show you. So I hope we can you're looking already in my screen. One thing to clarify, when we talk about a template, we are talking about what is behind the template on the slide master level. So we're talking individual layout. And as you can hear see here, this is my, template that I've created for my own, environment and for my own document agent. The first slide that you're looking at right now is a title or a cover slide. No one knows your brand as good as you do, and not even AI can do that. So the way you can help it to get the result and make the same choices when it, creates the content strategy is to actually take a look at unit layout names and, name them properly. Right? So, so AI cannot get confused about what is the title slide, what is an agenda slide, and what is the timeline slide. If you have multiple versions of a timeline slide, for example, we would also expect expect to say, let me see if I can find it. I have two timeline slides here. So in the naming convention, I also made sure that it it knows that this one is a timeline with five events as opposed to the second timeline that has eight events if it's seven events, eight events. I should I should fix that. So, it's really just about using using, you know, human friendly names, how you would distinguish, picture a between picture b. This will help AI immensely making sure that, you know, the right content lands on the right layout. And it goes even further than that when you think about it. Because when then you have, hierarchy or a correlation between certain placeholders on that layout that should be contextually together. So in the example of timeline slide, not only it's a sequence of events Mhmm. But they also have in my, in my example, they have a header and a corresponding description. Right? So what I need to do is by now is say that this is a milestone header one, and this is a milestone one description. Mhmm. So then a, I know that these two belong together and does not make milestone three, the description for milestone one, and so on and so forth. Additionally and when I said you are in control, I also meant you to the very detail of that layout. Right? So my, all those placeholders are styled. Here you can see I have a month in the size of 10, and it's bold, whereas the other placeholder has a different font, and a different size. It could also have bullets if I wanted to. Mhmm. And this is always you set it up all on your placeholders, and, document agent will respect that always. So, essentially, once you're done with all of that work, that template is going to dictate everything when it comes to your brand, and it will become your always available designer of permutations. I really like it. I think it's a lot of our customers already will have you know, we're very, very strict on these kind of rules. But if they if they're not and if they wanna, you know, when they become a Telify customer and they wanna configure their document agents, how do they go about it? Is that something they can we can help with, our solution and so on, your team? How does that work? Yes. So, it would be part of the implementation process where you scope out, and that's where you also go through the discoveries. Like, what is it the type of documents that I would like in my organization to have covered, and therefore, what type of layouts do I need to have included in my template. Right? So we will help with that and also the creation of those layouts Mhmm. As well as naming convention. Once that is done, you're pretty much really good to go. You save this template or we'll do it for you, upload it to admin center, and you're ready to get tested. And if you don't like any of the results or how things look, because sometimes it could be that it looks good on the layout and then the text does not align or you forgot to do something with one place holder, you just go back, align it a little bit better, re upload, and tweak and test. That's pretty much it before you are ready to roll out. That's really good. So, essentially, full support from the Semify side in getting customers set up. So one of the things that we've been doing as well is, obviously, been doing a lot of POCs with customers, so introducing documentations to them. And it has been really rewarding seeing the work that your team have been doing in the you know, starting off with the configuring the template for them. They test with the users. We take that feedback on board about, you know, oh, we wish we could do this. We wish that this slide looked like this. We implement those changes, and you see the, you know, the adoptions and the and the value it's bringing. Because I think from the talking back from the London event, one of the guests when we said because we claim this is gonna be over around 30% completion, 30 to 40% completion of the document with the context when you generate. You can look at the previous time if I talk for a bit more about that. But one of the guests at the London event said it got them around 60% in their testing, which I thought was was really clever. So what can customers do to get, you know, an even better result from the document agents in this stage, like in the setup part of your, the layouts? This is actually it. There's not much more to it, really. You just need to be, crisp on the type of layouts that you introduce. If you're lacking imagination or you don't know where to get started, for existing customers, the advice would be and this is the process that I personally went to with some of our existing customers that we ran previews with. I looked at the library content inside so you can see what your users are typically inserting into presentations and use the most used assets as a point of reference. Oh, these are point of reference. Oh, these are possibly layouts that are so, widely used that, likely, it will be beneficial to have them in document agent. For, for new customers or prospects, I would say that, take a look at the finalized decks, especially the best practice examples as a, you know, what good looks like really and transform that into that template that powers our document agent. Amazing. And just to clarify as well, this isn't replacing this the core company slide master. They will still have that sort of Yeah. You know, in library configuration in Sembify's case. They'll still have that core template. This is something separate that you're setting up for the agent specifically. Yes. Good to know. Yeah. You can do it both ways, but, if you're still have a separate one Mhmm. Specifically powered by document agent, you can definitely do that. Awesome. So just to recap then, we've configured a tone of voice. We have, found a source for the images, which is Templafy, and, assessed that you will only have images in a presentation if you have access to them in Templafy. And we've created the template with the layouts. So I would be really keen to show with just those three simple ingredients what kind of cake we can bake with that. So do you wanna share give us a demonstration? Absolutely. I would love to. Alright. Lisa, let's just get started. I am determined that I'm going to build my document using yes since now I have availability, to use a document agent. Right? And I have my bespoke, document needs, which is I wanna create an internal strategy, flooding deck, cater for my leadership team, and the goal I'm writing down the goal is to align current positioning, articulate a vision, strategic pillars, and the main KPIs, and so on. And since I'm attaching a document that, I'm as mentioning that specifically because sometimes I tend to not pretend that the document does know what to do with it. So the more you can write about how the document should be used and what should be focused on, that's exactly in my prompt. And that is also one of those things that could push, the actual creation or the first draft from 30 to much more than that. Okay. So and since I'm saying use attached document, don't do that when people send emails. They tend to see document attached and nothing sends, and there is none. So let me just, to do that. So I will take my planning brief and hit send. Simple as that. So what's it doing now? It's actually reading the contents of the document and trying to come up with a summary of what is, what is the content that content or context that was provided. It's thinking about it, summarizing, and, also, trying to prepare potentially a narrative or determine whether I provided in that context, or it's gonna ask me clarifying questions. If my prompt was very nonspecific and, there could be very much open it would be very open. And this, for example, I wanna create an all hands presentation. It's like, I understand your intent, but I'm not entirely sure what is it that you wanna include, what is it that you wanna, you know, focus on. So it will ask those questions for you in case you forget to for you know, provide it upfront. Given that my prompt was quite comprehensive, I actually skipped couple of steps or or yeah. Skip couple of steps where it presented the narrative to me, and it's exactly the sections that I asked for. Right? So the current positioning, the vision, and the strategic pillars, the KPIs, and the timeline. Here, I'm thinking for the vision and strategic pillars, it's way too many, way too many, slides. So I'm just gonna keep it to two. Mhmm. Because I just want one for vision and one for the strategic pillars, for example. So the user still can control the output from here even though the agent has set a structure? Exactly. Same here. And if it if it just so happens that you forgot to add a section or you don't like it or the ordering of it, you can always do so. Okay. So we can click add the section, delete a section, and adjust the number of slides. That's what I typically do because it tends to be a little bit too much. And since it's a short strategy deck, and for the demo purposes, we don't want to just see as the slides are being created one by one. I'll just shorten it a little bit. So let's just say I would like two slides. Also, the nice thing is that if it's if the number of slides exceeds, you can just add it the last slide, and it will just, retroactively also, update the slide the number before. Awesome. So I'm happy with the outline. It shouldn't be too long of a presentation, so I'm just going to hit create. Awesome. And, again, on this interface, I really like it because you get sort of a an understanding of the steps that are happening each time. Mhmm. And I like there's a progress bar at the bottom as well. So this is this is a relatively new, introduction. What's happening now then? Yes. So as you can see, it's actually reporting on the update real time. First, it's emphasized on the information it received, prepared a content strategy. And once it processed all of that, it's now creating individual slides one by one. And here we're talking, as I mentioned, in terms of how we do image search. Right? Now it's just creating the slide content Mhmm. So it matches the content and finds the appropriate layout to represent that content in. Once we generated all 14 slides, we are then going to move ahead and try to find corresponding images to those slides individually one by one. That process is usually very, very fast. So sometimes it just skips over that steps, but, visually, it's so quick that it may not even register or you may not see the corresponding UI for it. But, yeah, that's pretty much the gist of it. Awesome. And so is it always gonna be 14 slides? Because it says at the moment now it's showing slide six out of 14. And what about divider slides, title slides? Do they count in this 14 as well, or are they Yes. They counted in the 14, but what you might have noticed in my outline, right, that I might have that there's four sections. All of them were approximately two slides. So let's say eight. But because I have four sections and we do not count the title, agenda, and the section dividers into it, that ultimately adds to the final number. So that's something to be mindful of. You don't have to add a section with introduction. We already take care of it for you. Fantastic. Anything to add, Oscar? Yeah. I think one thing that, I always get asked about at least when when showing this to to customers, that is, that like, what happens to all this information? Like, what happens to to the documents while you're attaching here? Like, are you saving that back at, like, the list on on some of our server forever? Yeah. But that's something that, like, we've been very, conscious around at least that, you are it it's not staying there forever. It's something that is happening in the documentation process. Mhmm. And that's it, basically. So that it's not something that, that we will have, going forward. So So you're using it to train a model. It's not saving any of this information. Exactly. So that you can, yeah, stay safe and private, in that regard so you can upload anything, basically. We do actually have a a white paper on document agents for the security. I'll make sure that at this stage, someone, Casper, uploads this in the in the chat if, and, also, it's on our I think it's available online as well. But we'll send a put a link in there, so you can learn more about security. So it looks like it's finalized now, Barbara. What's happening? Exactly. The presentation is ready, and it's opening now. So let's take a look. I have my title slide. My agenda with all the things that I wanted, the vision, the pillars, the performance, and the timeline. And now we just picked, the content from the word file that I've uploaded as and, matched it with the most appropriate layout. Something that may not have been seen when I shared the master layout, is that I had this permit where, I said that this is the most appropriate layout based on the naming convention for something that is either hierarchical or has some logical feeling around it. Mhmm. So, obviously, when I talked about strategic pillars, it picked the right layout for it. Just like when I talked about the financial things, I have a ROI or KPI slide that it picked and, populated the numbers over there with the descriptions on it, and so on and so forth. And just like timelines, right, I've talked about a strategic timeline for the initiatives and the milestones, and you know that there is five. So they fit the five step timeline instead of the eight one Yeah. So that you don't end up with empty placeholders moving forward. This is awesome. And so I can also see that you've got on slide 11. There's an an image in there as well. That's gonna come from your demo environment. Yes. And then the tone of voice in each of the, texts generated would also be abiding by that rules that you set up in the Exactly. The document in the admin center. Sorry. Maybe one thing to highlight, just the learning for myself, I need to improve that on the template. As you can see, it added a number here as I would expect. Mhmm. But this is also a number of placeholder. So maybe as you look at the naming convention, make sure to also state, should it be a number that goes in here, or is it a text only? Because, you know, AI does not always know. Even if it's a KPI slide, it doesn't know where the KPI should be represented. Is it this this text field or the other one? Right? So went from my mistakes. But, again, if you if you take you just had a a document, right, which contained information. To get that into a presentation using just a template Mhmm. Would take a lot of time. Not only do you need to figure out what slide best represents the information you're trying to convey, you would then have to actually put that information in, iterate upon it, you have to find the right images, and also you have to when you are writing the information, you have to make sure you're adhering to your company tone of voice. Yes. This is doing all of that for us and and as we saw, like, not long at all. Mhmm. And so and then you can still iterate upon it and perfect it from here as well. So I think it's a really good example. I think one of the the yeah. AI is really good at contextualizing the contact that you context you provided to one of the other use cases that I really like to show, I think, the power of AI behind it, is when you have a, customer, customer meeting notes. Mhmm. In those meeting notes, you can just take a transcript from Gong or the summary from Gong as an example. You put it in a word file. A customer had asked couple of questions. You know that let's say security questions. You've attached a security questionnaire, and then you also they mentioned some challenges, and we wanna correlate that to how, of example, our solution might solve them for them. Right? So you attach another product brief, that you think it's they're appropriate, but you don't have to do the thinking for your AI. As you attend those three files, you tell them this is where you find x topic x. This is in the security questionnaire. You, find questions to the cast answers to the question that a customer asked, and and it will do that for you while also creating a presentation that you can just send off. So that is a real time saver. So this document, for the purposes you, wanted to achieve, how far percentage wise do you think you're along? I think minor tweaks. As you can see, there is some, content overlay on this slide. And just reviewing some of the data to make sure that, actually, the descriptions match exactly how I would like to phrase it. I'll be very happy to pass it on. Yeah. Fantastic. I would say five major tweaks, and I'm ready to go. Awesome. That's that's a really, really strong example. I guess, though, Oscar, what sort of steps would we need to take if we want us to try and increase this completion? And and, I guess, the question before that is, is this relevant for all documents? Good question. And I, I almost expected that you, you want to ask that. So I brought them a couple of slides actually to, to talk into that. Yes. That's much like we planned this. Exactly. So to talk into that, I actually I want to take a little step back. Yeah. Actually. Because in organizations, like, there's many type of documents that are being created every single day, basically. And try we try to, like, depict that, basically, on the spell curve that that that I have on the screen here where, like, all the way to the right, you have all the templates. The way you just have a general reusable thing, we have all the the base elements in place. We need to fill that out afterwards. Then all the way to the right, you have repeatable documents. That's where you have automation cases. Things that, like, you might even not even have a human in the in the loop because it's part of workflow of what it might be. But then in the middle, that's where you have bespoke documents, things that you cannot automate, because they are individual every single time. At least that's been the case so far where, like, you've had people in that middle bucket where, actually, most documents have been created, but there was just no technology to actually make sure that you could automate those. And that's, of course I mean, I guess you you guessed it already, where AI is coming in because that is actually where AI is starting to be able to handle not only, like, the the template and the repeatable documents that could get speed on those, but also the, bucket in the middle with all the bespoke documents. So diving into that one a bit, what, Barbara just showed, that is where that's also a nuance within that space of what can AI do. Where what Barbara just showed, that's to get started with universal. When you don't necessarily have one specific document type in mind Mhmm. Like, you're trying to do, like, a universal agent, so to say, where you wanna create something where you can get to, like, quickly get to 40% done. But you know you won't get all the way there. Like, you might have a lot of content, but there might be review process after that Yeah. Because not tailored into something specific. And you need more context to get more done, basically. But if you shift right on this graph, basically, that's where, like, documentation can start enriching you, getting more custom, getting more context, more specific into what you're trying to do. And that's, that means you have different type of documents that are good for different purposes, all the way from, like, universal, agent and to more custom ones and also into the repeatable ones that what advanced document automation. So that's where like, I just tried to take some examples, yeah, at least on on what type of documents could could be there. Like universal agents, I think training materials, company updates, meeting preps. Like, a lot of these things, we might have some material as well, some, customer notes of what it might be. You wanna put that on a deck, so you can quickly get that presented. But it's very general. Then if you start adding more context, starting more structure and data and so on, that's where you can get into custom agents. Well, you get purpose built specific agents that, like, they're still not tailored into like, it can only be one thing. It still be tail like, general in terms of, status report. It can be for all kinds of different projects, for instance. But you can start being more specific from the what kind of data do we need, what kind of structure do we put I wanna put into it, and so on. Same for business cases, pitch stakes. Like, what are the best practices Yeah. For how do you create a pitch deck in our organization? Not that we are defining this is the word that should go in on slide three, but say, that should be an introduction. That should be a ROI calculation. That should be something about pricing or what it might be. Right? And then lastly, that's where then we'd get into, like, 90% completions that we see. That's where you start getting into advanced AI automation where that's where you have, like, contract proposals, financial reports, and so on. Like, where we wanna have the maximum amount of control because it's super business critical, but also where you are very purpose specific in terms of what do you wanna get out of it, where do you wanna get, what content into your document. So, generally, like, what drives this precision is? Like, that quality, throughout that process is context. Context of what is best practice, what is the right information, and so on. And if we like, start in the very left side, you have the templates where, like, that won't get you far. It will have a lot of the basics in place, legal disclaimer, meter data, and so on, but you won't get completed in that document. But as soon as you start adding, some, like, user input, some in intent, then the AI can actually do with universal agent, get you quite far. Mhmm. We usually talk about that expect 30% complete or something like that. You'll probably get a deck that is, like, everything's filled out, but there might be some review process, of course, because it didn't have enough context necessarily for what it, to make sure that it's precise, what you're doing. Then, when I get further up, like, some of the things you can add to then get that preciseness in custom. That's, like, knowledge. It's a structure as I talked about before as well. And then further on, then with advanced automation, we can combine it with, like, using custom agents and rules as well for that matter because sometimes you want something to be a specific way. Yeah. That's data integrations and also automation. But all the time building on top of the concepts from the previous step basically. Fantastic. So Barbara showed that Universal Agent contains the tone of voice, images and the layouts, and that gets the 30% of the way there. What can we do? How do then you go that extra step to start to get to 60%? What sort of steps can we take to increase the completion? Good question. And rather than selling, I think it's always more fun to show. Right? I agree. So, I have my Templafy admin center for the ones who have not been in there yet. That's where where you administrate all of Templafy and what make sure that you as an organization can stay in control of what has been generated, but also you can distribute best practices. Like, tone of voice is the best practice. How do you wanna sound like? How images are looking like is also best practice. But when you go into custom, they want you wanna take it one step further in terms of what is best practices. And I already have a couple of agents set up here in my admin center, but I'm gonna set up a new one, actually. So I'm gonna go into create new agent. And in this case, I can chose between, like, is it specialized or is it flexible depending on how much control I wanna do. In this case, I have a specific, agent in mind, a specific use case. That's, a performance stage reporting because I'm a product person. Mhmm. I, I need to do a a product reporting once in a while. So I and I want that to have a specific format as well. So in this case, I'm gonna say, create a presentation, and I cannot spell, about, for a weekly product report to the management team. That's something that I I do quite often, and I get this hour again. Security first. What are the Autobar token expiring at the same time? Yeah. Let me go I'll go back here and go in here and then performance status reporting. And I create a presentation for a weekly product status report to the management team. That's how you can see it's real as well, that getting locked out. Right? So what it's doing here is entering out, okay, what type of presentation you're trying to do and then creating a skeleton for how should those look like. And that includes quite a few different things, actually, where you can start getting more quality. It's, like, what's the purpose? What what are you trying to do? What is the general instructions? Also, like, specific tone of voice for this specific agent. It could be if you're doing, let's say, a pitch deck. You wanna be more convincing, more salesy, than if you are doing a report that I'm doing here to the general management team, but you wanna be more precise in terms of what are you doing. But, actually, where I think it's even more interesting and even more like, really start getting up that quality ladder Mhmm. That's where you start getting into the document structure as well as the knowledge. So what you see here is actually the ability for you to say what sections should go into this, into the status report. And so that every time it generates a status report, it will use those sections. And you can say, what should each section be about as well? So you don't have to go in and say, slide one should be this, slide two should be that. We have that flexibility. But in as you can see here, it says, like, what is the overview, analyze the general performance, summary of key performance. And there should be two to three slides. Like, the AI will figure out in the moment depending on what is relevant, depending on the data it has as well. Then it goes on, what's the progress and challenges, two to four slides as well, what is the strategic insight and recommendations, and alignment with, you can say, some go goals and data driven future initiatives. That's what it came up with from the get go. And, of course, that's where I then can start, iterating on that. I can say data driven future initiatives, I'm gonna delete that one. Up here, probably, that's gonna be only one slide to not 21, but I wanna have, like, one to two slides here. Oh, I could start adding additional, sections as well as start having saying, this section, use one of these specific layouts Mhmm. For instance. Because for KPI reporting, we always wanna use one of these three layouts that Barbara also talked about before. Like, you don't want it to have choose random, most likely. Sometimes you won't do that if you don't care, but other times you won't have consistent way of seeing reports, if you see them day or day. So if you're doing what you're what you're doing now, it sounds very much like you're setting up a template. Why would you use an agent for this and not just a standard template that any salesperson or, you know, if a pitch deck agent, for example, can just have that structure ready. Why would I use an agent for this? Because of flexibility. Okay. It's around how do you make sure that you don't like, this takes minutes to get started, basically, with distributing best practices. Where you're going to say, yeah, where what type of template, layers do you wanna use if you wanna have that control, but you don't need to. And I think that's the big difference from before. If in a template, if you don't, specify it, it won't get done. Here, you can always from universal agent, which Bob what Barbara showed, like, you get results from the get go. Here, you can add additional layers of quality and controls when you see the need for it, basically. Similarly, in here, like, just for to round this off, like, a knowledge. Like, I, this is a product report. Right? So what and I'll sort of have the right sections, then I also have and I have this. Then I have 10 to five performance and knowledge I can add. I also have, in here, I have product updates that I can I can add as well? So that way, I can add additional context, like, knowledge repositories. There's always be kept up to date. Right? So that when I create this agent, credit document based on this agent, then it will always be using that information, the latest information, so it can get more precise in terms of what it's doing, basically. What if your data lives somewhere else? That's a that's a quick question as well. Let me actually get out of this one. Because in this case, what I did like, the what I just added here, that's actually something that lives in Templafy. Mhmm. So you can upload everything into Templafy if you don't already have it somewhere else. But on top of that, like, what you can do is actually go into, and connect to the existing data source you have. So let me in in here, for instance, like, I could upload additional files. I could like, you see, this is actually some of the files I already have. But we see quite often that customers have it in SharePoint. They have it in some of the the new knowledge of possible, being rider or clean or procure and so on. Copilot retrieval for that matter. So that's where, like, starting adding it from SharePoint, adding from Glean, and so on is something that we're also supporting, and helping our customers with so that you can have a combination even of what is uploaded to Templafy on top of where you already have some AI repository of information. Just bring in real time information in there. Exactly. Opposed to having to reupload the document into Templafy. Exactly. So, that's pretty much how I wanna how I wanna set it up. Very cool. So how then do you get this into a workflow? Yes. So, like, when you wanna get through the further step, like, that's actually where you often wanna bit more control. Because if you start having a workflow, then you might wanna have some parts that you're fully in control of and some parts that are still using AI because it needs to be tailored into the specific use case, basically. And to show that, what the what it did was actually go into Salesforce. Okay. Because I think that's that's one of the common cases you see with workflow where, like, Sam will would be that whenever you are going into a new state, a stage for your deal, like, could be that now you're actually about to close that deal. So then it triggers a a Salesforce flow, where create documents based on that and potentially even send that directly on generate as PDF, send it on to DocuSign. It could be. Could be any service. Right? But those are the type of flows that we we often see with with Templafy agents and especially those where AI comes into play. For today's demo, I actually, didn't put into a flow just because it's it's hard to see something that a human is not involved in. Mhmm. So I did create a a button here, so that we can actually open Templafy and see how that works. So in this case, I I'm creating a it's a consultant proposal where I'm going in here and saying this is for Acmer Inc. That is, health care. It is biotechnology, and it is starting to update and John Lee. So this is the some of the information I did not already pull from Salesforce, but it's also adding additional information, of course, from the Salesforce opportunity that I'm coming from. So in this case, I'm just gonna go ahead and and download it instead of sending it back to Salesforce, because then we can actually see what is going on. So it's just, generating now. And I like to just notice on this point, you're you're on a Mac as well. Yeah. Exactly. Like a system agnostic solution as well. Templafy works across anything. So no matter if you have Mac, Windows, in the browser, it, it works, basically. But, as you can see here, like, this is where you have a fully fledged out document, a proposal that, that can, like, can be used directly, basically. So you you see there's all kind of different slides all the way from, like, very advanced slides where you definitely wanna have more control, more rules added, like something like this one down here with a tech product survey. We're pulling the data in. But also up here where, like, we have some fields that are, like, tailored into your input based using AI, specific custom agents, where you can also see that the like, we go in attack. Like, this was actually generated by AI, so you can figure out what part of this was AI, which one was all within control. So, that way you can, like, quickly get to a presentation that's actually, like, fully fleshed out and and ready to send off, whether to customer, to DocuSign, or what it might be. Can you still edit if you want to in this use in this instance? Like, can I still if I wanted to change some of the generated text or just to give it my own kind of Of course? I mean, you have access to your full, Tenify library with library and with your Templafy AI system as well. So you have all of that access to to all of those things, in here as well. Right? On top of that, we, of course, have the ability to insert, like, generate full slides using our agent as well. So all the flexibility you know and also more more than that is, it's available in here for you to keep iterating before setting it up. It's incredible. It's really exciting to see, like, how far we've come in a really short space of time. I think it was only April this year when you and I presented document agents for the first time. You know, already we've got lots of customers already using this and, for generating presentations and now starting to, you know, move into that sort of custom, documentation flow as well. So I guess while I've both got you here and putting you on the spot, what's next for document agents? Because, you know, if we've done so much in this six months, what's gonna happen in the next? That's a it's a good question. And, basically, what, what we're posing is, like, full on on, like, how to make sure that we we get as high quality as possible. Like, some of the things that, that Barbara also talked into in terms of, configuration, like, making sure that that get as little as possible, how to get as much help as possible, how do we understand, as much as we can inside the presentation. So we better can make those connections Yeah. Between what is the header, what is the content, but also going into adding additional data sources, adding additional control elements is definitely something that is gonna be a focus for us. So they keep building on this idea of of best practices, like being making sure that simplifies the the center of excellence, basically, of all the good content you have in your organization so that you can, add so whenever the agent is at a building stuff, it builds on the best of the best, basically. Mhmm. So that's something that we are we're gonna focus a lot on over the next six to twelve months, actually. Fantastic. Anything to add? Well, this is definitely on a strategic level, and I think there's, you know, a scale of things almost, that fall into that area. We've yeah. Output quality is what is most product for us. And, also with universal and custom agents, we also wanna push the boundaries of the completions rates, in general. Right? There's multiple ways to go about it. We're, exploring the possibility of it's gonna be not relevant for existing customers is you have a repository of your slides, that are residing in your library That agent can currently search for and suggest is not an alternative, but how about we could actually compile a presentation just using those slides or combination of slides and AI so that completion rate gets pushed from 30 to potentially 70% even for an ad hoc document that you do not have a template set up for or a custom agent set up for. Another thing that is very important of our clients and, would be, reporting. Right? The insights. Just like we have the usage insights on the existing content repository, to spot the patterns, see what performs well, what doesn't. We tend to do the same or intend to do the same also for, you know, especially for the universal document agent because you wanna see what your users are creating to see if there is needs to actually introduce more structure to some of those repeating document types. What type of imagery is being used? That that seemed very, important for people that especially in the London event, a lot of people asked about the image pattern usage trends. So these are the type of things, that we are going to look into also. And then, yeah, last but not least, exploring the ideas about how can we make it also more visually appealing or, allowing the slide or layouts that you have available that are not actually layout residing in your template to extend that repository much, much further so you can cover a lot more use cases going forward. And you don't have to do that all just within that one template that I showed you today or earlier today. Fantastic. So as you can hear from that, we are still full steam ahead on our document agent journey. We'd love you to join us on your document agent journeys. In order to do that, if you haven't already started the journey with AI, you can get in touch with us, in the link. I think Casper's gonna post the link in the chat if you would like to learn more. You can also contact your account or customer success manager and set up some time. And, yes, as you can see, it's not a very difficult, solution to set up. You create your tone of voice. You have your bank of images already in Templafy, and you work with us to configure your template. It's as simple as that. And that's only gonna get smoother as we've heard already. So, essentially, get in touch. Document agents can be set up in a short amount of time, and you can essentially start to fill that bell curve that Oscar showed with bespoke documents given going from an intent to a document 40% of the way. So we've seen a lot today. I would suggest that, if you haven't already, go back and watch Templafy, talks document agents one zero one and, the use cases, which was episode two. I can't remember the name of episode two. And so now we've got a trilogy of document agent, webinars. So you'll be able to find those on our website. As I mentioned, if you want to learn more about document agents, get in touch using the link, from myself. This is probably gonna be the last Templafide Talks of the year, but keep your eyes peeled. There may be a bonus one at the November. We're still trying to work that out. But from myself, from Isabella behind the camera, Casper at home, and Barbara and Oscar, my guests, Thank you very much for tuning in to Templafide Talks, and we'll see you on the next one. Thank you. Thank you very much.