Hi, everybody. Welcome to our new webinar. We're very excited to tell you all about it because we've taken our Zendesk integration to the next level. We've kind of been bursting at the seams to show everybody what it can do. So whether you're a new user coming to learn all about Plego and our integration or you're an existing user, happy with Plego excited to use Beligo, I now wanna see the next level you can do with this integration. This webinar is for you. We'll try to cover both tracks so you all can gain something out of First, let's have a little introduction into Polygo itself before we go and explain what the Zendesk integration does, what the new features do for you. So what Polyga does, you can see on the screen, you all have the content, What's significant here is the authoring and instruction environment made easy. You literally get the gain of all the content reuse of a full management system of workflows and versioning without having any of the pain that's previously been in these type of systems to set them up. So you'll be able to simply write your topics and your informal topics and put them in a publication and send them out that the the user has a lot of white space. You don't see any code a friendly interface that even non technical writers, such as sales departments or or human resources department, can learn to use the authoring environment in Bellego. And lots of different types of reuse where we'll get to. The reuse will give you greater efficiency. Allowing you to reuse content, use it in different channels, different type of products, different types of documents. The collaboration workflow nowadays collaboration is a huge part of any internal workflow for the authoring, gathering, and review of content. We have that built in with assignments. If you kind of wanna pictureize, pictureize it just for now, kind of Google Docs type of environment, where you've got comments with bubbles. You can have people add editing and deleting. You've got a project planner. So you can see the status of what everybody's doing. So that full collaboration process where I'd say it was critical in today's environment, the publishing, you can publish a lot of different channels. So whether it's to Zendesk, as we're talking about today, or HTML five, PDF, scoring for learning management systems, even word files. You can publish to a whole range of different outputs all from the same content. And translation is also a critical part of your whole workflow for those involved. Palego integrates either directly with translation memory systems, or we export the XML format that they use happens to be called XLIF. This previously was a very expensive and problematic task for technical writing products. With us, it's essentially virtually immediate You can export immediately. You can import the content, and then you can publish to PDF, let's say, with language tabs. So multiple languages in the same PDF if that's what you want. HTML five with a language switcher into the Zendesk and Salesforce worlds, pushing into multi language into their to their their their support, their knowledge bases. It's a complete workflow and very efficiently done, and versioning. So unlike some systems, you maybe need to integrate with a git or something of this of a like, it's part of our core platform. You've got full revisions of every change. You can do parisons, and you've got branching, but branching for technical writers, not branching for coders. This is not the time to elaborate on that. Essentially, you can mirror inside Polygo, how your development team will manage your product. Let's have a very quick look at what Polygo can do for you. So first of all, if you're not using a content reuse product, you literally can get up to forty to nineteen percent. Depending on your product and your environment and and your audience, reusing content between those different places. As we said before, multi channel, that you can push the content into multiple places, all essentially, we're just clicking a couple of couple of buttons. You're gonna get a consistency and accuracy because when you're single sourcing, that consistent voice, that magical source of content, you can reuse again, not just in the Techcom's environment is maybe traditionally these products have been used. But in other departments, anywhere where there's reuse and accuracy needed, like in the human resource, legal department, marketing sales proposals, and we're in the and we're in the structured authoring environment. Which essentially means inherent consistency. Part of an industry standard. You're not with a proprietary format in Polygo industry standard. Your safe for the future, if you would ever want to make a change, we'd hope you wouldn't, but it's important for you to know that you can. And as we just discussed before, teamwork and collaboration, it's all integral part of our product. Now it's time to jump in to the Zendesk integration. They're now on an equal footing. We all understand what Plego is and the benefits. Let's talk about the Zendesk integration. And we'll first start explaining the basics of how it works before we move move to the new functionality. So the workflow could be something like you can see on the screen. You're going to possibly import your content from different formats with this word or another XML format or HTML, and also an import from Zendesk, which, by the way, I think without any doubt, is the best Zendesk import on the market. We import the content to the best that we can going from. Non structured Zendesk into structured Plego, and that can often be painless. And if you need help with air to help you, or you can write the content yourself, obviously. So we have now the content inside Polygo. We do all the magic we discussed on a couple of previous slides. We're we're authoring and we're managing it. And we've got our different reuse of the translations and conditional texts. We've set up our translation. So all the hard work we've done in Polygo to make our content ready. And then all you need to do is push a couple of buttons, and the content goes straight into Zendesk all done. Let's just have a quick discussion about how the magic happens. How we're mapping your content from Falego into Zendesk. And one of the great things we have a publication, which a publication is my collection of topics in the hierarchy. And it's a any publication, and you you push it into Zendesk, and Polygo does the magic to make sure it works inside the Zendesk categories sections and articles. Because here, you can see at the top, we have a section at the top, the styling, and then articles underneath. Then underneath a larger to larger rectangle is basically showing. This has got more nevilles. So Plegos automatically fitting it into an article. And then as you can see on the right hand side, you know, you've got your hierarchy with the menu on the left would be created by Zendesk. But if you've got a topic with multiple sections, it automatically shows for you. And now let's jump into pre flight. We've been through all the positives of Pulego. We've explained the Zendesk integration Now we're gonna explain how we're moving to the next level, moving you to the next level. Plegos had the integration for about four years. With the most mature integration from a documentation platform into Zendesk on the market. And now as preflight says, we're shooting it up to the heavens. We're taking you to another level. Preflight gives you unprecedented control of where you're going to put your content inside Zendesk. So we're starting essentially with an empty Zendesk help center or guide. Where there's a couple of categories. There's no content, and we're going to go and add content and later we're going to modify and update content. So now welcome to Piligo, for those of you who are seeing Piligo for the first time. Just very briefly on the left hand side is our content manager. That's where we're gonna men manage all our content. Our topics and our publications. So now we're taking our publication that's being created already with an existing hierarchy, and we're going to push it to Zendesk for the first time. So we're going to choose the HTML option and inside There's an option called Zendesk multi section, which will create our sections and articles. We'll automatically we're going to select the category that we want to push our content to What's happening in the background here is Plegas is actually looking right now at Zendesk and it's showing all the categories that exist in Zendesk. So you can choose where you exactly where you want to push which category you want to push the content to. So admin's smart home is where you want to push it. And now we're clicking on Zendesk preflight on watch what happens. And now welcome to Zendesk pre flight. You can see that Pligo is going to create forty seven resources inside Zendesk from the content from Pligo. That essentially means all the sections and articles in that category. And you can see for all of the articles, as well as individuals you can set if the status is published or draft, who's managed by, and who's who the articles are visible to. So you have that global as well you could do it for particular article you wanted to. And then when you've finished doing that, all you need to do is click publish document and now our content is being sent over to Zendesk. And let's have a look inside Zendesk itself. And you can see there's been populated with the content from Polygo. Let's have a look at one of the articles that we pushed in. For example, the about page, and there you can see. You've got text, you've got images, all come directly from Polygo and formatted according to the Zendesk team. Each time we're going to go to an extra level. So now we've got our content in there, normal process, is you've got to update content. So let's go and see how pre flight can allow you to update content So whether you add, remove, change, all those scenarios are covered with Zendesk pre flight from Polygo. We're going to the entertainment, which would actually be one of your sections. I'm actually renaming one of the articles. Now this is actually really quite significant because what you need to understand with polygon is a database happening behind the scenes. And the name that you can see on screen is just an indicator for us in order to help organize our content. But the underlying ID has not been changed. Meaning, the bottom line, it doesn't affect what pushes into into Zendesk. Again, you might see with with other products is very significant. One little name change can throw off the the the whole publishing process. This is not the case as we're going to show. And we're also gonna put some bullets on these. You see how quick and easy it is, by the way, and structured authoring in Balego. We're gonna add an image. So this is gonna be very different to the article that's currently in Zendesk. We changed the title, changed the the name inside Polygo. We've made it look different. And that also makes some more changes to the actual publication collection and hierarchy. So we're going into tainment, and we've we're gonna delete some content as you can see. We've actually deleted two articles. Note that for for a couple of minutes. We're also going to add some new content. So adding a new topic that's called stoves, and we're going to move it into the appropriate place inside household equipment in our in our hierarchy. So we've made some significant changes, which is probably quite similar as to what you will do in your environment because you're always going to be adding, deleting, and editing content. That's the way we work. So the integration has to be able to work with your environment quite comfortably and easily. For you to manage that content. So now we're gonna push that content over again. So we'll same as before multisection, and we're gonna select our category, same one as before, and over to pre flight. And now we're going to see some more magic, how we're going to do that, how we're going to specifically manage what goes where So you can see on the screen at the moment that we recognize there's forty five resources. That's forty five sections and articles together. Inside Zendesk we want to update, and we've created one new resource, which will create one new, article inside inside Zendesk. So if we go into our entertainment section, you will see there's two articles in Zendesk that we don't can't map to anymore because we re we removed those topics inside Polygo. So we're actually going to be able to remove them directly from Zendesk. As you can see, just by clicking the x to remove them. And you can see on the right there that we have two resources, essentially two articles in Zendesk we're going to remove. Now let's have and we're going to see we have our new article called stoves inside the household equipment that's being picked up. And you can see the change that we've made to the topic title, if you remember in Polygo, but supported smart speakers is what it's still called in Zendesk, we're still matching to that same article. But later when we publish, you'll see that the Plego change will be pushed into that article as So we're all ready now to go and publish our updated content over into our Zendesk category And now let's take a look. You can see our updated entertainment section, and you'll see the title has been changed just as smart speakers and audio according to the change that we made inside the legal. And you'll see the changes. Remember, the additional image, and we bulleted all that content. There's the updated content from Polygo into Zendesk, updated the exact same article that was meant to happen. Next, we're going to do something really clever. We're going to go into this article of smart TVs and there's a link there if you notice. To another topic, our smart speakers, and audio. And what we're going to do next is we're actually going to do selective publishing What selective publishing allows you to do is we don't have to publish the whole publication anymore. We can just push over to Zendesk what we need to, whether it's a sat a a section, maybe it's a single article, and anything that needs to done with the article will be done as part of the process. We're gonna see in a second even sending an article with a link to another article that we're not actually going update, it's still going to work. Let's take a look how we're gonna do that. So now let's go and publish that content. So you're now familiar HTML into the Zendesk multi section, selecting the category that keep you by the way, there's ways to remember this. We'll get to this late enough to do the same process each time, and Zendesk pre flight. And you can see now that the forty six resources need to update it. The first thing we did was to cancel everything being updated. We're gonna specify what we want to update. And when we selected this article we're going to update supported smart TVs, it also selected automatically the section in Zendesk where it needs to go to, and we'll publish that content. So we're just pushing that single article into Zendesk rather than the whole publication. And let's go into Zendesk, and we'll take a look. Look at supported smart TVs. That's the art the only article that we updated in Zendesk with this publish. And you'll see that at the end, that link at the bottom is actually working even though we didn't update both of the articles. The one, the source, and the one we are linked to, and there's the con them. Magic. Now let's take an additional example, additional scenario. Maybe somebody inside the support team, they made a pull of new, they made a new section called FAQ, and they put a couple of articles in there. But you're the technical writers want to have your consistent message across the whole company, the consistent way of writing. So what we want to do is to write that content inside Polygo and then map that content specifically over to the existing Zendesk articles. So here's our publication. And what we're going to do is create a new topic, which is go which are going to be our section title, which we're calling FAQ. That will be the section right now just at the consignment Beligo, and r two topics which are going to become the articles inside that Zendesk FAQ section. See how quick and easy it is to write to create the new topics directly from the publication inside Palico. And you can see the nesting of those topics inside the FAQ, what will be section in Zendesk. And now I'm sure you're very familiar with. We're going to publish our content, and we're gonna go and open Zendesk free flight after selecting the category. Everyone's an expert now. Here we are in Zendesk's free flight, and let's see what comes up. So you can see we have a new FAQ section with articles inside. Our next task is just to match that up with what we want to push into Zendesk and match them up. So the first thing we're doing is mat is matching the section level. So we're matching our new content from Polygo with the section inside Zendesk. Very easily done. And now just as an example, we're also going to match one of our new topics inside Plego with an existing topic, an existing article inside Zendesk, the other one we're going to leave What is a smart home will be matched into Zendesk? We're not going to publish everything at once like you've seen before. We can just push what we want to. And that FAQ article that was created automatically same levels as section, it's optional. We don't want it. So we just Turn it off, easily done. And we're also adding another article. And when you're ready, we publish One of the great things about Polygo is when you publish, you don't need to recreate from scratch. That scenario and story you want to tell for your published content in terms of your variables and the conditions where you want to output it to your categories and Zendesk. You can actually save them. It saves a lot of time. Makes you very, very efficient. So this page is where as you see you create your publication. And if you look down below, you've got profiling attributes. In other words, conditional text, you've got a certain product. We have a certain variable, and then could be many more of these with your architecture, how you create your content, and you raise your content in different places even with small changes. Rather than creating from scratch, you can go and save these settings. Give them a name so you can find them later. So later on, when you want to publish the next time you just go to publish. Go into save settings. We'll find that we created before. Click on that, and Zendesk pre flight appears. So you don't need to recreate even just the category you're selecting to. Very quickly, get into Zendesk preflight. So you then decide, as we've seen before, what you want to publish and what you don't want to publish. So you're seeing how you can create your tentant and Plego, credit save setting with any variables and profiling conditions and categories already. So just a couple of presses of a button, go into pre flight and publish your content over to Zendesk, quick, efficient, and effective. So we hope by now it's really clear to you why we're so excited about this new feature because not only do we have and have had. The leading Zendesk integration from a documentation tool in the market, and by far, there really is nothing that compares The whole workflow is gonna work great for you. It's gonna save lots of time. It's gonna be efficient. The reuse. You can match However, your company works with Zendesk content, whether the writers are creating it, support team are creating it, a mixture of both Pligo will mirror how you're working. So whether you're a new user to Plego, and you're contemplating how Polygo can help you, or with an existing user, just starting to use the Zendesk integration, or you've been using it for some time already. You're all gonna get such great benefits out of this new Plegos end integration. They're gonna make yourselves your stakeholders and your end customers really happy with the content that you've produced. I can't finish this part of the webinar without saying a few words about the new features that released and they're really exciting. Our customers have been asking us and requesting, can we automate the publication process from Polygo directly to your website, and we've given you four different ways to do that. You can use the regular FTP. You can push to Amazon Web Services s three or via Bitbucket or GitHub. So essentially put the Polygo content into your development pipeline so you can synchronize an auto make that process. So again, like with the Zendesk integration, just press the publish button, and it goes directly to your website. You're gonna save a lot of time with that feature. And if you want more details, please go to the what's new page in help.