10 Performance & Impact Features
Do you have a remit of:
Recruitment
Marketing
Outreach
Events or anything else closely linked to these?
Do you have a colleague who doesn't currently use the CRM that does work in these areas?
If the answer to any of these were yes, maybe, sort of or anything else other than "no", then this Webinar is for all of you! Download the slides here http://dhdocs.com/D1RI
Transcript:
Andy Speed: Yeah. So often everyone, um, suffering, we're going to be talking through 10 performance and impact features within student CRM within the system, uh, areas that either aren't being utilized by all or many, um, and things that just will help us understand the system and use things in a different way. Let's say hopefully, um, what I would say is that for the majority of the people on this call, the majority of things we're going to talk about already included in the packages.
That you have some of the features maybe in apps that you don't have. Um, but you can obviously pick and choose which ones you're going to, to utilize, move forwards. And we can talk about those afterwards with those that wish.
We're in the session, the four sort of main steps of the, uh, the session agenda for today. One define what we mean by sort of performance, impact and dates hooks. The second part is looking at the 10 features, hopefully deal that deal with that in 10 ish minutes, hopefully to allow plenty of time for questions and discussion at the end.
I'm very aware. I don't necessarily like to follow my timings very well, so it may be slightly more than 10 minutes. Um, and then at the end quick discussion and questions and next steps from there, sorry, performance impacts and data folks. First of all, to address data hooks, data hooks is an official term that's out there.
I don't necessarily mean it in the official term of data hooks. I'm referencing. The idea of, um, a nice bit of imagery, let's say where we're identifying. Items of information, data, knowledge, et cetera, that we might want to keep poking out a little bit, that we can utilize further down the line for other purposes, to identify or to analyze or judge or, or however you want to terminate it.
Terminology sort of use for that. That's basically why I'm determining bikes or data hooks. All of the features that I'm going to talk through are all ways of creating those books, creating these points of additional data and implement. So within that, essentially, to understand what high-performance or higher levels of impacts are, we need to understand what we're trying to achieve, uh, from, from what, from our activities and our things that we're doing.
The same can be said from this webinar. So to utilize the tools and the tips on talking about, you're going to need to know what you're trying to achieve as a result of that, and that hopefully we make more sense as we've moved around. The survivorship bias plays a part in this, for those that don't know what that is, and don't recognize the image of the plane that's on there.
There was a study that was undertaken during world war two. Um, basically BOMA planes that were returning, um, from there, from their runs and they misunderstood, um, that the, that the weaknesses in the planes that were returning were where the bullet holes were, where the red dots were. And in fact, actually the problem was I didn't recognize that the planes that weren't returning were probably showing areas of, uh, of weakness in the air is different to this one.
And they had assumed that because they survived, that they could understand where the findings were for. Where does that play in terms of this and what I'm talking about? Uh, essentially, what are we measuring? Why aren't we measuring it? What aren't we using, et cetera. And what don't we know, um, uh, my, I guess, point with this and the things that we're going to talk about is.
Why wouldn't you want to do some of the things I'm talking about as we move, move throughout the, the features in a little while, um, in order to have a better, deeper understanding of, of all of our activities and the successes and those types of things. Um, and ultimately if you don't understand where you're going and what you're trying to get to, um, and you don't really know what solutions you don't know what the primary scope of the, of the role is or what you're trying to achieve.
My bigger question. Why wouldn't you do that? Why wouldn't you create these various data hooks that I'm talking about with you, um, for use in the future when, when you have weather out or when you decide you want this, actually you could start building a sort of base of information and knowledge to be used in the future.
Hopefully that will make sense. And hopefully that wasn't too much of a, of a gardener thrown in my own presentation. So onto now, our 10 in 10. Now the first one of these, uh, is probably, uh, it's a little bit of a cheat. And then the first five all relate to this one particular, uh, aspect. But each of them I believe are worth sort of talking about an individual basis.
So I'm going to, if an activity reports in, I would say when I've looked across the. Most providers aren't using this and, or aren't using it consistently, um, for their own success. This for me is the, the sort of the gold element of, of sort of building these data hooks. You're applying multiple. Tags to your data that you create, um, through each of these five things that are on screen there, between the teens, your users, your activities, and your organizations you're involved yourself with and the outcomes, um, to understand basically the value that's coming from these.
And it's as simple as when you clone an event from one of the event apps, because it's available in event matters. Michael have been capture prep can open days, applicant open days, and it's even available when you do a data upload into one of those, those occurrences as well. Um, that you're creating these, these sort of data points.
So when we're talking about understanding sort of group value. So again, when we talk through the, the activity types and using teams, that will make more sense, but it could be around on Samuel sort of staff and team effectiveness. And it could also be around understanding sort of your return on investment from, from the types of activities that you're undertaking.
So activity types is the second feature that we're talking about, that links back to the event activity report. Ultimately, this is a way of comprehensively sort of identifying any activity that leads to students, joining your, your providers, be it recruitment bit, nurturing, bit conversion, whatever types of terminology you want to apply to that.
Um, it's a way of recognizing that your outreach accidents, uh, your international teams work, whatever it is, there's a way of capturing it within. It's as simple as a, as a free text, you create a line, you give it a number and you give it an activity name. You create a bit of a description to provide some sort of continuity and transparency across your teams, across your departments across time so that everyone knows what it was being recorded against that activity at that period of time.
Um, and you can go on infinitum and create these down as many times as you like. What is it? It's essentially, it's just a way of identifying these activities that you're doing. It's found within the student database, um, settings cold. Um, and why. For me, it's all about that continuity element. It's about, uh, providing the opportunity to collect information against these, for example, in this one here.
[00:07:07] So you'd know how many webinars, what success level look like from that webinars, how many leads we were capturing from those webinars? Um, it's, it's a way of having a deeper understanding of what it is that we're doing and judging some value off the back of that and providing that sort of continuity and consistency as well.
On top of that number three, our users and teams. So it's the second part of the event activity reports in. Again, continuity is a big part of this. For me, it comes down to, uh, understanding which people belong to, which teams that link to which activities. And we start to build a bigger, deeper picture within the CRM, uh, as to what's contributing to our success, it could be looking at performance management or monitoring.
Teams groups or teams, groups of people. However you want to sort of utilize those, understanding the sort of the group value again. So again, if you have a team that specifically international or outreach focused, or our schools and colleges and partners or whatever else you want to break those down to, it's a way of judging success, performance impact against those.
But you have to be able to create these first and again, most people. Using this function very often at all. Um, again, it's creating sort of large levels of data against these these groups. Um, and you can also partner it with an automation. Should you wish to, to be able to automatically, um, allocate teams, user sorry, or teams, uh, against.
People which we can, which you can see within the student record as well. And so that's, that's another function and that again, available, um, within, uh, the shin database, sorry, under users. Sorry. Um, and then the assessments there set the users up within there. So they're using the teams come from there.
Just a little aside here, before we move forward, I'm gonna reference this a bit. So I just wanted to introduce this here. In our it's actually quite useful. I would say most people aren't using these in, in any real, uh, real sort of passion let's say. Um, but they're available in most apps, right? Varying degrees of, of usability or, or sort of value.
And a lot of them link back to things that are coming up within these 10 that we're going to be talking about. And as you can see that as there's a handful on there. So between users assigned teams assigned personas and stages, all of those are things that we're going to talk about in the next sort of six or so features.
Speaking of associations, probably my favorite one in our, in our list of, uh, of 10 for today. Um, the ability to understand and link people, organizations, and events together. In such a simple and slick way from the, from that event activity reporting point, um, linking student database thinking, contact manager and all of your event apps in one fell swoop, just the ability to be able to record.
Beyond just what the event is. So an example of what that would look like on this example here, we've got our, our student, our example, student Johnny Cash, um, within the student record card yourself, uh, that you'll see this yourself and tab eight along the bottom is associations. I would say most, most people don't have.
Any, anything in these, when you look at your student records, um, and they would, they will appear in here automatically when you create the, the association with the event that you create, and then, then import those students for whatever reason. And the example that we've got here, our pink column was actually manually entered, um, which is done from within the student record card itself from within the student.
And, and that association is given the blue one was automatically allocated when they send it a specific. Here's what it looks like in the logs as well. So we can see exactly where they came from. Again, the blue, you can see that happened from, uh, from taking part in an event, uh, and the pink one was added by a specific, uh, organized, uh, specific person, myself, uh, who added this to this, this organization.
So we could see what I looked like. From within contact manager itself, uh, it starts to look like this. So again, when we looking in concept manager and we look under our organizations, they have the same tab of association. And within that, we'll show you the full list of the students that are associated with that organization.
Now for big organizations, something like a, you cath, where you could have thousands of students associated. Top, press that tab. If you've got a lot of time to wait, sometimes it can be a wall to put a lives through an easier way of saying how many students are associates with that is to help her over the little green, um, Person icon in the top right-hand corner and it will show you how many students are associated with that organization.
And again, this one here, so fake kg, consultancy others for notices you Casper. I'm not going to call it that on a demo at so Fe kg consultants. Both of those organizations, vacate G consultancy and fake academy both exist in different occurrences. So fake academy in this example existed in our schools and colleges, and then our fate kg consultancy existed in our business contacts.
So we're able to separate the two different types of organizations. Two different associations within those. Um, and still at the same time within the student themselves, see it in one place. We can see the different ways that they're interacting with the different parts of our organization, our partners, et cetera, and understanding that full value.
On the back of that. Another one of our in-app reports, which is really, really useful to know, and to see, and to understand is this one here, which is the in-app report for associations by organizations, where you can view and see a simple count based on the timeframe that you associated the top. So that ones for all time within this test, Set up the, I had to see which organizations we have in there and how many associations they've got.
So where they're coming from in reality, what this means to you in real life is that those associations will be coming when a lead is generated from that organization. So when I'm at a school and they fill out my MEC form and that, that, that name comes and hits. Uh, hits the student database and it comes in on the same cable automatically, or the end of the event, that association is created as a, as a result of that.
And that goes on their record. Then that student, we meet them again, uh, a UCAS event. Then we meet them at an open day. Again, all of those things can start to build up within there. So it's given us a real, real idea of where that partnership. The next one from that is, uh, is around event outcomes. So this is the last part of, uh, the event activity reporting.
And it's the area we come back to post event. It's our understanding of how successful that event was. And basically trying to put some level of tangibility, uh, against that. Now you could use the simple. Attrition of how many leads did we capture? How many people did we find? Which of course you'll get from, from your data important.
You'll understand it from that perspective, but are there other things that are valuable to us as an organization beyond just how many leads did we capture? Is it about how many people we actually going front? Or if it's outreach, how many students did we see while we're there? Is it about how many parents we saw or is it about how many perspectives as we gave out?
Whatever those other sort of intangible elements normally would have. Can we record it here in some capacity. So you would set it up again, based on each occurrence of, uh, of each of your event apps, you would have the option to create a different set of outcomes available to you. And again, you just build these out as many as you like, as long as you've got some logic to it that makes sense to you and you use the description to help other people understand that.
For example, this one that I've got in front of us here, where I've selected five, very good. That's on the basis that actually there was more than 200 people at that event. And I've said that that was really good. That was, that was a very good event from this capacity. So it's just as long as you understand how that works for you for that occurrence for that app, et cetera.
That's where that, that value really comes into. So that's the event outcomes. Um, In terms of outside of, uh, event activity reports in, so the last, the second half of this basically are all outside of that. So you're responsible for is a really interesting one, um, in my opinion. So, uh, it's the little tab just below Jimmy nails.
Nine, that is a little down, and it's basically the chance to allocate a user from the system, a member of your staff, to be responsible for an individual. And there could be many reasons why you might want to do this. It could be that that individual falls within a specific outreach category or. Uh, there's a specific recruitment target and that student for whatever reason meets within that, because they, uh, they're part of a key focus for you in terms of courses or they're an alumni or whatever it is.
There could be a reason to specifically identify them and essentially account manage. Account management them through sort of the recruitment process. This could be a way of, of sort of allocating that and then measuring what that does. Um, you could allocate them based on postcode or allocate them based on region or whatever it is that you want.
There's ways of, of identifying this. Um, and ultimately it's something that you can do if you wanted to. That have too, but it's, it's a function that's I would say is currently not utilized as much. Um, and the big part for me with this one comes down to sort of performance management and sort of monitoring.
So if there are multiple people doing the same function, Is there a distinct difference in the success rate from individuals within the same team. And is there learnings to come from individuals that are ultimately doing the same function as someone every year massively outperforming in terms of enrolling more students at the end of the process?
And if so, what are they doing? Are they doing anything different? Is it purely luck? What is that? And without having this attributed, you don't have the ability to really do that beyond that, unless you're obviously saving this information somewhere else separately. Um, the other key parts of this is the ability to partner with an automation again.
So the ability to automatically allocate individuals to be responsible for someone, if they meet certain criteria. Okay. So for that, I keep referencing automation. So those that don't know what what's motions are. It's a separate app, uh, that allows for, um, basically. Non linear integrations between applications.
So functionality that ultimately is within a specific application. It allows it to interact with another application in another way that it wouldn't do without the automations app. If anyone wants to understand more about that, can we can talk about it often. Number seven is personas. Uh, probably one of the features that you use the most, but the most differently across the system.
And the most probably inconsistently, um, I saw this on LinkedIn. Couldn't help myself, but bring it into this session. The phones aren't about demographics. And I think that a lot of the time is because they, everyone has something shared, actually a persona is about more the differences, less so than the shed.
So in this case, all of the shared actions are the shared sort of demographic elements to this. So in prince Charles and OZO, Could paint them as the same individual. If we took the picture away and just had the description by our ultimately the same person, it'd be hard to argue that they weren't, if you didn't know who they were, um, on the right-hand side, you can see the difference in the way that the system can look at this and the way that you could use personas.
So we can see prince Charles is a money bail in orange, and also he was born is black and he's a balmy back. And essentially it's a way of, um, allocating. The attributions to individuals based on either how they self-define or based on the actions that you see them do or perform, um, either through one of your, sort of your web forms or rapid survey, something like that, um, or, or partner with an automation.
So when they do something specific that you allocate them to a certain persona, And it's about the ability in the future to be able to personalize content to them. The other thing which is probably the most seen with personal persona, sorry, is the fact that personas are time limited. So a student can move between personas throughout their journey with us.
It isn't fixed in time. So you will see students changing episodes as they move through the process. Depending on how many opportunities you give them. So I, so identify as a persona that will happen at the screenshot. And you can see that is essentially it's a, it's a short one. It looks like a salad within student database.
Again, under the settings called new, create them by creating the name, allocate color code. Actually create some kind of a ballot to explain what they are and what it's doing. And that falls within that. The other, the other aspect I'd say within this as well, is that if you aren't going to use this and wanting to track personas over time, it's always good to partner it with an automation, to be able to potentially tag the student with the persona that they have at that time, so that if they change the cider in the future, and you wanted to understand previous personas, you could, you could understand that through an automated.
Hopefully that that makes sense. We can talk about them more in questions that are offending or might come up. Uh, this is the, my second favorite one in the list this afternoon. So around stages, uh, again, one that's, uh, inconsistently used and I'll show you on the next grade, the next couple of screens, couple of different ways that this is, this is being done.
Essentially it's about defining and identifying what your funnel. Um, I would say most people in the system are focusing purely on understanding the stages or the state. Uh, of applications, but not necessarily understanding the stages or the positions students sat pre-application. So that whole big sort of chunk between lead gen and an application, this is potentially a way of doing that.
It creates a real high level of flexibility as well, because you have complete control over what these look like. Um, and you can, you can determine what these stages. Look like and work. And so it fits your system that you want it to not necessarily, not necessarily just as the standard sort of UCAS idea, it could be leading up to the Yukon one and then mimic the UCAS one answer was, or however you want it to basically, as you can see on screen here, this is another really nice feature of the in-app reports.
Is that it shows us our stages really nicely. So if you want it to understand how many students were relevant of how they applied, whether it a direct African a post-grads, if it was an undergrad, if it was in central student, whatever else, um, obviously all of their status is, uh, application stage. I'll one thing.
But when the, in the, in the buildups that, what does our pipeline look like? Where are people sitting? How long are they sitting there for? What does that, what does that whole thing look like before they apply? Ultimately the time where there's the highest level of attrition normally is that you're losing people between lead gen and application.
So what's going on in that period of time. And, and what can we do to basically stop that or to limit that or to, to reduce that. And this is a nice way of doing that. And again, that flexibility of doing it, however you want to work really well. And again, you can partner it with an automation to automatically move or, or to recognize when students are at specific stages, depending on, on how you build things out.
This is an example of, of a couple of different ways that this is, uh, this is potentially being used in the system. So these are two different test environments we've got. Um, and I thought let's just show both versions of these. Um, so we've got, uh, on the, on the left-hand side, you've got a real, uh, Follow the less structured let's save them the one on the right.
And that's more of a gut feeling on the left. So are they just calling on us? Are they, are they, are they hot? Are they, are they really interacted with us? And then have they applied or enrollment? It's a really basic one on the right. We're talking about a far more sort of micromanaged processor that the sort of understanding of it, but you can see how potentially the two different processes work.
On nine is our engagement scoring. So engagement scoring again, south lynching database out in the. The Coke within that. It's essentially a way of, um, recognizing interactions that you're having with your, with your leads or with your applicants and allowing the engagement score, which you can see a quick snapshot of in the top, right.
And corner where that sits in the student record card. To understand how engaged those students are with you and with your processes. Now we know that there are a couple of, uh, complications as a result of, uh, essentially bots inside email, um, providers, a couple of specific email providers, and that can skew a couple of the scoring functions related to sort of email opens.
It's an ongoing thing that we're working, but they, they, they develop issues, uh, for us as we fight the fires, uh, we are working on this. But the point that I sort of refer to on this, uh, it always comes back down to what I think I mentioned at the start around focusing on outcomes, if we're focused on our outcomes and the actions that we want, our, our students, our leads, our applicants to be doing, as opposed to necessarily what they've read it.
So the actions that we get into attend something, book onto something, speak to someone, for example, those things aren't skewed by email stats. Those things are all fixed in stone, late they happen. Um, and there's a way of recognizing that. So you could minimize the implications of the emails. But just not monitoring email, email opens, for example, and that can come up within this.
The good thing about email, so it will be guidance store and sorry is they could be pre-planned so you can program this whole sort of page of grids and give their scores and all these things to it, or it can be ad hoc. And I say that on the basis, they could be partnered with an automation. Um, and you could allocate some level of, uh, of engagement score based on that, which I'll show you on the next slide.
And it's about being outcome focused success. So if we focus on the outcomes and the things that we want our students to be doing, you're more likely to sort of see value in this section itself. This is an example of what an automation looks like. That involves engagement score. I've broken this down.
It's normally a one straight string by brokenness. It's easy to view. Um, so in this example, we're looking for a student that inquires with us. They come in by our, the inquiry. Um, and we're looking within the message content within the message content. We're looking for the value Easter egg, 2022, and as a result of their comment, including Easter of 2022, we're going to give them an engagement score of a hundred.
Now that's a stupid example. Um, however, it has its value when we put it in the context. If I'm giving a presentation, a large store fair or something like that, or an assembly or wherever it is, or on a piece of marketing material and a bit like a voucher Dakota, March madness, 20, 22 or whatever it is for one of our shops that we have.
And the rules, if they quote that back to us, does that mean they're more highly engaged than someone that doesn't quote that back to. Maybe, maybe not. Um, there's a lot of different ways of, uh, of tweaking or recognizing that engagement score change. And that's an example of one of those times that I quite like.
Speaking of automations, we're going into our 10th one now. So 10 hair, there's two examples on the screen. Essentially automations are used to increase team capacity. If you're looking to automate things and to take away some of the manual processes to use some of the functionality that I was talking about before or, or whatever else, the automation is a really neat and nice way of doing that.
Um, it allows, uh, Applications to interacting non-ordinary ways, as I mentioned before. So as we can see in this example, we, the first one we're looking at inquiry. So we're looking at when a web phone creates inquiry. Someone creates an inquiry with us, um, and the message content includes. And you can't say that.
For example complaint, terrible Paul rubbish. So if it includes any of those, we're going to adjust our engagement score and we're going to reduce it by 99. We're going to say that if they've, if they've taken their time to contact us and use any of those words, it's likely that that's negative and therefore we're going to reduce their engagement score.
And what we're going to do then is we're going to replace their priority, fill with the little staff due to the inquiries. And we're going to turn that into a yes. So it's going to say. And then what we've got on the right here is a secondary automation from that. And that's, if an inquiry form has a priority of yes, that is going to trigger an automated notifications, a specific member of staff to go and deal with that.
So in this instance, if that gets tagged, sorry, if that gets prioritized. An email is going to be sent to team leader, uni.com. And that member of staff is going to have a direct email land in their inbox to say, this student has been made a priority, go and have a look at them, go and find out what's going on with them.
Same can be said. For example, if someone's using the data compliance one, for example, it could be. There's all sorts of different ways. It could be around status changes. It could be around, um, withdrawal rules or whatever else is ways of, of using this to your, your sort of benefit. So, yeah, automation is a great way of increasing capacity and again, it's a, it's a function.
And a feature that I would say is, is vastly under utilized. And then I know us at 10 in 10, and I've gone over my 10 minutes and now I'm going to go over my 10. And I'm going to throw in one more, which states tax, which ultimately, uh, on the, on the screen here on the right, we've got, uh, This is just an example on the power BI I have on the system from an American university, the types of things that you can build out with your, with your.
That information from the data packs, uh, it could be through Tableau or another, another platform, whatever your institution is using. And it's a way of really deep diving into that data. I've mentioned in our reports. They are specifically very lightweight. They're not designed to be, uh, to be able to deep dive into things.
The system isn't designed to be. Allow that to look across those apps, uh, within the system, uh, taking it out into device, back to looking at it on a proper business analyst sort of platform is the best way of doing that. Looking at how your success works in the future, looking at where your trends analysis comes from.
Again, the data is a great way of taking that out on that that covers all that. The sort of the data we've spoken about today as well. Uh, understanding specifically the, the sort of the value and the impact of your maybe your outreach activity or international activity, schools, colleges, partnerships, et cetera.
That's where it comes from. Understanding your selling investment all from this. And the real key to this one, the reason why the data packs and the BI platforms are more useful and better than having it just as in the system, you have the ability to bring in other data from external, you can bring in stuff from, uh, from your student record system and look at the, the journey that they take from inquiry through to, uh, I don't know, to graduation or beyond sort of graduate destinations, those sorts of things.
So it's not just the recruitment process. You can look at the, sort of the whole life journey. Okay. That's my 10 in 10, just a quick recap of the sections that we've covered across there for you on screen. And I'll ask if people can start to get their questions together. I'm going to take a moment to just not speak for a second.
I'm going to open up the chat window so I can see what's there. And step, fuck asking you to come back on for me and let me know if there's any ones that you specifically think I should be speaking. Oh, I'm here. Um, no, we haven't had any questions yet, but let's see if anybody has got anything that they'd like to ask about.
Yeah. If anyone has questions, feel free to turn your Mike Mike and-or camera on. We're not recording cameras, so you're not going to be on screen. Um, one of the questions I've got actually is, um, Throughout the system. Lot of what you're talking about here is, is actually across apps. So, so is that one of the primary benefits really are things like, for instance, um, the event activity reporting panel is that you can categorize things across the different apps.
Yeah, I think so. So it's the, I guess. The benefit of having it across apps is that you have that it's not just happening in isolation. So it's not just recording what you're doing in mobile event capture and only mobile event capture allows for that comparison across similar apps. So everything that relates to activity your, are you there that for your events that you're doing, it will record that against those, but you also have the ability.
Within this stuff is, but you can change for example, your outcomes. If you want to have different outcomes for different occurrences, you can have that difference at the same time as being similar. Um, as long as your activity list is comprehensive, you don't necessarily need to use all of those activities in all of the apps within all of the occurrences.
As long as the activity list itself is comprehensive and it provides that sort of single point of, uh, of reference then, then yeah, it works great. Yeah. So an example might be for instance, um, like, uh, you might be running a specific kind of, um, event with a particular channel, like an online event, um, using a particular, um, third party for instance, but you might have a big event like in PhD, in pre applicant, open days, and then a much smaller targeted event at, um, various, uh, a very specific student demographic.
But using event manager, but if you had the same, um, activity type across the two apps and you record that accurately, then you'll be able to see how that particular channel is performing for you both in the bigger open day, online, open day, and about specific student event. It's the sort of thing where my head immediately with the situation you just presented that stuff, but actually your activity type might well.
For example, a presentation and, and your recording. Cause they're all presentations in different capacities. And then actually your, the association is where the success part comes from there because actually you could record, uh, you could set up your platform, you could set up, I don't know. My webinar or go to me or whatever it is as your business contacts and then associated from there.
So you can actually record your activity type and your, your platforms, a separate thing. You can obviously do that within the location part as well above which comes into that as well, because all of that context is usable in line with this when it comes out in the data packs. Um, it's just a question for me.
It just. It gives options. And that flexibility, that ability to, to get a bit creative with how you want to record something or how you'd want to, to, to understand things at a deeper level comes from doing that. And the nice thing is the clone ability. So once you clone it and a lot of that hard coding part bottom just needs tweaking.
You just need to adjust who the association is, go and see, but actually the person that's doing the event or the team that's doing the event is already there. So you don't even necessarily need to rebuild it every time you just need to tweak it. You. Yeah. Okay. That makes more sense. So does anybody have any questions then?
Always happy. That's not a problem. What I would say is, um, next steps from this, in that case, um, there's, there's two things that you can do or three things you can do. One is you can say that was, that was lovely. But it's not for me or it's not going to work or whatever else, and that's absolutely fine.
Or go and have a little play with that yourselves and just, just do what you want to do. The second option is that you have a chat with staff or a team about how you might use some of these functions and features, or the third option is, is to book, to have a meet with me and have a chat about things, uh, as your account manager.
And especially if there's a function there, if you're looking at automation, for example, um, or if you don't have access to contact manager or whatever, As, as a possibility of sort of taking that element and seeing how that works. So if there's no other questions, I'll ask you to wrap the, uh, wrap the recording upstairs.
Yeah. Cool. Okay. Yep. That seems to be it. So I'll just stop the recording now.
