42: 911 Secure

WEBVTT
00:00:02.229 --> 00:00:05.129
Welcome to ACP, the Amazon Connect Podcast.
00:00:05.469 --> 00:00:09.140
This is the show that focuses on Amazon Connect and related technologies.
00:00:09.640 --> 00:00:17.609
I'm your host, Tom Morgan, and I'm joined as usual by my co-host, AWS solution architect and contact center consultant, Alex Baker.
00:00:18.410 --> 00:00:27.300
We are also joined this week by Kevin Kitto, President and CEO at 911 Secure, and Alan Gaspe, solution architect at 911 Secure
00:00:35.451 --> 00:00:37.011
It's time for another ACP.
00:00:37.040 --> 00:00:38.161
We are back.
00:00:38.271 --> 00:00:38.990
Alex is here.
00:00:39.060 --> 00:00:39.750
Hello, Alex.
00:00:39.771 --> 00:00:40.091
How are you?
00:00:40.591 --> 00:00:40.881
Hi, Tom.
00:00:40.890 --> 00:00:41.941
I am good, thank you.
00:00:42.420 --> 00:00:47.511
Had a good week of mainly outbound campaigns this week, which has been quite interesting.
00:00:47.511 --> 00:00:49.140
Seem to be getting a lot of projects on that.
00:00:49.390 --> 00:00:49.941
How about you?
00:00:49.951 --> 00:00:50.261
All good?
00:00:50.689 --> 00:00:51.219
Yeah, all good.
00:00:51.219 --> 00:00:51.598
Thank you.
00:00:51.649 --> 00:00:53.329
So really interesting episode today.
00:00:53.329 --> 00:00:54.348
Really looking forward to this one.
00:00:54.408 --> 00:01:04.649
We're gonna be talking all about 911 and 911 calls and the obligations and the solutions all around providing that as part of a phone system.
00:01:04.649 --> 00:01:11.588
And we thought who better to come and help us talk about this than the folks over at 911 Secure.
00:01:11.599 --> 00:01:22.209
And so I'm delighted to be able to introduce Alan Gaspe, who is a solution architect at 911, and also Kevin Kitto, who's the president and CEO of 911 Secure.
00:01:22.218 --> 00:01:23.308
Gentlemen, hello.
00:01:23.349 --> 00:01:24.358
Welcome to ACP.
00:01:24.608 --> 00:01:25.698
Hey guys, nice to see you
00:01:26.921 --> 00:01:27.070
you.
00:01:27.251 --> 00:01:27.941
Thank you for having us
00:01:28.191 --> 00:01:28.450
All right.
00:01:28.570 --> 00:01:38.111
Can we start with you, Kevin, I think maybe just for a brief introduction to the company and why 911 Secure, why now, and a little bit about what you do, and then we can go from there
00:01:38.668 --> 00:01:39.118
Sure, yeah.
00:01:39.118 --> 00:01:42.198
So I've been in the, the 911 industry for about 20 years.
00:01:42.578 --> 00:01:44.748
We started 911 Secure over eight years ago.
00:01:44.748 --> 00:01:47.899
We're in our ninth year now, and we do all things 911.
00:01:48.088 --> 00:01:56.659
Somebody makes a 911 call from a wired phone or a cell phone or whatever that's what w- our lives revolve around that making sure that the best possible outcome happens.
00:01:56.659 --> 00:02:07.399
The call gets routed to the right place the right people on site are notified with the location information where that call is coming from, and the person who made the call is either resting comfortably in a hospital or they're at home with their family.
00:02:07.459 --> 00:02:08.808
That's the whole point of 911 Secure.
00:02:09.396 --> 00:02:15.296
Gosh, it's one of those things we'd never really think about un- until you suddenly need it and you hope somebody else has been thinking about it all this time.
00:02:15.673 --> 00:02:15.902
Yeah.
00:02:15.902 --> 00:02:20.342
That's exactly the whole thing is, yeah, it's oh gosh, I'm never gonna dial 911.
00:02:20.342 --> 00:02:34.203
And talk to so many people, like w- with what we do, and a lot of people are, have this misunderstanding that they think,"Oh, no matter what, any phone that I pick up, if I dial 911, the 911 operator's gonna know exactly where I'm at, and I don't have to say anything," that type of thing.
00:02:34.203 --> 00:02:35.772
And obviously that's not the case, so
00:02:35.908 --> 00:02:37.679
And Alan, you're a solution architect.
00:02:37.729 --> 00:02:40.979
I guess the problem statement is fairly well-defined actually in this case, isn't it?
00:02:40.979 --> 00:02:43.829
It's more that the, maybe the landscape you're going into is different.
00:02:43.889 --> 00:02:46.769
Is that true, or are there lots of different variables to think about?
00:02:46.895 --> 00:02:55.645
There are definitely a lot of variables, especially in today's world where we've got cloud computing and, you're not physically connected to really anything, right?
00:02:55.645 --> 00:02:57.474
You're all use-- everybody's using wireless.
00:02:57.485 --> 00:02:58.675
Everything's up in the cloud.
00:02:59.064 --> 00:03:07.814
So in the old days, it was pretty easy'cause, you had a, a, a piece of copper that tied a, a phone to a port, and then that port was in, a particular location.
00:03:07.814 --> 00:03:09.004
So that was pretty easy.
00:03:09.435 --> 00:03:26.685
But in today's world, especially in the contact center space, where you have agents working from just a, a web browser that they're just lighting up from anywhere, that, that really introduces a lot of challenges of, like, where is this person and how do we get them to one of the over five thousand answering points across the the country, right?
00:03:26.685 --> 00:03:31.504
So it's really, there is a lot of technical complexity on the back end to try and solve for that.
00:03:31.905 --> 00:03:35.354
'Cause to to Kevin's point, it's nine one one's kinda like just water in the taps.
00:03:35.354 --> 00:03:39.324
You turn it on, you're expecting the water to come out, and you don't have to think about it.
00:03:39.745 --> 00:03:49.064
But just with anything else with technology, there's a whole bunch of stuff underneath the covers, and a whole bunch of people working behind the scenes to make sure that everything kinda works when you need it
00:03:49.691 --> 00:03:51.480
It's worth, maybe worth calling out as well.
00:03:51.711 --> 00:04:02.800
I think this is maybe slightly more of a US-centric episode this time around, but, super interesting hopefully for everyone and for partners and especially customers in the, the US.
00:04:02.850 --> 00:04:10.890
I don't think in the UK we, we have any of the same sort of regulation around 999 calling, for example.
00:04:10.901 --> 00:04:19.500
So I think coming into it as a, a UK-based partner, I was probably slightly unaware of the, a- actually the complexity of the...
00:04:19.690 --> 00:04:20.951
There's a couple of laws, aren't they?
00:04:20.951 --> 00:04:22.281
Whi- which I think we'll come onto.
00:04:22.281 --> 00:04:29.571
But it's very specifically laid out in law around 911, whereas it isn't for 999 calling in the UK
00:04:29.821 --> 00:04:29.870
Yeah, that's definitely true.
00:04:29.870 --> 00:04:30.971
We should definitely talk about that.
00:04:31.040 --> 00:04:43.321
I think just before we do, it's worth mentioning and saying that we know about you guys through some work that we've done through Cloud Interact, and we think we're quite good at Amazon Connect, but there's a couple of places where we know we need to bring in partners.
00:04:43.370 --> 00:04:44.211
And this is one of them.
00:04:44.221 --> 00:04:47.701
This is one of them where it's like this is a whole separate thing by itself.
00:04:47.740 --> 00:04:53.011
There's specialist knowledge here, and a lot of that is on the compliance re- like the legislation requirements.
00:04:53.211 --> 00:04:56.401
And I was just looking through your website actually,'cause I was bringing myself up to speed.
00:04:56.401 --> 00:05:08.391
Not that I'm not all over all of the 911 legislation, but I was just like looking through it, and I was like, I got the first bit, and I was like,"Yeah, that all makes sense." And then you scroll down, and every state is slightly different, and it's like, wow, there's like there's a lot going on here, right?
00:05:08.810 --> 00:05:15.651
Let's talk about the legislation then actually, because it's interesting if you're not from the US to think about it, and it totally makes sense, I think, when you say it.
00:05:15.860 --> 00:05:22.341
Could you just briefly take us through like I- I guess there's two main kind of laws and acts, right?
00:05:22.380 --> 00:05:24.990
And they've got like names, but they're ones that people have probably heard of.
00:05:25.490 --> 00:05:25.980
Yeah, Tom.
00:05:25.980 --> 00:05:34.230
So the, yeah, like you said, there are states that have different legislations, but the two that everybody hears about is the national federal legisla-lation Kari's Law and RAY BAUM's Act.
00:05:34.230 --> 00:05:36.411
And Kari's Law has three tenants.
00:05:36.440 --> 00:05:41.630
One of them is being able to just pick up any phone and dial 911, not have an hit an access line or anything like that.
00:05:41.630 --> 00:05:44.430
And that's usually simple programming in the phone system.
00:05:44.690 --> 00:05:48.221
The second one is the calls need to route to the local public safety answer point.
00:05:48.511 --> 00:05:51.771
They just really don't want the calls to route to a front desk or on-site security.
00:05:52.060 --> 00:05:54.711
And then the last one is immediate on-site notification.
00:05:54.711 --> 00:06:05.930
And when they say immediate, they really want that to be right when somebody dials 911, somebody is notified rather than there's some, some systems out there that will notify when people hang up and stuff, that's really not good enough.
00:06:06.221 --> 00:06:13.060
So we really want those to be people to be notified so that when police, fire, and ambulance get to the scene, they're not like,"Hey, what are you guys doing here?" They'll already know.
00:06:13.060 --> 00:06:17.550
They maybe already unlocked doors or stationed somebody in the parking lot, those types of things.
00:06:17.560 --> 00:06:19.850
So that's the three parts of Kari's Law.
00:06:20.161 --> 00:06:23.321
And again, yes, these are L- US legislation requirements.
00:06:23.341 --> 00:06:31.240
The second one is Section 506 of RAY BAUM's Act, and that one is where y-you need to provide some-something other than just the address.
00:06:31.740 --> 00:06:36.411
I think it's pretty obvious, you need to provide the actual right address of the building that the, the call's coming from.
00:06:36.781 --> 00:06:39.761
But you also need to provide something else other than that.
00:06:39.810 --> 00:06:54.141
So you need to say, hey, maybe it's building two, west entrance, third floor, northwest quadrant or something along those lines, so that when the first responders get there, especially say it's at night and there's hardly anybody in the building, they know kind of the general area of where to go.
00:06:54.331 --> 00:06:55.790
So those are the two laws.
00:06:55.790 --> 00:06:59.290
I don't know, Alan, if you wanna jump anything else on there, but those are the basic laws.
00:06:59.790 --> 00:07:00.071
Yeah.
00:07:00.071 --> 00:07:06.341
And that's really where some of the complexity comes in is yeah, okay, this guy's at 123 Main Street, but what floor is he on?
00:07:06.651 --> 00:07:07.891
Or what zone is he in?
00:07:08.321 --> 00:07:15.190
And that's really where that dispatchable location comes into play of it's really de-depends on the actual environment, the facility.
00:07:15.211 --> 00:07:23.221
'Cause like a, a warehouse, for example, with a big square footage may be a little bit different than a than like an office tower where there's seven or eight floors.
00:07:23.781 --> 00:07:30.350
It really comes down to making sure that when a first responder shows up, they know where to go, how they can actually reach that user.
00:07:30.730 --> 00:07:42.290
And to Kevin's point about the onsite notification, en-engaging the security team that is actually gonna be opening gates and providing access to the facility, it also gives them the ability to actually respond.
00:07:42.610 --> 00:07:48.130
So they may have first aid training, they may have like a defib kit that they have at the front desk, something like that.
00:07:48.461 --> 00:07:55.610
It gives them a chance to get engaged, and it really just helps to kinda coordinate a response when the, the first responders show up, they know what's going on.
00:07:56.081 --> 00:08:01.591
The gates are open, the gurney-capable elevators are ready, and the first aid team's already there.
00:08:01.630 --> 00:08:06.370
So that's really what we're trying to do is just m-make these outcomes a lot better, right?
00:08:06.370 --> 00:08:11.540
'Cause, the people will only use our system on the worst day of their lives, so we wanna make it nice and smooth and easy for them
00:08:11.966 --> 00:08:12.307
Yeah
00:08:12.346 --> 00:08:27.391
do, how does it work then in terms of, the practicalities of it in a massive office or warehouse, you're being able to actually more accurately pinpoint where that person is, what kind of things, w-what are you looking for in order to be able to more accurately find them?
00:08:28.040 --> 00:08:28.250
Yeah.
00:08:28.250 --> 00:08:29.130
So that's a great question.
00:08:29.130 --> 00:08:34.280
So that, that kinda comes down to the complexity of how this works, especially in a cloud environment, right?
00:08:34.760 --> 00:08:48.311
So what we typically do is we we break up a particular building, say a warehouse, into zones or areas and then tag out the the wireless access points, for example, saying these different wireless access points are on the third floor.
00:08:48.350 --> 00:09:06.311
And then we have a piece of software c- we call Gatekeeper that sends us a, a notification that says,"This phone is now connected to this wireless access point." That wireless access point's been tagged out to be warehouse B, northwest corner, you know, column four, door six, or whatever, wherever it happens to be located.
00:09:06.801 --> 00:09:08.541
So we do that either by by...
00:09:08.671 --> 00:09:14.760
It really kinda goes down to identifying where that device is connecting to the physical network, right?
00:09:14.760 --> 00:09:18.760
So in today's world where everything is all cloud-based and everything, there is still that access layer.
00:09:19.140 --> 00:09:45.610
So that's where we kinda drill down to, is looking at the IP address, looking at the wireless access point BSSID that they're connected to, the MAC address, things like that, that the, the underlying fundamental part of how the internet works is really how we can actually drill down and say,"This particular MAC address is connected to this particular BSSID of this access point, and that's on the third floor at 123 Main Street in Skokie, Illinois," or wherever it happens to be
00:09:46.578 --> 00:10:00.769
I think that's a-- that's right there a great example of why you might wanna use a, a partner like yourselves,'cause I think you can put certain measures in place, certainly in Amazon Connect, to try and be compliant with some of the laws and regulations you mentioned.
00:10:00.778 --> 00:10:07.028
But actually, I'm not sure if people would consider it to that depth and granularity that you have to be able to do that
00:10:07.528 --> 00:10:16.308
One other big important point about both Kari's Law and Ray Baum's Act is who's responsible for making sure that the laws are compliant or you're compliant with the laws.
00:10:16.509 --> 00:10:24.778
And obviously the end customer, the person who's using the phone system, they're obviously one of the people who, or one of the entities that needs to make sure that the organization is compliant.
00:10:24.958 --> 00:10:28.249
But then the other one is they're called the leasing se- installation company.
00:10:28.249 --> 00:10:32.708
So the actual one who's selling the phone system, they're actually called out in the law as well.
00:10:32.908 --> 00:10:37.668
And that's why we always tell our partners,"Hey you can't force the end customer to do something.
00:10:37.958 --> 00:10:45.589
But at the very minimum, you could introduce a solution to say,'Hey, here's a solution, here's a quote for it,' that type of thing." So that's why we always say,"Hey, it's...
00:10:46.208 --> 00:10:47.399
when something bad happens, or...
00:10:47.599 --> 00:10:49.308
people are gonna sue everybody involved, right?
00:10:49.349 --> 00:10:51.278
And so at least if you could say,'Hey, you know what?
00:10:51.278 --> 00:10:55.428
We provided a quote, we provided this, and the customer decided not to do anything.
00:10:55.438 --> 00:10:56.678
We did our part.
00:10:56.719 --> 00:11:02.099
We can't force the customer to do this.'" So that's why we're always talking with our partners to just get the word out there, kinda like what we're doing right now.
00:11:02.883 --> 00:11:16.832
I think maybe a lot of folks assume that something like Amazon Connect would have it all built in because they haven't been through that thought process of like this is a joint exercise between something like Connect and networking on the ground to make that transition, if you like.
00:11:16.852 --> 00:11:20.423
You've gotta make that jump down to the physical reality of where this stuff is.
00:11:20.822 --> 00:11:25.322
So I wonder if a lot of people just kinda think,"Oh Connect sorted it out," without really thinking it through.
00:11:26.065 --> 00:11:27.054
Oh yeah that's the thing.
00:11:27.065 --> 00:11:42.625
Everybody just thinks,"Oh the phone system's just gonna do it." Like I said right off the top, anytime I talk to anybody about what I do, they're like,"Wait a second." The first time I talked to my brother-in-law about it, the he was like-- He works for a large city here in Southern California, and I was like,"Yeah, if you make a 911 call, they're not gonna know where you're at.
00:11:42.644 --> 00:11:45.985
Actually, the call's gonna give an address at a different building." He's like,"Wait a second.
00:11:45.985 --> 00:11:48.705
What are you talking about?" Everybody just thinks that, oh, it just works.
00:11:48.735 --> 00:11:52.434
Even the people a lot of times who are implementing the phone system, it's like an afterthought.
00:11:52.434 --> 00:11:56.294
It's like,"Oh, we're going live," and we've gotten many of those calls the last minute.
00:11:56.304 --> 00:12:05.054
They're like,"Oh my gosh, we're getting this to go live, and we totally forgot about 911 and it was a last-second thing, and all right, we need, we, we--" It's scrambling to get a solution in place.
00:12:05.414 --> 00:12:05.615
So yeah
00:12:06.115 --> 00:12:06.445
Yeah.
00:12:06.794 --> 00:12:09.914
Okay, so this is a, podcast for Amazon Connect folks.
00:12:09.924 --> 00:12:17.674
So if you're running a contact center operation on, you're running it on Amazon Connect and you haven't thought this through yet, what should you be thinking about?
00:12:17.674 --> 00:12:28.607
What are the things you should be thinking about to make sure that, people using your Connect system, the Connect system you are responsible for can, get their location correctly notified if needed?
00:12:29.107 --> 00:12:36.518
So the way that it technically works is as the user is setting their location, we're storing that in in our cloud, keeping that up to date with with...
00:12:36.557 --> 00:12:37.628
as the user is moving.
00:12:37.988 --> 00:12:42.278
And then the only time that location is actually really shared is during a 911 call.
00:12:42.408 --> 00:12:47.248
'Cause Connect will send an API query over to our cloud, say,"Here's this user's identifier.
00:12:47.248 --> 00:12:50.888
Where is he?" We then return back the location, and then off it goes from there.
00:12:51.388 --> 00:12:55.937
From a location tracking perspective, it's only available for 911 calls.
00:12:56.177 --> 00:13:01.028
If you're placing a call outbound to Domino's Pizza, none of that location information is actually shared at all
00:13:01.629 --> 00:13:01.940
Got it.
00:13:01.960 --> 00:13:02.980
Okay, that makes sense now.
00:13:02.980 --> 00:13:03.460
I understand.
00:13:03.509 --> 00:13:05.159
Might be useful for Domino's Pizza as
00:13:05.354 --> 00:13:06.124
Yeah, I know.
00:13:06.179 --> 00:13:06.779
got side angle but
00:13:07.029 --> 00:13:07.860
Yeah, definitely.
00:13:08.159 --> 00:13:08.500
All right.
00:13:08.549 --> 00:13:18.220
So Connect supports this 911 location stuff by virtue of saying if you're making a 911 call, it can call an API, but you gotta set it up.
00:13:18.259 --> 00:13:19.610
You figure out what API it is.
00:13:19.629 --> 00:13:25.659
Like you figure out, you tell us where to call and like we'll give you the, like the number or the agent and you give us back the location.
00:13:25.710 --> 00:13:31.320
And then what you guys do is fill in that gap basically to make sure everything stays up to date all of the time and it's ready to go.
00:13:32.177 --> 00:13:33.138
Yeah, e-exactly.
00:13:33.138 --> 00:13:45.947
So like to your point, Connect does have some E nine one one functionality in it, and it's really when a call comes out, grab a location from some other system, wherever that's coming in from, and then just send the call outbound.
00:13:46.408 --> 00:13:50.327
So Connect provides the the routing and the connectivity and things like that.
00:13:50.648 --> 00:13:53.177
But to your point, what we're doing is we're providing the location.
00:13:53.577 --> 00:13:59.447
So instead of it coming out of a static HR database or something like that, the Gatekeeper client is dynamic.
00:13:59.457 --> 00:14:05.738
It allows them to track if a user's like a hybrid user where he's in the office three days a week, and then he goes home for another two.
00:14:06.087 --> 00:14:09.278
Or you got a guy like me, I'm chained to my desk in the basement.
00:14:09.337 --> 00:14:10.477
I never go anywhere.
00:14:10.758 --> 00:14:13.648
I set my location once and it maintains that and tracks that.
00:14:14.048 --> 00:14:18.548
But that is definitely the piece that we're adding in is the the location of the call.
00:14:18.557 --> 00:14:24.398
Like the Connect system, it basically queries and says,"Hey, where is this user?" We return back a location payload.
00:14:24.817 --> 00:14:30.128
It kinda gets stapled into the the outgoing SIP invite, and that's how the location is sent.
00:14:30.138 --> 00:14:44.307
But maintaining the location and making sure it's up to date and accurate, that's essentially the major piece that we're adding into this, in addition to the notification capabilities that we have to notify security personnel or HR managers, things like that.
00:14:44.557 --> 00:14:44.878
Got it.
00:14:44.998 --> 00:14:46.687
That's really not a trivial thing, is it?
00:14:47.148 --> 00:14:53.807
The, just like maintaining a database'cause we- we've seen it in the past where, it becomes quite a, a management overhead.
00:14:53.988 --> 00:15:04.937
We can put something in as a partner maybe with the building blocks that are available to us, but somebody's then gotta take on the ownership of that, that database, make sure it's up to date via some mechanism.
00:15:04.998 --> 00:15:13.148
It's so helpful that you guys can just take care of that automatically and follow those nomadic workers around and make sure they're always up to date.
00:15:13.398 --> 00:15:22.138
Yeah, and it's also impossible for an administrator just to ha- stay on top of it, especially if you have work-at-home agents where, they can light up at a at Starbucks.
00:15:22.138 --> 00:15:25.177
They can light up their client at their mom's house or whatever.
00:15:25.548 --> 00:15:31.158
And it's a really-- the, the Gatekeeper application is really meant to kinda track users when they're on-premise.
00:15:31.158 --> 00:15:35.408
So if they're working in-inside the contact center, they have to come on-premise and they're working there.
00:15:35.408 --> 00:15:38.817
That's where the tracking the automatic discovery kinda comes into play.
00:15:39.207 --> 00:15:43.878
But if they're working remotely, Gatekeeper's smart enough to know,"Wait a second, I don't recognize where I am.
00:15:44.217 --> 00:15:45.878
I'm on a different wireless network.
00:15:45.878 --> 00:15:49.768
I don't understand where I'm at." And it then prompts the user to to provide it.
00:15:49.807 --> 00:15:58.327
From an administrative perspective, there's no way to, for an administrator to stay on top of the movement of all of their agents, this guy lights up his his client.
00:15:58.327 --> 00:16:00.837
He's working from from his cottage or something like that.
00:16:01.087 --> 00:16:04.738
The administrator doesn't have the bandwidth to actually go through and track all of that.
00:16:05.028 --> 00:16:08.087
So we try and give the user the tools to kinda manage it themselves.
00:16:08.408 --> 00:16:13.697
And then that also gives the administrator and the the organization the ability to say,"Hey, we gave you the tools.
00:16:13.977 --> 00:16:14.908
You can use them.
00:16:14.957 --> 00:16:18.988
If you don't use them, that's on you, but we've given these tools to be able to to manage this."
00:16:19.764 --> 00:16:19.974
Yeah.
00:16:19.974 --> 00:16:22.833
One, one point that I wanted to make is y-you're right, Alex.
00:16:23.264 --> 00:16:38.214
Trying to maintain this database as a customer, it's like you have all these other things that you have to think about, and then if you're just like,"Oh, I'm gonna shirk that responsibility'cause oh, 911, no one's gonna call 911." Giving the wrong location information is obviously worse than giving no location information because then you're, confusing everybody.
00:16:38.214 --> 00:16:47.524
'Cause the person on says,"Oh, they got this on their screen." It's like no, I'm actually over here." That's obviously been a, a big problem with this, and that we've been trying to solve for all these years,
00:16:47.874 --> 00:16:48.163
yeah.
00:16:48.193 --> 00:16:58.663
It's exactly one of those problems that you don't wanna stop thinking about, and there's all these weird edge cases that I'm sure you're thinking about are like this"Hey, we haven't had anything location-wise for this agent for a while.
00:16:58.683 --> 00:17:02.053
That's weird." All these things that you just wouldn't think about unless you're thinking about it all the time
00:17:02.104 --> 00:17:02.333
Yeah.
00:17:02.333 --> 00:17:14.963
One other thing that we've seen, since we've been doing this for so long, especially when people first started getting soft phones on laptops, literally there was companies that would send out stickers that said,"Do not use for 911." That was the solution for 911.
00:17:15.064 --> 00:17:19.624
And we actually still hear that today where people are like,"Ah, who's gonna use their soft phone to make a 911 call?
00:17:19.644 --> 00:17:20.334
No one's ever gonna do that.
00:17:20.443 --> 00:17:24.483
Everybody's gonna use their cell phone." But since we've been in this industry for a while, we've heard of the stories.
00:17:24.493 --> 00:17:27.693
There was one story of a guy who, he was a sales guy, he was out on the road.
00:17:27.693 --> 00:17:29.513
He went to check into his hotel.
00:17:29.693 --> 00:17:35.453
He plugged his phone in between the two beds in the hotel room, and then he went over to his desk and he starts using his computer.
00:17:35.673 --> 00:17:45.473
And thank goodness he was able to, put his location information in, and then he started having chest pains and he went up, like anybody would, to go pick up the phone on his cell phone, but he couldn't get up out of the chair.
00:17:45.663 --> 00:17:48.104
And he's like,"Oh, shoot, I just put my location information in.
00:17:48.304 --> 00:17:58.933
Let me make the 911 call from here." And then he was able to make the 911 call, and actually it w- it turned out to be a better situation not calling from his cell phone because he was able to say,"Hey, I'm on the fourth floor.
00:17:58.933 --> 00:18:04.663
I'm in room 413." When he dialed 911, automatically all that information was shared with the 911 center.
00:18:04.673 --> 00:18:15.153
If he would've called with his cell phone, yeah, it would've given him a map overhead and said,"Hey, he's in this building," but they would've had to search probably several floors, not knowing exactly what room he was c- he was calling from.
00:18:15.153 --> 00:18:25.433
So I say all, all the time, it's a better situation, especially if you're calling from a hotel or you live in an apartment complex, to use your soft phone on your laptop than to call from your cell phone.
00:18:25.433 --> 00:18:42.334
Yes, location information has gotten a lot better when it comes to cell phone usage, but when it's right there in black and white,"Hey, I'm calling from the office in the in the d- detached garage," for instance, somebody's working from home, it just gives the first responders that right there, it's in black and white, this is where the person's at
00:18:42.584 --> 00:18:44.733
Could be saving valuable moments, couldn't it?
00:18:44.756 --> 00:18:46.395
Yeah, and that's what the whole point is, right?
00:18:46.395 --> 00:18:49.016
Saving time to get to that person as quickly as possible.
00:18:49.266 --> 00:18:50.645
Minutes mean lives, so
00:18:50.748 --> 00:18:56.573
'Cause like a, another typical scenario is like we've got a contact center on the third floor of this building.
00:18:56.583 --> 00:18:57.633
That's where everybody's at.
00:18:57.633 --> 00:18:59.673
I'm just gonna hard code the location to be that.
00:19:00.022 --> 00:19:01.752
But then the users are working from home.
00:19:01.932 --> 00:19:08.393
If they place a call the first responders show up at the office and not where the the end user at is actually located.
00:19:08.403 --> 00:19:20.163
So it, it is one of those things that it's like, you know, Don, to your point, it's one of those things that there are a lot of corner cases, there are a lot of different scenarios that come up, and, sometimes people are just like it's just gonna be re-real easy.
00:19:20.163 --> 00:19:28.762
Just hard code a location, dust my hands off and call it good." But, if you have agents that are working from home or, hybrid work, it's may not be accurate
00:19:29.265 --> 00:19:29.625
Yeah.
00:19:29.845 --> 00:19:30.164
Yeah.
00:19:30.505 --> 00:19:39.400
And it's actually there's a value as well to having a company like yours that obviously you work with Amazon Connect, but you also work with a bunch of other kind of telecommunications providers.
00:19:39.400 --> 00:19:40.500
You also work with the mobile network.
00:19:40.609 --> 00:19:45.390
I was just looking on your website for, like, how you do that stuff with mobile, just cell calls as well, right?
00:19:45.390 --> 00:19:48.289
For like campuses and big estates and stuff like that.
00:19:48.670 --> 00:19:55.490
You could totally see, because you're right in an emergency, folks will do all sorts of things and they'll just grab whatever's nearest or to your point, whatever makes the most sense.
00:19:55.500 --> 00:20:05.960
So having something that can look across them all, and so the the security teams, the response teams or whatever, have a single place to go, a single pop-up, a single essentially a single procedure to follow.
00:20:06.440 --> 00:20:08.230
You can see the value in that as well, for sure.
00:20:08.976 --> 00:20:10.986
Yeah, the cell phone thing's been really exciting for us.
00:20:11.046 --> 00:20:12.756
Alan, I'm stealing his thing here.
00:20:12.756 --> 00:20:18.736
He said"Being able to alert when somebody makes a 911 call from a cell phone is like the Holy Grail when it comes to 911." And it really is.
00:20:18.736 --> 00:20:31.066
Like I said, I've been doing this for 20 years, and one of the very first calls that I was ever on was like, person was like,"Hey, it's great that you can do this for the phone system, but what about for cell phone calls?" And it was like wah, sorry, there's nothing we could do." And so now that we can do this, it is so exciting.
00:20:31.076 --> 00:20:35.685
We're talking to colleges and universities especially, and, there was one I just talked to this past Tuesday.
00:20:35.935 --> 00:20:39.215
I talked to them for the first time on Tuesday, and they were like,"Yeah, you know what?
00:20:39.385 --> 00:20:47.756
We get a lot of 911 calls during move-in because, people-- there's a lot of people there, and there's, confusion and,'Oh, that cart was mine!'" And then they start, some fight breaks out or whatever.
00:20:48.026 --> 00:20:53.935
And it was like,"It'd be really nice to be able to have this for, this coming weekend, but, we're not gonna be able to get a purchase order in time.
00:20:53.935 --> 00:20:57.796
We're not gonna be able to do this, and I'm sure the implementation time takes a long time." And I was like,"You know what?
00:20:57.826 --> 00:20:58.736
Hey, let's just do it.
00:20:59.036 --> 00:21:04.935
Let's just, fire you guys up." And they're like,"Really?" And I was like,"Is it really that quick?" And then we got on a call the next morning.
00:21:05.115 --> 00:21:06.115
Actually, I wasn't even on the call.
00:21:06.115 --> 00:21:07.036
I was on a different call.
00:21:07.036 --> 00:21:10.766
One of our, our-- Well our implementation team w- got on the call and got them up and running.
00:21:10.766 --> 00:21:15.586
So now they're receiving text messages and emails whenever anybody makes a 911 call from a cell phone.
00:21:15.586 --> 00:21:17.836
It's, it's-- it'll be interesting to see what happens over this weekend.
00:21:18.195 --> 00:21:26.445
But the fact that we can do it and we can do it so quickly, it's it's really exciting to be able to finally bridge that gap and say,"Hey, you know what?
00:21:26.486 --> 00:21:29.175
Yeah, we can cover you if somebody makes a 911 call from a cell phone."
00:21:29.771 --> 00:21:30.362
That's so cool.
00:21:30.372 --> 00:21:33.731
W- I think that's probably a US-centric thing, but how does that work?
00:21:33.731 --> 00:21:35.481
Is it just like a nationwide service?
00:21:35.511 --> 00:21:37.291
Is it like carrier specific?
00:21:37.372 --> 00:21:44.961
Without going into as much detail as you want to, but and is it available to everybody or is it like a thing you pay for or like you have to be approved or how
00:21:45.071 --> 00:21:46.102
is some costs involved.
00:21:46.211 --> 00:21:50.652
Yeah, there definitely is some costs involved, and it's not 100% of the country is covered.
00:21:50.852 --> 00:21:53.781
There's certain things that the, the 911 center has to be subscribed to.
00:21:53.781 --> 00:21:57.122
There's a company called RapidSOS that kinda works behind the scenes and whatnot.
00:21:57.122 --> 00:22:06.261
But the great thing about it is if there is coverage in the area, the end user, the person who's actually making the 911 call, the only thing that they have to do is dial 911.
00:22:06.602 --> 00:22:18.791
They don't have to download an app,'cause there's been solutions out there for a long time where it's like,"All right, have all of your students download this app and if-- and train them if they need to have an emergency, go into the app and make the 911 call." Who's gonna do that?
00:22:18.791 --> 00:22:21.541
And who's gonna remember that they downloaded an app three years ago?
00:22:21.541 --> 00:22:25.041
And most of the time that adoption's like maybe 20 or 30%.
00:22:25.041 --> 00:22:29.741
And the, the user actually doesn't even have to opt in, and the reason why is because we all already have.
00:22:29.741 --> 00:22:37.231
And what I mean by that is when you either got a new cell phone or maybe upgraded the software in your cell phone, every once in a while you have to agree to some terms and conditions.
00:22:37.291 --> 00:22:39.251
Everybody just scrolls down to the bottom and hits agree, right?
00:22:39.402 --> 00:22:48.551
One of the things that you scroll by is that you're gonna allow, if you make a 911 call, the location payload or your device coordinates that are in your phone to be sent to RapidSOS.
00:22:48.781 --> 00:22:50.142
We partner with RapidSOS.
00:22:50.142 --> 00:22:58.571
We draw this geofence and if the XY coordinates land within a geofence that we've created, they send us an alert, and that's how we are able to alert people on site.
00:22:58.582 --> 00:23:01.571
And again, this is all already been set up on the back end for our stuff.
00:23:01.832 --> 00:23:06.592
All we have to do is hit a couple of check marks on our side, and that's how it happens so quickly.
00:23:08.031 --> 00:23:16.564
Got it a follow-up question on that as I just think about it is there's maybe an irrational fear, that people have about being tracked and locations and stuff like that.
00:23:16.723 --> 00:23:23.273
Is all of this stuff, does it only work for 911 calls, or is it like you put in this kind of like you can get this location stuff?
00:23:23.324 --> 00:23:29.013
If I wanted to, could I geolocate all of my people making phone calls not on 911 calls, or is that not even a thing?
00:23:29.933 --> 00:23:30.253
Yeah.
00:23:30.253 --> 00:23:32.413
So that, that is a valid concern, right?
00:23:32.413 --> 00:23:36.554
'Cause, in today's world there's all kinds of weird stuff happening bad stuff.
00:23:36.963 --> 00:23:38.993
But this does only work for 911 calls.
00:23:39.074 --> 00:23:45.523
So essentially the location that's being i-i-identified is always under the control of the the end user.
00:23:45.574 --> 00:23:47.784
They can always change the, their location.
00:23:48.243 --> 00:23:55.894
So the system, like if it is automatically able to determine their location, says,"Hey, we think you're on the second floor here." They get a little toast message.
00:23:55.894 --> 00:23:57.294
They can change it if they want to.
00:23:57.653 --> 00:24:01.854
And if they're working remotely, then they have to s- you know, kinda set their own location.
00:24:01.854 --> 00:24:05.463
But if they have set that location, it's only available during an emergency call.
00:24:05.973 --> 00:24:14.124
It's worth mentioning because we've worked with you guys, and it generally was, really quite easy, in terms of a project to get things going.
00:24:14.554 --> 00:24:21.913
Was great to work with, very helpful, but it just seemed like, there were not too many moving parts in terms of things that we as the partner have to do.
00:24:21.953 --> 00:24:24.733
There was a bit of work in a couple of contact flows.
00:24:25.183 --> 00:24:28.203
There's what, maybe a couple of Lambda functions, Alan?
00:24:28.463 --> 00:24:30.413
But it was fairly low touch.
00:24:30.473 --> 00:24:39.193
And for the the relief it gives you to, to put in a, a robust solution, actually, it's pretty low effort from the partner standpoint, which is good and worth calling out.
00:24:39.443 --> 00:24:41.584
Yeah that's one of the things I like about the solution too.
00:24:41.673 --> 00:24:43.384
To your point, it's a couple Lambda calls.
00:24:43.663 --> 00:24:44.923
It's all API-driven.
00:24:44.923 --> 00:24:51.973
There's no plumbing to set up, to set up trunking and all the nonsense that goes along with SBCs and security and stuff like that.
00:24:51.973 --> 00:24:53.384
It's all just an API call.
00:24:53.884 --> 00:24:58.743
That's it's really fun to see how the whole thing works, but it's if you boil it down that's what it is.
00:24:58.864 --> 00:25:01.074
Somebody dials nine one one, hits an outbound flow.
00:25:01.453 --> 00:25:04.253
That flow hits a Lambda function that calls our side.
00:25:04.324 --> 00:25:06.554
Our side responds back with the location payload.
00:25:06.804 --> 00:25:07.183
Done.
00:25:07.423 --> 00:25:07.713
Easy.
00:25:08.531 --> 00:25:10.761
And the other neat thing was the callback, right?
00:25:10.761 --> 00:25:24.471
So if somebody makes a 911 call and then maybe gets disconnected, the emergency services are able to get straight back to them, to the user rather than to, like you said earlier, a, a front desk or a queue.
00:25:24.801 --> 00:25:26.692
That's pretty neat how that works as well.
00:25:27.488 --> 00:25:33.748
Yeah, that's that's a really important piece, especially in the contact center space'cause the, the agents don't have DIDs anymore, right?
00:25:33.748 --> 00:25:36.718
The, the agent is identified by their email address.
00:25:36.718 --> 00:25:50.978
So essentially the way that our system works is as that user is onboarded, once they're created for the first time, we'll say,"Oh, this guy doesn't have a phone number," so we'll assign what we call a shared callback number to the user, and that shared callback number is kinda shared across multiple users.
00:25:51.268 --> 00:25:56.327
Every user is assigned to one, but it's only activated when there's an a-actual outbound 911 call.
00:25:56.758 --> 00:26:00.907
So you don't have to worry about inbound calls coming in off the PSTN into the agents.
00:26:01.137 --> 00:26:07.337
It is triggered by the outbound 911 call mapping that shared callback number to that s- that particular agent.
00:26:07.718 --> 00:26:22.428
And then Alex, to your point, if the user gets disconnected and a callback comes into the system, the flow is just kinda reversed where it comes into Connect, Connect asks us and says,"Hey, who, who should I route this call back to?" And then we send it back to the user's email address or identifier.
00:26:22.678 --> 00:26:22.798
Got it.
00:26:22.847 --> 00:26:23.298
That's cool.
00:26:23.938 --> 00:26:28.248
Yeah, it's a really neat neat way of using the technology that exists to solve that problem.
00:26:28.307 --> 00:26:28.387
I
00:26:28.451 --> 00:26:28.771
Yeah.
00:26:29.122 --> 00:26:32.662
And it goes back to the old the old school PBX method.
00:26:32.662 --> 00:26:34.001
It's called an ELAN, right?
00:26:34.011 --> 00:26:40.821
There's a phone number that's assigned to a location, and then as a user places an outbound call, that mapping is associated.
00:26:40.842 --> 00:26:47.571
We've just taken that that old school telephony kind of practice and shoved it into the the new world API
00:26:48.071 --> 00:26:48.271
Got it.
00:26:48.392 --> 00:26:56.981
So I think, we've talked a lot about US stuff, but actually I think this isn't just a US topic because I think you have to consider it wherever you are in the world.
00:26:56.981 --> 00:27:00.622
Even if you're not covered by legislation, like it just makes sense to think about it.
00:27:01.261 --> 00:27:07.451
And in some ways it's more of a, a question that comes up at different points through the cycle for non-US customers, right?
00:27:07.451 --> 00:27:13.571
'Cause US customers probably have it in their heads from the start, or like it comes up in sales or pre-sales because it, they have to, right?
00:27:13.582 --> 00:27:14.652
It has to be considered.
00:27:14.761 --> 00:27:21.971
Whereas the rest of the world, like it's a, a thing you've gotta think about and make a decision on, and no one's gonna tell you off if you don't do it.
00:27:22.382 --> 00:27:29.852
But for non-US customers when's the right time to start thinking about, using something like 911 Secure?
00:27:30.152 --> 00:27:37.201
If you're doing like a Connect rollout or you're doing a migration or something like that, do you put in Connect first and then think about putting this on afterwards?
00:27:37.201 --> 00:27:38.971
Or should you do it right at the beginning, or does it matter?
00:27:39.021 --> 00:27:39.602
What's the...
00:27:40.061 --> 00:27:41.132
Like what's the optimal flow,
00:27:41.182 --> 00:27:41.491
yeah.
00:27:41.521 --> 00:27:45.461
I think it really comes down to u-understanding the environment, right?
00:27:45.471 --> 00:27:46.912
Do they have multiple sites?
00:27:46.912 --> 00:27:48.642
Do they have users working from home?
00:27:49.092 --> 00:27:49.951
Those kind of things.
00:27:49.971 --> 00:27:54.652
And then, to your point, the, the legislation that we've been talking about only exists in the United States, right?
00:27:54.652 --> 00:27:59.821
So it's not like there's a version of Kari's Law that works in in Germany, for example.
00:28:00.271 --> 00:28:02.001
However, the use case is still there, right?
00:28:02.001 --> 00:28:15.454
If there is a fac- a, a facility where there are users that are working in that facility and the first responders show up, then you can't just walk in off the street and go up to the conference room on the fifth floor, right?
00:28:15.505 --> 00:28:17.585
You have-- everybody's got a-access control.
00:28:17.585 --> 00:28:19.255
You gotta badge in and stuff like that.
00:28:19.595 --> 00:28:24.214
Just the, the notification to the security team could definitely help out the solution.
00:28:24.625 --> 00:28:27.934
But it really comes down to understanding like, how is it going to be used?
00:28:28.244 --> 00:28:30.194
Where is it going to be be implemented?
00:28:30.234 --> 00:28:32.575
Are all the users gonna be 100% remote?
00:28:33.295 --> 00:28:40.835
Do they have hybrid users that come in and out of the office, or does everybody have to come in and stay in, in the the contact center on the third floor?
00:28:41.075 --> 00:28:55.634
So it really kinda comes down to understanding how that works and and really kinda planning that out as I'd say as you're kinda thinking through how to set up the user groups and things like that within the the Connect system is to, think about the, the emergency access side.
00:28:55.884 --> 00:28:56.174
Yeah.
00:28:56.269 --> 00:29:03.558
Yeah, one thing I wanted to point out is, yeah, we have legislation here in the United States, and I think it's good and it's gotten a lot of people to do things.
00:29:03.558 --> 00:29:08.009
But, since Alan and I have been in this industry for so long, we did it pre any kind of legislation.
00:29:08.009 --> 00:29:11.538
And, we've been solving these problems for customers for a long time.
00:29:11.858 --> 00:29:15.338
And I think it's oh gosh, you're only gonna do this because there's legislation.
00:29:15.388 --> 00:29:17.568
No, you need to do it because it's the right thing to do.
00:29:17.719 --> 00:29:19.618
Number one, if you're, like, in a place where...
00:29:19.729 --> 00:29:27.388
again, pre, pre Kari's Law when Kari Hunt, and that's who the the law is named after, she was murdered and there was no law in place.
00:29:27.699 --> 00:29:30.808
But the family sued, and they were awarded forty-one and a half million dollars.
00:29:30.828 --> 00:29:42.358
I know outside the United States is maybe not as litigious as the US, but it doesn't absolve you just because there's no specific legislation saying,"Hey you need to do something." But then again, like it boils down, it's the right thing to do.
00:29:42.368 --> 00:29:46.568
Again, one of the first times I was on a call with a customer, I, they were like,"Yeah let's move forward.
00:29:46.568 --> 00:29:50.179
We're gonna do this." And then it got to procurement, and procurement was like,"Ah, we don't have budget for it.
00:29:50.179 --> 00:29:56.429
We're gonna kick the can down the road." And about six months after I, I heard about that, they called me and said,"Hey, you need to fly back out.
00:29:56.429 --> 00:29:59.648
We need to do a presentation," to, the upper management and whatnot.
00:29:59.648 --> 00:30:05.028
And right when I got picked up from the airport, the guy goes,"Somebody died." And literally, somebody had made a 911 call.
00:30:05.028 --> 00:30:06.388
They were in the basement of a building.
00:30:06.759 --> 00:30:10.298
The call said that she was in a building that was about a mile away.
00:30:10.578 --> 00:30:14.588
They went and dispatched people to that location rather than going to find her.
00:30:14.729 --> 00:30:17.419
She couldn't call from her cell phone because she was in a-- in the basement.
00:30:17.419 --> 00:30:20.679
They-- she had no cell cov-cell coverage, and it was a horrible situation.
00:30:20.689 --> 00:30:29.858
If literally, if they would've moved forward and we would've implemented the solution, her location would've been automatically transmitted and there's a very good chance she would've lived'cause she ended up passing away.
00:30:30.159 --> 00:30:35.638
It took'em forty-five minutes to get finally out to her, and she was on the phone for quite a while before she passed out.
00:30:35.719 --> 00:30:40.909
And again, she had a heart attack and the faster you get to somebody who's having a heart attack, the faster they're gonna be saved.
00:30:40.909 --> 00:30:54.398
And again, it boils down to, yeah, there's legislation, yeah, you might get sued, but at the bottom line thing is, would you really wanna implement something where if you would've done that extra step of implementing a 911 solution that one of your coworkers literally just died?
00:30:54.608 --> 00:30:58.868
And not to get too morbid on that, but this is what we do and this is what we see.
00:30:59.138 --> 00:31:10.798
Yeah, it doesn't happen all the time to every single company that's out there, but since we've been in this for so long, we've seen that technology can kill people because you don't have the thing set up correctly, it literally can kill, take somebody's life.
00:31:11.436 --> 00:31:12.497
Yeah, 100%.
00:31:12.497 --> 00:31:24.807
And in some ways, actually the, now that the technology is all there, now that these various legislations and laws have forced all the pieces to be there, you've got to look even harder at yourself regardless of the legislation if you like.
00:31:24.846 --> 00:31:26.866
I know it's all there and I'm choosing not to use it.
00:31:27.076 --> 00:31:31.977
That's a different thing, rather than just like apathetically"Oh, this seems too hard." It's actually it's not that hard anymore,
00:31:32.076 --> 00:31:32.156
yeah.
00:31:32.272 --> 00:31:34.502
So yeah, this is really interesting.
00:31:34.823 --> 00:31:38.673
Gentlemen, we could talk about this stuff all day but it is time to bring this episode to an end.
00:31:39.133 --> 00:31:39.833
Thank you, Kevin.
00:31:39.883 --> 00:31:40.583
Thank you, Alan.
00:31:40.643 --> 00:31:45.182
This has been really interesting and, super informative and thank you Alex as well for your
00:31:45.423 --> 00:31:45.803
Thank you, guys
00:31:45.932 --> 00:31:46.673
questions and input.
00:31:46.702 --> 00:31:46.903
Yeah.
00:31:46.903 --> 00:31:47.222
Thank you.
00:31:47.393 --> 00:31:48.803
And thank you all for listening.
00:31:48.843 --> 00:31:51.163
Be sure to subscribe in your favorite podcast player.
00:31:51.222 --> 00:31:52.782
That way you won't miss the next episode.
00:31:53.212 --> 00:31:55.633
Whilst you're there, we would love it if you would rate and review us.
00:31:55.653 --> 00:31:58.843
If you have colleagues that you think would benefit from this content, please let them know.
00:31:58.853 --> 00:32:04.893
To find out more about how Cloud Interact can help you on your contact center journey, visit cloudinteract.io.
00:32:05.313 --> 00:32:08.772
We're wrapping this call up now, and we'll connect with you next time.