0:24 [Music] [Applause]
0:25 [Applause] [Music]
0:36 hello everyone thank you for joining
0:38 today's webinar next think Infinity
0:41 solving it's nightmare scenario it's a
0:43 pleasure to see so many of you joining
0:45 today welcome
0:47 um to begin I'd like to say
0:48 um I'm Andy philp I'm part of the
0:50 product marketing team here at next Inc
0:54 and I'm also juggling by uh Doug hi Doug
0:57 hey Andy good to see you
1:00 so in this session what we want to cover
1:02 is really around the founding principles
1:04 of nexting which is really around this
1:06 core principle but the most important challenge
1:08 challenge
1:10 um the most important customer of it of
1:12 course is the employee but every
1:13 organization we speak to has the same
1:15 challenge which is in order to deliver
1:18 that optimal digital workplace IIT needs
1:21 a truly complete understanding of the
1:22 digital experience that's delivered to
1:26 every single employee so
1:29 next thing we understand that existing
1:30 tools don't give I.T the visibility
1:33 that's needed although these tools are
1:34 important they typically focus on
1:36 understanding the performance and the
1:39 availability of only a small component
1:40 of what makes up the complete digital
1:43 experience for any given user for any
1:45 given time and of course this changes
1:47 based on the context of the way in which
1:49 someone is working
1:51 and this ever increasing complexity of
1:52 the tools that are used to deliver
1:54 digital workplace Technologies is
1:58 leaving it teams blind to the number of
1:59 increasing issues that adversely
2:02 affecting employees when all of these
2:03 things come together
2:05 client management tools are great at
2:07 delivering applications and patches but
2:09 they don't really understand how
2:11 employees are trying to access Business
2:14 Services infrastructure monitoring tools
2:17 they focus on infrastructure inwards and
2:19 servers and typically the performance
2:21 and the availability but they can't tell
2:23 if an employee is sitting at home or in
2:25 the Office unable to connect to a
2:27 service because of a setting that's
2:29 wrong on their device
2:31 web hosted applications for example
2:33 application Performance Management tools
2:35 are great at going inside the
2:37 composition of the application inside
2:39 the code but they have no real concept
2:40 of how this is being delivered to users
2:43 in their browser on the device is it
2:45 working is it performant does it solve
2:48 the problem and the reality is that the
2:49 boundaries between all of these tools
2:52 are opaque they're walled Gardens and
2:54 even if the data is combined they still
2:56 lack the perspective that really matters
2:58 which is what the employee is actually facing
3:00 facing
3:01 and with employees and not necessarily
3:04 using corporate networks anymore and
3:08 increasingly applications devices and
3:10 infrastructure are moving to the cloud
3:13 visibility is reducing and the efficacy
3:15 and the relevancy of those traditional
3:18 tools is being diminished and ultimately
3:20 this leads to issues being passed
3:21 between teams
3:24 misdiagnosed and unresolved issues are
3:26 on on the up disenfranchise users
3:29 dissatisfied users overloaded service
3:32 desks and it's in the middle of it all
3:34 and it's compounding and it's getting
3:36 worse and this is this nightmare
3:37 scenario that we're seeing for it which
3:39 is how to get out from under all of this
3:46 so this is what we've always been trying
3:48 to solve here at next think since day
3:50 one is to provide it teams with that
3:52 single pane of glass that helps them
3:54 understand all of the time what
3:56 employers are using what they need what
3:58 instance they're facing and whether they
4:00 report them or not and this needs to be
4:02 understood for all employees all
4:04 Computing environments all applications
4:07 all networks and set in the context of
4:10 how these relate to digital experience
4:12 and the reality is if there's not a
4:14 complete and truly related visibility
4:17 related being a key word here and the
4:19 change is done and it's not done very
4:21 well any transformation project is
4:23 potentially at risk
4:24 and this is key to getting around this
4:26 is to drive a successful digital
4:29 workplace and it's not possible we think
4:31 without a solution that can decipher
4:33 digital experience of all employees all
4:37 the time across everything
4:39 so really at its heart next thing
4:41 Infinity souls for three underlying
4:43 challenges to mitigate that nightmare
4:44 scenario that I talked about
4:46 firstly seeing digital employee
4:48 experience issues as they begin to
4:50 affect employees but before they become
4:53 I.T problems across all of those silos
4:55 that I was talking about
4:57 diagnosing the context scope and impact
4:58 of issues
5:01 to accelerate issue ownership and
5:03 troubleshooting and then finally we're
5:06 appropriate to fix them and fix anything
5:08 very quickly minimizing the disruption
5:14 so taking a quick look about how
5:17 Infinity works at a very high level data
5:19 inputs are collected continuously from
5:20 devices with an ultralight weight
5:23 collector and we have connectors that
5:26 collect to relevant third party systems
5:28 bringing Telemetry in continuously and
5:31 in real time and whilst that happens we
5:33 are constantly looking to see all the
5:35 devices all of the apps all of the
5:37 connections in real time discovering
5:39 issues as they emerge and begin to
5:41 affect employees
5:43 with issues we identify the context the
5:46 scope and the impact of the issues to
5:47 accelerate troubleshooting and issue
5:50 ownership and we automate everything and
5:52 fix anything with very powerful
5:54 remediations that deliver fixes in
5:57 seconds at scale instantly automatically
6:00 behind the scenes or very powerfully
6:02 when the user decides
6:04 while this is happening data exports
6:06 bring next things intelligence to
6:08 external systems that need it to provide
6:11 the context that matters into systems
6:12 that don't have it
6:13 and while all of this has happened
6:16 Infinity is continuously analyzing
6:17 everything spotting patterns
6:21 benchmarking enabling the strategy to
6:23 inform the wider deck strategy and to
6:25 make sure transformation projects are successful
6:26 successful
6:28 so Infinities really designed to close
6:30 the loop on continuous digital employee
6:33 experience management enabling it to
6:35 focus on seeing diagnosing and fixing
6:38 the most impactful issues that employees
6:40 are facing
6:43 so we're really Keen to show off some of
6:44 the great capabilities that we have in
6:46 infinity and to do that we're going to
6:48 pass over to Doug he's going to run
6:50 through a live demonstration of how all
6:53 this comes together I hope to you Doug
6:55 appreciate that Andy thank you for
6:58 setting the stage so well for us
7:00 um so what we're going to look at today
7:03 is just one of the many different ways
7:05 that the next think platform the
7:07 infinity platform can help uh
7:11 organizations to uh to see diagnose and
7:13 fix problems
7:16 um as you outlined a few minutes ago
7:18 organizations really struggle at times
7:20 to resolve problems that are most
7:22 meaningful to the business
7:26 teams try and prioritize based on user
7:29 impact but they're often inundated with
7:31 service desk tickets
7:34 lacking the context at times to truly
7:36 understand the problems that are coming
7:39 across their kind of inbound queue and
7:40 that can cause a vicious cycle right as
7:43 i-team teams fall behind sometimes
7:47 employee frustration grows and that
7:49 leads to fewer problems getting reported
7:53 which gives the uh it team less
7:56 information about what's going on
7:58 only next thing can intelligently notify
8:01 it teams of the problems that employees
8:04 are facing across every workspace every connection
8:05 connection
8:07 in every application long before any
8:10 tickets are raised closing the loop by
8:11 offering resolutions that can be
8:14 automated or offered to employees
8:17 so imagine for now that I work at uh the
8:19 service desk
8:21 and although I've been in firefight mode
8:24 since I started my my company recently
8:26 invested in next thing to give me the
8:28 tools that I need to get the visibility
8:31 to get ahead of that Blaze
8:33 so I'm going to start my day today with
8:36 an alert and that might be an alert that
8:38 came across as an email from the next
8:40 think platform
8:42 or next thing may have initiated an
8:46 incident by way of a web hook based on
8:48 thresholds that we've set up or maybe I
8:51 start my day by reviewing the alerts
8:53 page so that I can get a sense of where
8:56 trouble is brewing across the organization
8:57 organization
9:01 so taking a look here I can see that in
9:04 the last 48 hours uh there have been a
9:07 significant spike in alerts that have
9:09 appeared on the on the dashboard here
9:12 telling me that we've got some issue
9:14 that's starting to catch hold something
9:17 that's blowing up and as I look over the
9:19 top of the list here I can see things
9:22 like an application here crowdstrike
9:24 which I know is critical to our security
9:28 perspective uh has been causing problems
9:30 or has been crashing repeatedly just
9:31 within the last hour or so across a
9:33 number of workstations
9:36 now I can take that information and I
9:39 can start to drill down into it by
9:40 looking at the one of the workstations
9:44 where one of these problems was reported
9:47 on the workstation view I'm going to see
9:49 some of the inventory data that next
9:51 thing has collected for this workstation
9:54 right I don't have to go out and call or
9:56 interrogate the user to understand
9:59 things like the model the OS that's been
10:02 deployed the resources that are present
10:04 on that workstation
10:07 you can see what user's been affected
10:09 but I've also got a very unique view of
10:12 what's happening on that workstation by
10:14 looking at next things timeline view
10:17 device view is taking all of the
10:20 Telemetry hundreds and hundreds of data
10:22 points that we're getting in real time
10:24 from those endpoints
10:27 and correlating them putting them on a
10:30 timeline so that you can easily see how
10:33 the different events the different data
10:34 points that we're collecting fit
10:37 together to give you a more complete
10:38 picture of what's happening on that workstation
10:40 workstation
10:42 some of the information here if I'm new
10:45 to next think I might need some guidance
10:46 uh in which case I've always got
10:49 documentation close at hand if I want to
10:51 just get a quick refresher about what
10:53 I'm looking at on this page where if I
10:55 want to go into more detailed online
10:58 documentation or even connect to next
11:00 things online learning platform to do a
11:04 full-on uh you know tutorial view of of
11:06 the page that I'm looking at
11:09 but on this page I'm seeing first of all
11:11 the last day's worth of data but I've
11:13 got 30 days worth of History
11:16 at this detail level that I can scroll
11:18 back if I need to if I want to rewind
11:21 time and look for the beginning of a
11:23 particular pattern
11:26 situation where uh write a combination
11:28 of conditions may be started to indicate
11:31 where the problem is is beginning
11:34 all the details that I have on here help
11:36 me to understand things like the
11:39 resources that are being consumed on
11:41 that workstation at any point in time
11:44 and I can see how those resources are
11:47 being consumed by what applications and
11:51 processes if it's CPU if it's memory
11:54 see things like system drive space even
11:56 network connectivity right throughout
11:59 time so that I've got all of the
12:01 information that I need to really paint
12:03 a complete picture about what's
12:05 happening with this workstation again
12:08 throughout this user's day
12:10 other events that are being captured
12:12 here are things like when was the
12:15 systems restarted when did a user log in
12:17 when did packages or applications get
12:20 deployed to it or security fixes
12:24 how are the applications that are on
12:26 this workstation getting used throughout
12:29 the day what collaboration tools are
12:31 being engaged right all of this again
12:33 just paints a completer picture for me
12:35 of what's happening with this
12:39 workstation so that I can see how those
12:42 individual pieces correlate to give me a
12:43 better idea about what's happening with
12:45 this workstation
12:48 now up here near the top I can see that
12:50 this is one of the workstations that
12:52 contributed to that alert right they
12:54 caught my attention at the beginning of
12:56 the day and just below that I can see a
12:59 number of errors that have been captured
13:02 if I want to I take a closer look at
13:04 those particular errors then of course
13:06 I'm going to click into them which is
13:08 going to give me more information about
13:10 what's happening where that problem
13:13 began now I can see here from this
13:15 single workstation that I've got a
13:19 binary it's a the crowdstrike agent that
13:22 has been crashing on this Workstation
13:24 but maybe at the moment my lens is a
13:26 little bit too focused right looking at
13:28 this one workstation doesn't necessarily
13:31 give me in this particular case enough
13:33 information to understand exactly why
13:35 this application's crashing I don't see
13:38 any other correlating events on this
13:40 particular type line to help me
13:42 understand it so I might want to
13:44 leverage one of the next things
13:46 diagnostic engines I'm going to take a
13:48 look at what
13:51 next thing can tell me about this
13:52 particular application not just for this
13:55 workstation but across the entire Enterprise
13:56 Enterprise
13:59 all right the next thing Diagnostics AI
14:02 is essentially in the background all the
14:04 time whether you're awake or whether
14:07 you're asleep it's correlating the
14:09 different data points that are going on
14:17 on this Diagnostics page what I'm going
14:19 to see is things like
14:21 how many devices are being impacted by
14:23 this particular event
14:25 I can see how the instances of this
14:32 are are we increasing in frequency
14:35 is this something that just spiked and
14:37 then went away or is it something that
14:39 continues to build and is going to need
14:41 some attention
14:44 I can see things like how our company
14:46 benchmarks against all of the different
14:48 clients that are out there
14:51 right next thing is able to look across
14:54 the entire platform to help spot Trends
14:57 and events that might be impacting just
14:59 your organization
15:01 versus other organizations out there
15:02 that might tell you something about
15:05 whether this is a problem with your
15:06 particular Enterprise or whether it's
15:08 something that exists outside your four
15:10 walls which might suggest that it's a
15:13 problem that the vendor is working on
15:15 something like a you know a zero day
15:18 flaw that has just been exploited
15:21 in this case I can see it looks like our
15:23 company is experiencing a much higher
15:25 incidence of this particular problem
15:28 than the rest of the world so it does
15:29 seem to be a problem within our organization
15:31 organization
15:34 well how specific is it within our
15:35 organization I might need to understand
15:38 things like is it occurring at a
15:40 particular region or a particular
15:43 location right with all of the data that
15:45 I have available and next thing I can
15:47 drill down to whatever level is
15:50 necessary so that I can understand where
15:51 this problem is occurring who it's
15:54 occurring to and what other information
15:56 might help me to troubleshoot
15:58 but speaking of troubleshooting right
16:01 that's one of the things that the next
16:03 thing Diagnostics AI is doing in the
16:05 background at all time it's it's testing
16:07 out theories about what might be
16:11 happening with this particular situation
16:13 if this is an application crash then
16:16 what we're doing is looking at aspects
16:18 of the problem that might be commonly
16:20 associated with the problem is there a
16:23 particular OS that this seems to be more
16:25 prevalent with is this a problem with a
16:26 particular model and in this case
16:28 although that may be the issue what
16:30 we've surfaced at the top of this list
16:33 is that there's a strong correlation
16:36 between a particular version of this
16:39 application right there's a specific
16:42 binary version that's deployed within
16:45 our Enterprise which accounts for almost
16:47 all of the crashes that we're seeing
16:51 over the last you know time period
16:53 so what that tells me is that there's
16:55 not only a clear correlation with a
16:58 problem with this particular version but
17:00 you can also see other versions that we
17:02 have within the Enterprise that maybe
17:04 are more stable that are not
17:07 experiencing this particular problem in
17:09 fact right here I can see there's a
17:12 newer version of this application binary
17:15 which is not experiencing the kind of
17:18 Crash Ratio or frequency that the one
17:21 that seems to be a problem is
17:23 given that information I've got a pretty
17:26 clear idea that I've diagnosed this
17:28 problem right I've seen that there was
17:31 an issue the alerts told me that there
17:33 was a problem the Diagnostics page has
17:36 helped me to understand the core issue
17:40 and it suggests a fix
17:41 what is it that I'm going to do to
17:43 resolve this problem well clearly I need
17:47 to deploy the newer stable version of
17:50 the crowdstrike application to our
17:52 Enterprise in order to Tamp down the
17:55 instances of this crash occurring
17:57 well that's great how do I do that I could
17:57 could
18:00 traditionally send somebody out to the
18:02 workstations to do a deployment or maybe
18:05 I queue something up in our you know
18:07 package management system but next thing
18:10 also has the list of all of the
18:12 workstations that were impacted by this
18:15 particular event so not only do you not
18:18 need to just do a broadcast update but I
18:21 can specifically Target those users now
18:24 I might do that for one user I might do
18:27 it for a test bed I may do it for a
18:29 whole 115 set of users that are impacted
18:31 by this event
18:35 right by selecting them I'm targeting
18:37 the update to the specific workstations
18:39 that need
18:41 the installation of the updated package
18:44 by executing this across all of those devices
18:45 devices
18:49 I can speed the Enterprise on to getting
18:52 back to a productive State without all
18:53 of the crashes interrupting day-to-day
18:56 operations right as simple as just
18:58 saying these are the workstations that I
19:01 want to deploy this to going ahead and
19:03 deploying it
19:05 now that's one way that I can
19:08 unilaterally deploy and update in order
19:11 to fix a problem that we've diagnosed we
19:14 may see opportunities to do something
19:16 like this with a security agent right
19:19 where a unilateral fix may make sense
19:23 there may be other times when deploying
19:26 an update might require us to Engage The
19:28 End user in order to understand whether
19:32 now is a good time to deploy that update
19:34 to replace a piece of software right
19:37 that may be common with things like
19:38 applications that are used for
19:40 collaboration that are used for
19:42 communications things that we don't want
19:45 to necessarily interrupt a user with in
19:48 the middle of their day in which case
19:52 the next thing engage campaign can be
19:55 used to ask the user is now a good time
19:58 for us to deploy the software to you
20:01 right engage can provide you with that
20:03 two-way interface first of all to get
20:06 input for things like
20:08 is now a good time for us to replace the
20:10 software for you but also to ask the
20:13 user for information about how is their
20:17 I.T service working for them to get
20:20 their their sentiment included in the
20:24 overall picture of how is our I.T
20:26 resource working for our employees right
20:28 and that allows you to do things like
20:31 set up The Branding you can identify
20:33 who's sending the message so that it
20:36 builds trust in your I.T department and
20:39 all of these right allow you to to craft
20:42 very specific very targeted messages so
20:45 that you can quickly send that message
20:47 out to the people in the organization
20:50 that need to get it you can ask them the
20:52 quick question that's going to give you
20:54 the information that you need
20:58 and then based on those results The Next
21:00 Step can be automatically handled in
21:03 this case right we're asking this user
21:05 what time would you like to receive this
21:07 update and they may say hey before I get
21:09 to work or maybe during my lunch break
21:12 would be a good time for this deployment
21:14 that's not going to impact me that much
21:17 to do it during those times
21:19 right and just by answering that quick
21:22 question right one simple question just
21:24 give me a time or a couple of times that
21:27 would be good we've engaged the user
21:29 we've told them that we're aware of the
21:32 problem that we have a fix for it and
21:33 that we're going to go ahead and deploy
21:36 it according to their preferences
21:39 now all of that information right is
21:42 going out to uh to provide your it team
21:46 with the visibility to understand where
21:48 they can spend their time most
21:51 effectively right to help the
21:54 organization at the broadest sense and
21:56 now that I've handled that issue
21:58 you know I can go back to the alerts page
21:59 page
22:02 I can start my day here every day or
22:04 after lunch now that I've handled that
22:06 issue I can refresh this page next thing
22:08 is going to provide me with a new
22:11 stacked list of the issues that are
22:12 causing the biggest impact to the
22:15 organization so I always know
22:18 where I can invest my time to have the
22:21 best results for the organization so
22:23 that I can make the the most good happen
22:26 for our employees and for the overall
22:29 organization as a whole
22:32 but that's my view as a member of the it
22:35 organization into how next thing can
22:36 help me
22:38 but I know of course next thing can do
22:40 uh you know a ton of different things
22:43 for the organization not everybody is on
22:46 the help desk like me I may have
22:48 um others in the organization that would
22:50 like to get a more Enterprise view
22:53 things like my uh Executives may need a
22:57 more broad high altitude view of what's
22:59 happening in the organization
23:01 so as we wrap up here I'll just take a
23:03 quick look at the experience Central
23:07 page right where we pull together and
23:09 summarize a lot of the data that I've
23:10 been talking about on the individual
23:13 sense into that broader view of the organization
23:15 organization
23:17 experience Central is going to give me
23:20 some visibility into things like how our
23:24 score our users experience of the I.T
23:26 services that we're providing has
23:28 changed over time so I can see whether
23:30 it's trending in the right direction or
23:32 not it's going to give me summary level
23:33 information about the number of
23:36 employees impacted by negative events
23:39 and even calculate things like how much
23:42 time is being invested or wasted in
23:45 those problem areas
23:47 that information can give me technical
23:50 information about particular
23:53 applications environments endpoint
23:56 resource constraints our collaboration
23:58 tools right all of that is giving me
24:01 visibility over time into how those
24:03 resources are performing from a
24:06 technical operational standpoint but as
24:08 I mentioned those engage campaigns can
24:11 also give me sentiment data so by asking
24:14 employees with quick targeted surveys
24:17 how they're feeling about their I.T
24:19 Services then they can give me feedback
24:21 that also marries that operational data
24:24 with experience data so that I've got a
24:26 more complete picture about how
24:29 employees are feeling as they engage
24:32 with their I.T resources through the day
24:34 right this information gives me the
24:37 ability to see things like what
24:39 potential score improvements uh we could
24:41 get by targeting particular areas that
24:43 are maybe not performing well right now
24:46 or uh seeing things like time loss per
24:49 week or employee counts with issues
24:50 right gives me a good summary level
24:53 information so at the executive level
24:56 I've got some visibility into what's happening
25:01 so I think that's about what we have
25:04 time for today Andy
25:07 um I think it's uh it's time to get uh
25:09 to get you back on the mic
25:12 thank you very much and that's fantastic demo
25:14 demo
25:16 um yeah I mean we've been looking at
25:18 Infinity now for a long time and seeing
25:20 an action it's fantastic and by the way
25:23 that is just a very brief small snippet
25:25 of some of the things that Infinity can
25:27 do just to reiterate we saw real-time
25:29 alerting cutting through the the noise
25:32 and the silos to find patterns in issues
25:34 affecting employee experience providing
25:37 the early warning sign we saw AI powered
25:40 issue-centric Diagnostics the impact and
25:42 scope and context and correlation to
25:45 potential fixes for application versions
25:47 build versions operating system versions
25:50 and we saw this incredible ability where
25:53 appropriate that we can fix issues in
25:55 real time at scale to all impacted employees
25:57 employees
25:59 automatically in the background and of
26:01 course Very impactfully when the
26:03 employee decides to minimize the
26:05 negative disruption on their day and
26:08 again this is just the very beginning of
26:12 what the infinity platform is capable of um
26:13 um
26:15 we don't have time to go talk about it
26:18 today but in our platform we very much
26:21 want to address many other use cases so
26:23 we have various expansion products that
26:25 sit on top of our base platform
26:28 application experience is a product you
26:31 may be aware of already 360 degree very
26:34 comprehensive view of all applications
26:36 when it goes into SAS applications being
26:38 able to look at the back end the network
26:41 the client understand how web
26:42 applications are being delivered and
26:44 adopted and their performance and if
26:46 people are happy with them is absolutely
26:49 game changing Employee Engagement you've
26:50 seen a bit of that already as well as
26:53 unlocking the ability for people to
26:54 self-serve and decide when fix is
26:57 deployed there's also the ability to
26:58 collect sentiment to understand what
27:00 they really need to make their day
27:03 better so they Thrive through technology
27:05 and of course collaboration experience
27:08 where many of us are very reliant on
27:11 tools like teams and zoom so being able
27:12 to have extremely good deep
27:15 comprehensive analysis of the experience
27:17 delivered by these tools and then
27:19 surfacing it through alerting
27:21 Diagnostics and device you and all of
27:23 these base platform capabilities that
27:25 you've just seen again is a game changer
27:28 we continue and next thing to go from
27:30 strength to strength um this has been
27:32 the culmination of many years of work
27:35 it's a proud moment for the company and
27:38 we continue to
27:42 um push the envelope on what's possible
27:44 um we'd like you to provide more
27:46 information so if you want to know more
27:48 information about the platform go to
27:51 nextthink.com forward slash platform
27:52 um if you want to know more information
27:54 get in touch with us and have a more of
27:57 a personalized demonstration again go to
27:59 the next thing.com forward slash demo
28:01 but of course we'd love to meet you in
28:04 person and we have a number of events
28:05 running in October called experience
28:08 everywhere they are back uh if you're in
28:10 Paris London Frankfurt or New York
28:12 please uh we encourage you uh register
28:15 for these events come and see us and
28:17 come talk to us about infinity and the
28:19 way that we can help you um
28:19 um
28:21 we hope this session has been very
28:23 informative there's been a number of
28:25 questions that have come through
28:27 we have a few minutes left um I want to
28:29 be respectful of time so I've seen a few
28:30 ones that we haven't answered through
28:33 the Q a uh Doug I'm going to bring you
28:34 in on a couple of them but the first one
28:36 is we mentioned alerts how are these set
28:39 up uh well the the great thing about
28:41 Infinity is all of that Telemetry that's
28:42 coming in
28:44 um basically is available at the
28:46 fingertips of the administrator you can
28:49 create alerts on any of this
28:52 intelligence now where do you start so
28:54 what we will do with infinity is provide
28:56 built-in alerting for the most common
28:59 and pervasive issues that we're seeing
29:01 in our customers to get you started
29:03 again think about across all of those
29:05 silos when they come together in front
29:07 of the user that's what we want to be
29:09 alerting on and getting ahead of issues
29:12 of course these can be customized and
29:14 any of these can be created and we have
29:16 a very rich and expressive simple
29:19 language allows you to interrogate all
29:20 of the data that's available in the
29:23 platform in real time very very powerful um
29:24 um
29:26 Doug uh quick question
29:28 um I see one here how many endpoints
29:29 does infinity support it's kind of
29:32 scalability question so yeah actually
29:33 I'm glad that we got that question
29:34 because it allows me to talk about
29:36 something that's that's not so visible
29:38 at the front end which is the tremendous
29:41 uh you know scale and capacity that the
29:44 next Infinity platform so for any
29:46 customer uh we can support up to a
29:48 million endpoints uh with no problem and
29:50 of course that's across all of the uh
29:52 the customers that we have on the
29:54 infinity platform so
29:56 yeah and I think another kind of a
29:58 couple of questions about this um maybe
30:00 there's some existing customers on but
30:02 can we expect kind of more features and
30:04 content in the future so um what we've
30:06 before I dug you past you have been what
30:09 we've shown today is just a very very
30:11 bad the core problem that we solve with
30:12 our platform but there is so much more
30:14 out there so
30:15 um more features what else is available though
30:17 though
30:19 yeah well uh certainly uh you know watch
30:21 this space right more is going to be
30:23 coming on a regular Cadence uh for those
30:25 customers that already know uh we have a
30:27 five-week release Cadence uh so there
30:29 are releases with additional features
30:31 and capabilities coming out uh every
30:34 five weeks or so now some of those uh
30:36 releases like uh this one is pretty
30:38 large and has a lot of you know
30:40 significant features some of them are
30:42 going to be uh you know smaller in scope
30:44 but that regular five-week Cadence will
30:47 keep new content and capabilities coming
30:50 on a regular basis
30:53 and exactly and again we have a library
30:55 which we expose will be exposing through
30:57 the product to use uh which helps you
31:00 answer specific use cases uh going
31:02 forward so Windows 11 migrations all
31:04 those kind of things uh we can then add
31:05 value in as well and that's
31:06 traditionally what we've been doing with
31:09 next thing for many years
31:10 um I think one more question there's a
31:13 couple of ones around uh is this
31:16 available on premises so this is a cloud
31:18 only product
31:20 um so no this this is not something on
31:22 premises all you need to be able to
31:23 access all of that amazing uh
31:25 functionality that I've shown is a
31:27 browser and we do all the heavy lifting
31:30 for you on our Cloud platform it's a SAS
31:31 service so
31:33 um I've seen lots of questions and uh
31:35 some people here are answering by the Q
31:38 a chat so with that I think we are a few
31:39 minutes over
31:42 again I want to say thank you to
31:44 everyone as the response has been uh
31:47 amazing to Infinity it's only the
31:49 beginning we've shown you a sneak peek
31:52 of what the capabilities are we intend
31:56 to uh keep uh improving and pulling away
31:58 from our competition and in the category
32:01 that we created so um it's been an
32:03 immense privilege to present to you guys
32:05 and with that I want to say thank you
32:07 and from everyone here at next think
32:09 have a fantastic day thank you yeah
32:13 appreciate it thanks all Andy and uh